A
Asperis
Guest
Hi, I've really been struggling with this and I've just needed some help, I have been getting DPC_WATCHDOG_VIOLATION BSOD's since making my new pc, the MOBO is a asrock b450m, the RAM is Crucial Ballistix 16GB, first the PC would probably crash around 2-3 times a day in the middle of me doing things, I updated and did a clean install of my GPU's driver which is a GeForce GT 1030, then the crashes seemed to stop (I also ran memtest86 and got 0 errors), but I've gotten 1 on startup recently for the same exact reason according to the dump log as the previous ones.
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\theke\Desktop\011621-5906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`19c00000 PsLoadedModuleList = 0xfffff802`1a82a2b0
Debug session time: Sat Jan 16 02:14:08.072 2021 (UTC - 7:00)
System Uptime: 0 days 18:16:21.703
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
...................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`19ff5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff802`1f67a540=0000000000000133
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8021a8fa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4140
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-IDU3QQI
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 23535
Key : Analysis.Memory.CommitPeak.Mb
Value: 77
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8021a8fa320
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: fffff8021f67a720 -- (.trap 0xfffff8021f67a720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000003000000 rbx=0000000000000000 rcx=0000000000184022
rdx=ffffe68af0d44000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8022e70b055 rsp=fffff8021f67a8b8 rbp=ffffe68aefd71010
r8=ffffe68af0d450a0 r9=0000000000610088 r10=0000000000000002
r11=fffff8021f67a940 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
nvlddmkm+0xbb055:
fffff802`2e70b055 c3 ret
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: RustClient.exe
STACK_TEXT:
fffff802`1f67a538 fffff802`1a03aa0c : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`1a8fa320 : nt!KeBugCheckEx
fffff802`1f67a540 fffff802`19e6f9a3 : 0000d777`946845bc fffff802`17763180 00000000`00000000 fffff802`17763180 : nt!KeAccumulateTicks+0x1c880c
fffff802`1f67a5a0 fffff802`19e6f48a : fffff802`1a8f3840 fffff802`1f67a7a0 fffff802`17763100 fffff802`1a8f38f0 : nt!KeClockInterruptNotify+0x453
fffff802`1f67a650 fffff802`19f27ef5 : fffff802`1a8f3840 fffff802`1f67a7d0 fffff802`1f67a700 fffff802`1a8f3840 : nt!HalpTimerClockIpiRoutine+0x1a
fffff802`1f67a680 fffff802`19ff722a : fffff802`1f67a7a0 fffff802`1a8f3840 00000000`00000000 fffff802`19eec5ca : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`1f67a6d0 fffff802`19ff7797 : ffffe68a`f0d44000 fffff802`19ff7797 00000000`00000100 ffffe68a`efd71320 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff802`1f67a720 fffff802`2e70b055 : fffff802`2e7b8fb1 ffffe68a`f0d44000 ffffe68a`efd71010 00000000`00000020 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff802`1f67a8b8 fffff802`2e7b8fb1 : ffffe68a`f0d44000 ffffe68a`efd71010 00000000`00000020 00000000`00000000 : nvlddmkm+0xbb055
fffff802`1f67a8c0 ffffe68a`f0d44000 : ffffe68a`efd71010 00000000`00000020 00000000`00000000 ffffe68a`00000020 : nvlddmkm+0x168fb1
fffff802`1f67a8c8 ffffe68a`efd71010 : 00000000`00000020 00000000`00000000 ffffe68a`00000020 fffff802`1f67a958 : 0xffffe68a`f0d44000
fffff802`1f67a8d0 00000000`00000020 : 00000000`00000000 ffffe68a`00000020 fffff802`1f67a958 fffff802`1f67ab60 : 0xffffe68a`efd71010
fffff802`1f67a8d8 00000000`00000000 : ffffe68a`00000020 fffff802`1f67a958 fffff802`1f67ab60 00000000`00000020 : 0x20
SYMBOL_NAME: nvlddmkm+bb055
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: bb055
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner
---------
Continue reading...
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\theke\Desktop\011621-5906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`19c00000 PsLoadedModuleList = 0xfffff802`1a82a2b0
Debug session time: Sat Jan 16 02:14:08.072 2021 (UTC - 7:00)
System Uptime: 0 days 18:16:21.703
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
...................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`19ff5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff802`1f67a540=0000000000000133
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8021a8fa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4140
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-IDU3QQI
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 23535
Key : Analysis.Memory.CommitPeak.Mb
Value: 77
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8021a8fa320
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: fffff8021f67a720 -- (.trap 0xfffff8021f67a720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000003000000 rbx=0000000000000000 rcx=0000000000184022
rdx=ffffe68af0d44000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8022e70b055 rsp=fffff8021f67a8b8 rbp=ffffe68aefd71010
r8=ffffe68af0d450a0 r9=0000000000610088 r10=0000000000000002
r11=fffff8021f67a940 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
nvlddmkm+0xbb055:
fffff802`2e70b055 c3 ret
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: RustClient.exe
STACK_TEXT:
fffff802`1f67a538 fffff802`1a03aa0c : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`1a8fa320 : nt!KeBugCheckEx
fffff802`1f67a540 fffff802`19e6f9a3 : 0000d777`946845bc fffff802`17763180 00000000`00000000 fffff802`17763180 : nt!KeAccumulateTicks+0x1c880c
fffff802`1f67a5a0 fffff802`19e6f48a : fffff802`1a8f3840 fffff802`1f67a7a0 fffff802`17763100 fffff802`1a8f38f0 : nt!KeClockInterruptNotify+0x453
fffff802`1f67a650 fffff802`19f27ef5 : fffff802`1a8f3840 fffff802`1f67a7d0 fffff802`1f67a700 fffff802`1a8f3840 : nt!HalpTimerClockIpiRoutine+0x1a
fffff802`1f67a680 fffff802`19ff722a : fffff802`1f67a7a0 fffff802`1a8f3840 00000000`00000000 fffff802`19eec5ca : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`1f67a6d0 fffff802`19ff7797 : ffffe68a`f0d44000 fffff802`19ff7797 00000000`00000100 ffffe68a`efd71320 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff802`1f67a720 fffff802`2e70b055 : fffff802`2e7b8fb1 ffffe68a`f0d44000 ffffe68a`efd71010 00000000`00000020 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff802`1f67a8b8 fffff802`2e7b8fb1 : ffffe68a`f0d44000 ffffe68a`efd71010 00000000`00000020 00000000`00000000 : nvlddmkm+0xbb055
fffff802`1f67a8c0 ffffe68a`f0d44000 : ffffe68a`efd71010 00000000`00000020 00000000`00000000 ffffe68a`00000020 : nvlddmkm+0x168fb1
fffff802`1f67a8c8 ffffe68a`efd71010 : 00000000`00000020 00000000`00000000 ffffe68a`00000020 fffff802`1f67a958 : 0xffffe68a`f0d44000
fffff802`1f67a8d0 00000000`00000020 : 00000000`00000000 ffffe68a`00000020 fffff802`1f67a958 fffff802`1f67ab60 : 0xffffe68a`efd71010
fffff802`1f67a8d8 00000000`00000000 : ffffe68a`00000020 fffff802`1f67a958 fffff802`1f67ab60 00000000`00000020 : 0x20
SYMBOL_NAME: nvlddmkm+bb055
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: bb055
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner
---------
Continue reading...