Windows 10 Need help with DPC Watchdog BSOD error

[la102]

Hi everyone

About once a day I get DPC_WATCHDOG_VIOLATION blue screen and it's really frustrating. Please help

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers for more information
Windows 8 Kernel Version 17763 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff80225400000 PsLoadedModuleList = 0xfffff8022581bad0
Debug session time: Fri Feb 22 20:40:31.070 2019 (UTC - 5:00)
System Uptime: 2 days 7:50:47.797
***

• *
• Bugcheck Analysis *
• *

***

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff80225942380

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

LAST_CONTROL_TRANSFER: from fffff80225656145 to fffff802255b3440

STACK_TEXT:
ffff85013e1ffba8 fffff80225656145 : 0000000000000133 0000000000000000 0000000000000501 0000000000000500 : nt!KeBugCheckEx
ffff85013e1ffbb0 fffff80225523daf : 00003fb15edf7acc ffff85013e129180 0000000000000286 0000000000c455f3 : nt!KeAccumulateTicks+0x12ed25
ffff85013e1ffc10 fffff80225e7247c : 0000000000000000 ffffae87bf0d3600 ffff8202e0a4f730 ffffae87bf0d36b0 : nt!KeClockInterruptNotify+0xcf
ffff85013e1fff30 fffff802254428b5 : ffffae87bf0d3600 fffff802255b8d16 0000000000000010 0000000000200246 : hal!HalpTimerClockIpiRoutine+0x1c
ffff85013e1fff60 fffff802255b4e3a : ffff8202e0a4f730 ffffae87bf0d3600 0000000000000000 ffffae87bf0d3600 : nt!KiCallInterruptServiceRoutine+0xa5
ffff85013e1fffb0 fffff802255b5387 : ffff820200000000 00001f80005b0294 0000000005d7129a ffff8202e0a4f898 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8202e0a4f6b0 fffff802254f0a0f : 0000000000000000 fffff80225466ec5 ffff85013e129180 fffff8022557b824 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8202e0a4f840 fffff80225466ec5 : ffff85013e129180 fffff8022557b824 0000000000000000 0000000000000001 : nt!KeYieldProcessorEx+0x1f
ffff8202e0a4f850 fffff802254b8c67 : ffff85013e12bf80 ffff820205d7259a ffff8202e0a4f990 ffff85013e12ea20 : nt!ExpGetPoolTagInfoTarget+0x65
ffff8202e0a4f890 fffff802254b82ae : ffff85013e139200 0000000000c45000 0000000000000001 ffff85013e139200 : nt!KiExecuteAllDpcs+0x2e7
ffff8202e0a4f9d0 fffff802255b6e5a : 0000000000000000 ffff85013e129180 0000000000000000 0000000000000000 : nt!KiRetireDpcList+0x1ae
ffff8202e0a4fbe0 0000000000000000 : ffff8202e0a50000 ffff8202e0a49000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KeAccumulateTicks+12ed25
fffff802`25656145 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KeAccumulateTicks+12ed25

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x133_nt!KeAccumulateTicks+12ed25

BUCKET_ID: X64_0x133_nt!KeAccumulateTicks+12ed25

Followup: MachineOwner
---------




More...