BSoD DPC WATCHDOG VIOLATION NVIDIA

My Windows 10 PC has been freezing followed by a BSoD screen with the stop code DPC_WATCHDOG_VIOLATION. I first encountered the blue screen on 2022/2/10 while Windows 10 was updating and followed the directions on the Microsoft Support “Troubleshoot blue screen errors” page. There were three updates installed: 1) Servicing Stack 10.0.19041.1525, 2) Update for Microsoft Windows (KB5009467), and 3) Security Update for Microsoft Windows (KB5010342). I was able to uninstall Update (2) and Security Update (3), but Servicing Stack did not have an uninstall option. Windows update was run to reinstall the two that were removed.

The freezing followed by the blue screen continued. I have opened the dump files in WinDbg to determine the affected driver and found they are related to the NVIDIA graphics card (see below). After that time I updated the NVIDIA graphics card driver through their driver update software. BSoD still occurred. Later, I used DDU for a clean uninstall of the current driver, then a clean install with an older/different driver. I have done this two times already. BSoD still occurred. My Windows 10 is up to date and so is my BIOS. So far I have not tied it to any activity on the PC when BSoD occurs, other than my son began using a USB gaming headset about that time.

Do I install older NVIDIA drivers until it works? Below are links to zipped files on my OneDrive containing the latest dump files for your analysis. I would appreciate any help and let me know if you need any more information.

Shared memory dump files on OneDrive:

2022/3/8 to 2022/3/12

2022/3/13 to 2022/3/14

2022/3/15 to 2022/3/18

Affected drivers found using WinDbg to open minidump files:

• 2022-0313 10:02 am: Image name winhvr.sys
• 2022-0314 11:05 am: Image name nvlddmkm.sys
• 2022-0314 1:06 pm: Image name ACPI.sys
• 2022-0314 7:30 pm: Image name rt640x64.sys
• 2022-0315 10:52 am: Image name nvlddmkm.sys
• 2022-0316 12:26 pm: Image name ACPI.sys
• 2022-0217 7:39 pm: Image name rt640x64.sys
• 2022-0318 11:32 am: Image name dxgmms2.sys
• 2022-0318 2:22 pm: Image name nvlddmkm.sys
• 2022-0318 5:37 pm: Image name ACPI.sys
• 2022-0318 9:17 pm: Image name dxgmms2.sys

2022/3/18 dump file from WinDbg:

Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\031822-8562-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 Personal

Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff800`1f000000 PsLoadedModuleList = 0xfffff800`1fc2a2d0

Debug session time: Fri Mar 18 14:22:59.330 2022 (UTC - 5:00)

System Uptime: 0 days 2:49:27.062

Loading Kernel Symbols

...............................................................

................................................................

................................................................

.............................................

Loading User Symbols

Loading unloaded module list

...............

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff800`1f3f7620 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffff800`1c54c500=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: fffff8001fcfa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

         additional information regarding the cumulative timeout

Arg4: 0000000000000000

Debugging Details:

------------------

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

*************************************************************************

***                                                                   ***

***                                                                   ***

***    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                                   ***

***                                                                   ***

*************************************************************************

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec

    Value: 4124

    Key  : Analysis.DebugAnalysisManager

    Value: Create

    Key  : Analysis.Elapsed.mSec

    Value: 28809

    Key  : Analysis.Init.CPU.mSec

    Value: 311

    Key  : Analysis.Init.Elapsed.mSec

    Value: 3730

    Key  : Analysis.Memory.CommitPeak.Mb

    Value: 97

    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

FILE_IN_CAB:  031822-8562-01.dmp

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8001fcfa320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff8001c54c6e0 -- (.trap 0xfffff8001c54c6e0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=000000000018470c

rdx=0000000000611c30 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8003bc2e420 rsp=fffff8001c54c870 rbp=ffffa884fee1ea10

 r8=fffff8001c54c8b8  r9=0000000000611c30 r10=fffff8001c54ca58

r11=000000000000000c r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei pl nz na po nc

nvlddmkm+0x8e420:

fffff800`3bc2e420 488b5c2430      mov     rbx,qword ptr [rsp+30h] ss:fffff800`1c54c8a0=ffffa884fee1e000

Resetting default scope

BLACKBOXACPI: 1 (!blackboxacpi)

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  

fffff800`1c54c4f8 fffff800`1f41f97e     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`1fcfa320 : nt!KeBugCheckEx

fffff800`1c54c500 fffff800`1f216953     : 00000e5b`aedf9b2b fffff800`1a7d7180 00000000`00000000 fffff800`1a7d7180 : nt!KeAccumulateTicks+0x2067ce

fffff800`1c54c560 fffff800`1f21643a     : fffff800`1fcf3880 fffff800`1c54c760 00000000`00000200 fffff800`1f21643a : nt!KeClockInterruptNotify+0x453

fffff800`1c54c610 fffff800`1f2de215     : fffff800`1fcf3880 fffff800`1fcf3930 fffff800`1a7d7180 fffff800`1f2de215 : nt!HalpTimerClockIpiRoutine+0x1a

fffff800`1c54c640 fffff800`1f3f90ca     : fffff800`1c54c760 fffff800`1fcf3880 fffff800`1c54cb01 fffff800`1f3f90ca : nt!KiCallInterruptServiceRoutine+0xa5

fffff800`1c54c690 fffff800`1f3f9637     : 00000000`00000000 00000000`00000000 00000000`00611ec0 fffff800`1f3f9644 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

fffff800`1c54c6e0 fffff800`3bc2e420     : 00000000`00611c30 00000000`00611c30 00000000`00000000 fffff800`1c54cb01 : nt!KiInterruptDispatchNoLockNoEtw+0x37

fffff800`1c54c870 00000000`00611c30     : 00000000`00611c30 00000000`00000000 fffff800`1c54cb01 00000000`00000020 : nvlddmkm+0x8e420

fffff800`1c54c878 00000000`00611c30     : 00000000`00000000 fffff800`1c54cb01 00000000`00000020 fffff800`3bd1d105 : 0x611c30

fffff800`1c54c880 00000000`00000000     : fffff800`1c54cb01 00000000`00000020 fffff800`3bd1d105 ffffa884`fee1e000 : 0x611c30

SYMBOL_NAME:  nvlddmkm+8e420

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  8e420

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

---------