Question DPC_WATCHDOG VIOLATION blue screen

[bwinters123]

Hello everyone. I am having some issues with a blue screen error DPC_WATCHDOG VIOLATION occurring at random times not associated with any particular software or anything. If anyone can find anything useful in the minidump it would be greatly appreciated.


https://www.dropbox.com/sh/1fdn2hcsfzvwu65/AABMSIongTOyu9rg8I1EIlw1a?dl=0

Loading Dump File [C:\Windows\Minidump\091321-6296-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80570000000 PsLoadedModuleList = 0xfffff80570c2a230
Debug session time: Mon Sep 13 18:37:28.290 2021 (UTC - 4:00)
System Uptime: 2 days 20:13:07.017
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805703f71b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff8057466db10=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: fffff80570cfa320, 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 *
* *
*
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 6843

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 122773

Key : Analysis.Init.CPU.mSec
Value: 311

Key : Analysis.Init.Elapsed.mSec
Value: 11345

Key : Analysis.Memory.CommitPeak.Mb
Value: 85

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


BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80570cfa320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff8057466dcf0 -- (.trap 0xfffff8057466dcf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80570397600 rbx=0000000000000000 rcx=0000000000001885
rdx=0000000000001885 rsi=0000000000000000 rdi=0000000000000000
rip=fffff805703976c9 rsp=fffff8057466de88 rbp=ffffb988b22cea20
r8=fffff8057466df00 r9=0000000000000001 r10=fffff805703976c0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!HalpAcpiPmRegisterReadPort+0x9:
fffff805703976c9 418800 mov byte ptr [r8],al ds:fffff8057466df00=00
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:
fffff8057466db08 fffff8057041f57e : 0000000000000133 0000000000000001 0000000000001e00 fffff80570cfa320 : nt!KeBugCheckEx
fffff8057466db10 fffff80570216ac3 : 0000814cb613c9ab fffff8056b674180 0000000000000000 fffff8056b674180 : nt!KeAccumulateTicks+0x20625e
fffff8057466db70 fffff805702165aa : fffff80570cf37c0 fffff8057466dd70 fffff8057466db00 fffff8058b80c1f0 : nt!KeClockInterruptNotify+0x453
fffff8057466dc20 fffff805702de045 : fffff80570cf37c0 0000000000000000 0000000000000000 0000000000000000 : nt!HalpTimerClockIpiRoutine+0x1a
fffff8057466dc50 fffff805703f8c5a : fffff8057466dd70 fffff80570cf37c0 0000814cb612bdac 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff8057466dca0 fffff805703f91c7 : 0000000000000000 0000000000000000 0000000000000001 0000000000000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff8057466dcf0 fffff805703976c9 : fffff80570396c99 0000000000000010 ffffb988b24fd000 ffffb988b26d9310 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff8057466de88 fffff80570396c99 : 0000000000000010 ffffb988b24fd000 ffffb988b26d9310 00000000000004f8 : nt!HalpAcpiPmRegisterReadPort+0x9
fffff8057466de90 fffff8057254671a : 0000000000000005 ffffd500fefd6280 fffff8057466df98 0000000000000f43 : nt!HalpAcpiPmRegisterRead+0x39
fffff8057466dec0 fffff80572545c94 : 0000000000000000 ffffd500fefd6dc0 0000000000000f43 fffff80500400a02 : ACPI!ACPIReadGpeStatusRegister+0x66
fffff8057466df00 fffff805702de045 : ffffd500fefd6dc0 ffffb988b22e3d70 ffffd500fefd6e70 ffff3a95f814bbf9 : ACPI!ACPIInterruptServiceRoutine+0x54
fffff8057466df40 fffff805703f89df : fffff8057465e4a0 ffffd500fefd6dc0 fffff80572520000 0000814cb612ba79 : nt!KiCallInterruptServiceRoutine+0xa5
fffff8057466df90 fffff805703f8ca7 : fffff805725a1860 0000000000000000 ffffb988cba6f102 0000000000000000 : nt!KiInterruptSubDispatch+0x11f
fffff8057465e420 fffff8057037bccc : fffff8057037a6e9 0000000000000000 ffffb988b7319ef8 fffff8057465e630 : nt!KiInterruptDispatch+0x37
fffff8057465e5b8 fffff8057037a6e9 : 0000000000000000 ffffb988b7319ef8 fffff8057465e630 fffff805725344f6 : nt!HalpAcpiPmRegisterWritePort+0xc
fffff8057465e5c0 fffff8057254644b : 0000000000000001 00001fa0003902c9 fffff80572550b80 0000000000040408 : nt!HalpAcpiPmRegisterWrite+0x39
fffff8057465e5f0 fffff805725463b7 : 0000000000000000 fffff80572520000 0000000000000004 0000000000000008 : ACPI!ACPIWriteGpeEnableRegister+0x6f
fffff8057465e630 fffff80572545fcf : 0000000000000010 0000000000000008 0000000000000000 0000000000000000 : ACPI!ACPIGpeEnableDisableEvents+0x37
fffff8057465e660 fffff8057029a3ae : fffff8056b677240 fffff8057465ea30 fffff8056b674180 fffff80500000002 : ACPI!ACPIInterruptDispatchEventDpc+0x1bf
fffff8057465e760 fffff80570299694 : 0000000000000000 0000000000000000 0000000000140001 0000000000000000 : nt!KiExecuteAllDpcs+0x30e
fffff8057465e8d0 fffff805703fad1e : 0000000000000000 fffff8056b674180 fffff80570d26a00 ffffb988ced26080 : nt!KiRetireDpcList+0x1f4
fffff8057465eb60 0000000000000000 : fffff8057465f000 fffff80574658000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: ACPI!ACPIReadGpeStatusRegister+66

MODULE_NAME: ACPI

IMAGE_NAME: ACPI.sys

IMAGE_VERSION: 10.0.19041.1110

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 66

FAILURE_BUCKET_ID: 0x133_ISR_ACPI!ACPIReadGpeStatusRegister

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9524459d-2f22-efe5-b0c9-f824c586f42c}

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

 

[bwinters123]

Bad weather can be a bummer Colif, but maybe if you are stuck inside you can help with my problem more! I am using the intel driver & support assistant already and have updated the intel wifi 6. I will try to update my router firmware today.

John, I had previously installed the chipset driver from Lenovo. Maybe the installer didn't work properly last time . Also, why wouldn't the intel assistant find this? I any case, I got it from Lenovo and installed it with no errors. However, when I look in device manager at the IDE ATA/ATAPI controllers I see "intel 400 series chipset family SATA AHCI controller" the driver details date is 12/20/2019. So I am not sure if I am not looking at the right place or the installer failed. There are no other chipsets under system devices.

 

[bwinters123]

Well I finally got feed up and went with the nuclear option and reinstalled windows 10. First I tried the fresh install tool, but it installed an old version of windows 10 and the updates failed so I could not update windows and the older version of windows was not compatible with the available Nvidia drivers. So I used the recovery media drive that I made when I first got the machine with the delete everything restore option and managed to get Windows setup and updated. Sadly though, after a couple of days of bliss the crashing started again just like before.

So I guess either there is a bad driver out there that Windows loaded again or I have some hardware problem. What do you guys think? I am kind of going crazy with this one.

Here are the two recent minidump files: https://www.dropbox.com/sh/1fdn2hcsfzvwu65/AABMSIongTOyu9rg8I1EIlw1a?dl=0

Any common threads in these dumps? If it is hardware, what should I try first? I already removed and reset the drives and memory. Should I switch the memory locations? Should I remove one memory stick at a time and see if one is bad?

 

[gardenman]

I think both Colif and johnbl may be away at this time.

One crash is blaming the NVIDIA drivers. Considering using DDU again and trying a different version of the driver. Either the latest one, a slightly older one, or the one from Windows Update.

I cannot tell what the cause of the 2nd one is. Have you tried removing the 2 Corsair RAM sticks that you added and just running the system with 8GB of RAM it came with? I know this may limit your gaming but it's worth it for a week or two to see if you continue crashing or not. (If you continue crashing, go ahead and add them back in).

To answer your last question, I think it's worth a try. You might as well run memtest while you are at it if you haven't yet. https://forums.tomshardware.com/threads/how-to-test-your-ram.3691373/

 

[bwinters123]

Thanks gardenman, I have run memtest with all chips but can try it again. Also, the additional RAM chips are not new additions, about 1.5 years old. Nonetheless it is worth a shot to remove them for a while. I will also do a fresh DDU install.

What about a hard drive issue? I have 3 drives. The m2 SSD and HDD that came with it and a samsung SSD I added in one of the open drive slots. I could remove the other two drives for a while and see if the problem persists.

 

[gardenman]

It's a good idea to strip it down as far as possible to see if you see have the issues. So, the less drives, RAM, etc, the better. Anything you can eliminate is progress.

 

[bwinters123]

I misspoke when I said I had tested the memory like said. I had only used the built-in windows memory test. So followed the instructions you sent and ran a full memtest from the usb drive and it passed with no errors. I put the report html file in the dropbox folder.

Does this rule out any memory issues or could it still be the socket or something? I could move them around to different sockets, but there is only one free.

 

[gardenman]

It's likely the RAM is OK if you got no errors with 4 full passes with memtest. However, using software to test hardware, in any fashion isn't perfect and can't always be 100% accurate. Could there still be a RAM issue? It's possible, but unlikely. We've seen people pass memtest before, replace their RAM, and their BSODs go away. Rare, but it happens.

I would still suggest removing the extra RAM and testing for a few days without it. The same with any extra drives or unnecessary USB devices. Eliminate as much as you can.

 

[bwinters123]

Well, sadly it didn't take long to get another crash with only the original RAM chip and the C drive. I also did the DDU Nvidia driver update. Anything consistent in the minidump?

https://www.dropbox.com/s/b3vy6r6l9naos51/102321-5421-01.dmp?dl=0

 

[bwinters123]

Thanks to everyone's input on this problem. It has been stable for several days now. I wish I could say exactly what fixed it, but I did several things at once.

For my IDE ATA/ATAI controller in device manager, I set it to the standard built in driver instead of the updated intel one I got from Lenovo. This was suggested by several post on DPC_WATCHDOG VIOLATION. I think this was for an older problem with drives and I had done it previously without any improvement.

View: https://www.youtube.com/watch?v=WchKOykPudw


I also turned on Verifier for a while, but didn't get any more crashes. Not clear how it would help with the reports anyway. But I followed this post which had some other setting changes associated with turning it on. https://www.makeuseof.com/how-to-use-driver-verifier-windows-10/

The other thing that I did that might be the most likely is that I installed the older Nvidia driver that Lenovo had on its update page after DDU wipe in safe mode.