Question DPC_WATCHDOG VIOLATION blue screen

Sep 13, 2021
13
0
10
0
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
---------
 

Colif

Win 10 Master
Moderator
Deferred Procedure Call in ACPI.sys. I seen that a few times this month, wonder whats going on with that.

I will ask a friend to convert dumps.

DPC errors can be Sound drivers so updating those could help
 

gardenman

Distinguished
Moderator
Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/r3up1qzj/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:091321-6296-01.dmp (Sep 13 2021 - 18:37:28)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Probably caused by:memory_corruption (Process: System)
Uptime:2 Day(s), 20 Hour(s), 13 Min(s), and 07 Sec(s)

File information:091021-7093-01.dmp (Sep 10 2021 - 21:55:42)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:memory_corruption (Process: System)
Uptime:2 Day(s), 10 Hour(s), 29 Min(s), and 43 Sec(s)

File information:090821-5968-01.dmp (Sep 8 2021 - 09:18:59)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 23 Hour(s), 50 Min(s), and 16 Sec(s)
Comment: 2 or more types of RAM are installed.

The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

Possible support page: https://pcsupport.lenovo.com/us/en/products/desktops-and-all-in-ones/legion-series/legion-t5-28imb05/?linkTrack=Caps:Body_BrowseProduct

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Sep 13, 2021
13
0
10
0
Thanks for the input everyone. The earlier minidump (090821) did indeed implicate the Nvidia driver so I did exactly as gardenman suggested using DDU in safemode then installing the newest driver from Nvidia. After this I have continued to get crashes and the Nvidia error was not in the later minidump files (091021 and 091321).

Another thing I noticed was that my wireless mouse battery was very low. Perhaps glitching out from time to time? I replaced the batteries and will try to update the sound drivers as Colif suggested.

I have had the two types of RAM since I got the computer ~1.5 years. The one 8 gb stick came with it and I added two more matching ones in the paired slots (there is a total of 4 slots in 2 pairs).

I also downloaded all available updated driver from the Lenovo site and installed them.
 
Last edited:

Colif

Win 10 Master
Moderator
Well 2 of the last 3 you gave us blamed NVIDIA, but the last is less revealing apart from it mentioning ACPI.sys

wonders why so many DPC errors relating to ACPI.sys right now. I just answered another DPC/ACPI.sys question. I seem to get patterns like this.

Advanced Configuration and Power Interface https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/acpi-driver
The responsibilities of Acpi. sys include support for power management and Plug and Play (PnP) device enumeration.

it was only mentioned, not blamed in yours.

can you give us any other dumps as you get them as more info helps.
 
Reactions: bwinters123

gardenman

Distinguished
Moderator
I ran the dump files through the debugger and got the following information: https://jsfiddle.net/c47rgtus/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:091821-11250-01.dmp (Sep 18 2021 - 14:34:23)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Probably caused by:memory_corruption (Process: System)
Uptime:1 Day(s), 17 Hour(s), 26 Min(s), and 39 Sec(s)

File information:091321-6296-01.dmp (Sep 13 2021 - 18:37:28)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Probably caused by:memory_corruption (Process: System)
Uptime:2 Day(s), 20 Hour(s), 13 Min(s), and 07 Sec(s)

File information:091021-7093-01.dmp (Sep 10 2021 - 21:55:42)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:memory_corruption (Process: System)
Uptime:2 Day(s), 10 Hour(s), 29 Min(s), and 43 Sec(s)

File information:090821-5968-01.dmp (Sep 8 2021 - 09:18:59)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 23 Hour(s), 50 Min(s), and 16 Sec(s)
Comment: Be sure you are uploading only new dumps to a new folder each time, and posting a link to that new folder. There's no way I can go through each persons dumps and sort out which ones I've looked at and which I haven't so far. Thank you.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Sep 13, 2021
13
0
10
0
Well I thought I had something figured out by replacing the wireless keyboard/mouse with wired ones, but after a pretty good run I had another random freeze/BSOD/reboot. The new minidump can be found here.

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

For some reason I can't seem to open these files anymore using WinDBG.

It is never the same thing twice as far a program being used or functions.

Does anyone think that refreshing Windows would fix things????
 

gardenman

Distinguished
Moderator
I ran the dump file through the debugger and got the following information: https://jsfiddle.net/fa4j0beg/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:092021-5921-01.dmp (Sep 20 2021 - 11:47:03)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Probably caused by:memory_corruption (Process: System)
Uptime:1 Day(s), 18 Hour(s), 02 Min(s), and 19 Sec(s)

I'll remind Colif about this thread.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 10 Master
Moderator
so last 4 have all been the same, DPC in APCI.sys.
Now I am not 100% sure the DPC errors are caused by Audio drivers, it just seems to be the result if I search for DPC ACPI.sys on Google so I feel I shouldn't ignore it, thats about only reason I am looking at your audio drivers now
Jan 16 2020RTKVHD64.sysRealtek Audio System driver https://www.realtek.com/en/
now I wonder what driver version that is
Can you look in device manager/Audio inputs and outputs
right click Realtek Digital Output, and choose properties
Look on driver tab.

realtek have 2 different kinds of drivers and it makes it complicated figuring out which you have
 
Sep 13, 2021
13
0
10
0
Maybe you are onto something here. I have stereo Mix by realtek. When I click on driver details though it says "no driver files are required or have been loaded for this device." But when I go to update driver it say the best one is installed, audio endpoint. See image in dropbox folder.

I also have speakers plugged into my monitor which go to my video card via HDMI. I get the same messages when I click on driver details and update driver for this one.

After yet another crash and reboot while writing this, the realtek one no longer appears in device manager. Also, when I reboot there is a blue screen saying "closing 1 app..." RealtekAudioBackgroundProcessClass

A new Nvidia driver came out today so I removed the prior one in safemode with DDU and installed the latest drivers including the HD audio one. After booting back into regular mode and checking the audio stuff in device manager I see both the nivida and realtek ones and get the same responses to trying to update/verify the drivers. It looks like it is still using the microsoft driver. See image in dropbox folder.

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

Finally, I moved the physical audio output jack to the computer instead of the monitor and now it shows up as "Speakers (Realtek(R) Audio" and uses the same driver as the others. Maybe if realtek gets to handle it completely everyone will play nice.
 
Last edited:

Colif

Win 10 Master
Moderator
its not same driver really, its just the Microsoft version of either realtek or Nvidia drivers
10.0.19041 = the windows build it was installed with
they are the newest drivers Realtek or NVIDIA have given Microsoft for testing, they may not be newest.

Its likely HD AUdio hasn't been updated by Nvidia since the version you are on, so they didn't replace it. I can't compare your version against what I have as I don't install the Nvidia HDMI audio drivers as my monitor doesn't have speakers, and discord app always wants to use those as default regardless.

i didn't think to ask where audio came from. I didn't even suspect it was monitor, as I run my 5.1 from the PC. SO I just assumed.
 

gardenman

Distinguished
Moderator
Colif might be slow to reply.

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/7m1ufgq4/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:100421-6171-01.dmp (Oct 4 2021 - 10:58:53)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Probably caused by:memory_corruption (Process: System)
Uptime:5 Day(s), 11 Hour(s), 18 Min(s), and 29 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Sep 13, 2021
13
0
10
0
Thanks gardenman. I don't think memory corruption has been suspected before in the minidumps. If anyone is interested there are several in the "old" folder in dropbox. Would that be RAM or one of my drives? Early on in troubleshooting this problem I reseated the RAM and drives as someone suggested. I have three 8 GB RAM sticks, two matching ones in paired slots and one that came with the machine that is of a different make.

I ran the windows memory diagnostic and it found no issues.
 
Last edited:
Sep 13, 2021
13
0
10
0
Well, still struggling with this issue. Data corruption has led to me being scared to use this machine for anything even semi-important. Nvidia dropped a new update so I cleaned with DDU and installed it as well as doing some Windows recommended updates and intel recommended updates including wifi 6 system. I also went through device manager and right-clicked on every single thing and asked it to look for an update. So I was hopeful. But no, crashed immediately next time I booted it up to use it. The minidump is here: https://www.dropbox.com/sh/1fdn2hcsfzvwu65/AABMSIongTOyu9rg8I1EIlw1a?dl=0

So I am thinking about deleting everything and starting with a fresh Windows 10 install. What do you guys think? Kind of a pain so do you think it will work?

Cheers
 

Colif

Win 10 Master
Moderator
Colif has been having bad weather for 2 weeks now and would love for it to end.
Thanks John, but I can't figure out what device that might be in device manager.
if its Intel WiFi 6, you could try running Intel updater - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html

if you have updated those already, a clean install might be the answer as it would at least force windows to get all new drivers. Its not the answer I go to right away.
 
looks like you have a 2019 intel chipset driver but you have the current bios with the acpi updates from late 2020.
file:
Nov 05 2019dptf_acpi.sys

update should be at
desktops and all in ones :: legion series :: legion t5 28imb05 - Lenovo Support US
dated in june 2020

if the bios has the new jan 2021 acpi specifications version changes
then the driver might fail to respond to a reading a port and end up with a timeout.

as a side note: when there are major spec changes to acpi as in jan 2021. you should get your driver update from the motherboard vendor rather than the generic driver from intel.
since the bios and driver version needs to match and mother board vendors will keep them in sync.
your bios is dated one month before the new acpi spec release.


acpi gives windows control of power functions rather than having the bios do the control. old drivers will not respond correctly if they are not in sync with the bios. make sure you get the updates to match your bios virsion from
Intel Chipset Driver for Windows 10 64-bit (Version 1909) - Legion T5-28IMB05 Desktop - Lenovo Support US

looks like they also had the updated intel wifi 6 driver that was need to fix the crash in the memory dump I looked at.
Intel Chipset Driver for Windows 10 64-bit (Version 1909) - Legion T5-28IMB05 Desktop - Lenovo Support US
 
Last edited:

ASK THE COMMUNITY