DPC_WATCHDOG_VIOLATION happening after extended use after woken from sleep

adamk33n3r · Aug 31, 2023

I've been plagued with this BSOD for months now. It seems to happen after the computer has woken up from sleep. Generally, it is hours afterwards while gaming, but I have had it a couple times within a couple minutes of waking up. If the computer has been started from a fresh boot, I haven't gotten any crashes. Even after running for 10+ hours. But if it's started from sleep, it often crashes if it runs for a while. I have looked at the minidumps and they generally reference applications that use the graphics card, games, or otherwise hardware accelerated applications. Looking up the stop code, everything online says it's a driver issue so I have updated all of my drivers. No dice. I thought maybe there was an issue with the card so I RMA'd it since it was still under warranty but that didn't help either. Does anyone know what I should be looking for?

V2 Log

VICTORIA-(2023-08-31_18-57-51).zip

drive.google.com

I have also attached the most recent minidump file.

x BlueRobot · Aug 31, 2023

Could you please zip up and provide the following file:

Code:

%systemroot%\MEMORY.DMP

It will be too large to attach to a forum post so please upload it to your Google Drive. You can't really debug Stop 0x133 bugchecks without a kernel memory dump.

adamk33n3r · Sep 1, 2023

x BlueRobot said:
Could you please zip up and provide the following file:

Code:

%systemroot%\MEMORY.DMP

It will be too large to attach to a forum post so please upload it to your Google Drive. You can't really debug Stop 0x133 bugchecks without a kernel memory dump.

Oh geeze ok, it's 32 gigabytes. Good thing I have extra storage on there. I'll get back with you tomorrow, thank you for the response.

zbook · Sep 1, 2023

Please perform the following steps:

1) Run: Tuneup plus > post a share link using one drive, drop box, or google drive

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

2) Uninstall and reinstall these drivers:

a) nvrtxvad_waveextensible NVIDIA Broadcast c:\windows\system32\drivers\nvrtxvad64v.sys

b) e60mz0380.x64 Game Capture HD60 Pro Service c:\windows\system32\drivers\e60mz0380.x64.sys

Elgato

A leader in audiovisual technology for creators and WFH pros, Elgato builds premium webcams, microphones, Stream Deck controllers, capture cards, and more.

www.elgato.com

c) nvlddmkm nvlddmkm c:\windows\system32\driverstore\filerepository\nv_dispig.inf_amd64_1ddf203f8d876fdf\nvlddmkm.sys (31.0.15.3699, 56.39 MB (59,131,512 bytes), 8/15/2023 7:37 PM)

For the Nvidia GPU uninstall using DDU and reinstall using the Nvidia website:

Display Driver Uninstaller: How to use

How to Use Display Driver Uninstaller to Uninstall any Installed Display Driver

www.sevenforums.com

Display Driver Uninstaller (DDU) download latest version 18.0.7.6

Official Display Driver Uninstaller (DDU) download website. DDU is a driver removal utility that can help you completely uninstall AMD/NVIDIA/INTEL graphics card drivers and packages from your system, trying to remove all leftovers (including registry keys, folders and files, driver store).

www.wagnardsoft.com

Download the latest official NVIDIA drivers

www.nvidia.com

Name NVIDIA Broadcast
Manufacturer NVIDIA
Status OK
PNP Device ID ROOT\UNNAMED_DEVICE\0000
Driver C:\WINDOWS\SYSTEM32\DRIVERS\NVRTXVAD64V.SYS (1.0.1.9, 57.51 KB (58,888 bytes), 1/14/2023 1:42 AM)

Name Game Capture HD60 Pro
Manufacturer Elgato
Status OK
PNP Device ID PCI\VEN_12AB&DEV_0380&SUBSYS_00031CFA&REV_00\6&8FB0788&0&0018000A
Memory Address 0xF8000000-0xF9FFFFFF
Memory Address 0xFA0FF000-0xFA0FFFFF
IRQ Channel IRQ 31
Driver C:\WINDOWS\SYSTEM32\DRIVERS\E60MZ0380.X64.SYS (1.1.0.195, 3.72 MB (3,896,880 bytes), 10/7/2021 1:25 AM)

Name NVIDIA GeForce RTX 3080
PNP Device ID PCI\VEN_10DE&DEV_2216&SUBSYS_48973842&REV_A1\4&31AC7A68&1&0019
Adapter Type NVIDIA GeForce RTX 3080, NVIDIA compatible
Adapter Description NVIDIA GeForce RTX 3080
Adapter RAM (1,048,576) bytes
Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_1ddf203f8d876fdf\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_1ddf203f8d876fdf\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_1ddf203f8d876fdf\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_1ddf203f8d876fdf\nvldumdx.dll
Driver Version 31.0.15.3699
INF File oem84.inf (Section139 section)
Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPIG.INF_AMD64_1DDF203F8D876FDF\NVLDDMKM.SYS (31.0.15.3699, 56.39 MB (59,131,512 bytes), 8/15/2023 7:37 PM)

C00002C4

ubuysa · Sep 1, 2023

It's up to @x BlueRobot of course, and he might disagree with me, but I wouldn't upload that dump. It's a complete memory dumps (which we don't need) and will take an age to upload and download.

Can you please enter the command sysdm.cpl at the Run command prompt, click the Advanced tab and then click the bottom Settings button (in the Start-up and Recovery section). Use the 'Write debugging information' pull-down menu to select 'Automatic memory dump'. That will create a kernel dump of between 1GB and 2GB typically. Also please ensure that your paging file is set to 'System managed'.

Unfortunately you'll then have to wait for another DPC_WATCHDOG_VIOLATION bugcheck to occur. As soon as you get one upload the C:\Windows\Memory.dmp file to the cloud with a link to it here (be sure to make it public).

x BlueRobot · Sep 1, 2023

ubuysa said:
It's up to @x BlueRobot of course, and he might disagree with me, but I wouldn't upload that dump. It's a complete memory dumps (which we don't need) and will take an age to upload and download.

No I agree with you, if it is a complete memory dump then the additional size isn't going to add any value to our debugging efforts and it will potentially take a long time to upload/download, I think even WinDbg might struggle loading it as well.

If you set your crash dump settings to Automatic like @ubuysa suggested, then your machine will produce both Minidumps and a single kernel memory dump. You can either update the settings using the GUI as suggested or you can update them from CMD using the following command:

Code:

reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl /v CrashDumpEnabled /t REG_DWORD /d 0x7 /f

Unfortunately, as already mentioned, it does mean that we will have to wait until another Stop 0x133 crash has occurred.

I would also look into updating or removing your Game Capture card driver as @zbook suggested, as it did seem to cause a Stop 0xD1 crash on the 11/08/2023, however, all the other bugchecks are Stop 0x133 so there is likely chance that you might have other problematic drivers too.

adamk33n3r · Sep 1, 2023

x BlueRobot said:
Could you please zip up and provide the following file:

Code:

%systemroot%\MEMORY.DMP

It will be too large to attach to a forum post so please upload it to your Google Drive. You can't really debug Stop 0x133 bugchecks without a kernel memory dump.

Ok here is the memory.dmp file! Thank you!

MEMORY_DMP.zip

drive.google.com

adamk33n3r · Sep 1, 2023

Oh, the page hadn't loaded the responses until after I made the post. Too late now! lol. At least the zipped file is only 20gb.

adamk33n3r · Sep 1, 2023

x BlueRobot said:
No I agree with you, if it is a complete memory dump then the additional size isn't going to add any value to our debugging efforts and it will potentially take a long time to upload/download, I think even WinDbg might struggle loading it as well.

If you set your crash dump settings to Automatic like @ubuysa suggested, then your machine will produce both Minidumps and a single kernel memory dump. You can either update the settings using the GUI as suggested or you can update them from CMD using the following command:

Code:

reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl /v CrashDumpEnabled /t REG_DWORD /d 0x7 /f

Unfortunately, as already mentioned, it does mean that we will have to wait until another Stop 0x133 crash has occurred.

I would also look into updating or removing your Game Capture card driver as @zbook suggested, as it did seem to cause a Stop 0xD1 crash on the 11/08/2023, however, all the other bugchecks are Stop 0x133 so there is likely chance that you might have other problematic drivers too.

Ok I will wait until I get another crash, sorry about that. Also I didn't see anything from a @zbook, but do you mean the elgato capture card I have? I've never gotten a 0xD1 so maybe it's a non issue for me. But I'll report back once I get another crash and dump.

zbook · Sep 1, 2023

See post #4.

Which components were RMA?

Was RAM or GPU tested or replaced?

adamk33n3r · Sep 1, 2023

zbook said:
See post #4.

Which components were RMA?

Was RAM or GPU tested or replaced?

Oh weird it wasn't showing that but I do now see it. I just replaced the GPU. Have not replaced or tested the RAM.

zbook · Sep 1, 2023

Tuneup plus will check and optimize the computer settings.

adamk33n3r · Sep 1, 2023

zbook said:
Tuneup plus will check and optimize the computer settings.

Here is the output from that

Code:

Microsoft Windows 11 Pro  Version 22H2 (OS Build 22621.2134)
 
==================================================================


    Started on Fri 09/01/2023 at 14:21:07.75
    
        [SFC /ScanNow]
    
Beginning system scan.  This process will take some time.


Results:
 
Windows Resource Protection did not find any integrity violations.
 
==================================================================


    Started on Fri 09/01/2023 at 14:27:48.31


        [DISM /online /cleanup-image /ScanHealth]


Deployment Image Servicing and Management tool
Version: 10.0.22621.1


Image Version: 10.0.22621.2134
 
No component store corruption detected.


The operation completed successfully.
 
==================================================================


    Started on Fri 09/01/2023 at 14:35:30.48


        [DISM /online /cleanup-image /RestoreHealth]


Deployment Image Servicing and Management tool
Version: 10.0.22621.1


Image Version: 10.0.22621.2134
 
The restore operation completed successfully.


The operation completed successfully.
 
==================================================================


The second "SFC /ScanNow" was skipped, as the first output the following:


Windows Resource Protection did not find any integrity violations.
 
==================================================================


    Started on Fri 09/01/2023 at 14:37:56.81


        [ChkDsk /Scan] 
 
The type of the file system is NTFS.
 
Stage 1: Examining basic file system structure ...
3429120 file records processed.                                                       
File verification completed.
Phase duration (File record verification): 38.36 seconds.
39758 large file records processed.                                   
Phase duration (Orphan file record recovery): 21.05 milliseconds.
0 bad file records processed.                                     
Phase duration (Bad file record checking): 0.05 milliseconds.
 
Stage 2: Examining file name linkage ...
139036 reparse records processed.                                     
4157592 index entries processed.                                                       
Index verification completed.
Phase duration (Index verification): 1.86 minutes.
0 unindexed files scanned.                                       
Phase duration (Orphan reconnection): 1.92 minutes.
0 unindexed files recovered to lost and found.                   
Phase duration (Orphan recovery to lost and found): 0.35 milliseconds.
139036 reparse records processed.                                     
Phase duration (Reparse point and Object ID verification): 324.56 milliseconds.
 
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 71.66 milliseconds.
364237 data files processed.                                           
Phase duration (Data attribute verification): 0.13 milliseconds.
CHKDSK is verifying Usn Journal...
40832000 USN bytes processed.                                                           
Usn Journal verification completed.
Phase duration (USN journal verification): 201.88 milliseconds.


Windows has scanned the file system and found no problems.


No further action is required.
 
1999030271 KB total disk space.
1876041872 KB in 2486141 files.
1278236 KB in 364238 indexes.
0 KB in bad sectors.
3610123 KB in use by the system.
65536 KB occupied by the log file.
118100040 KB available on disk.
 
4096 bytes in each allocation unit.
499757567 total allocation units on disk.
29525010 allocation units available on disk.
Total duration: 4.44 minutes (266606 ms).
 
==================================================================
 
    Started on Fri 09/01/2023 at 14:42:38.97
 
AutoReboot   
 
TRUE       
 
==================================================================
 
        [Set AutoReboot = False]
 
Updating property(s) of '\\VICTORIA\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.
==================================================================
 
AutoReboot   
 
FALSE       
 
==================================================================
 
DebugInfoType   
 
7             
 
==================================================================


        [Set DebugInfoType = 7]


Updating property(s) of '\\VICTORIA\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.
==================================================================
 
DebugInfoType   
 
7             
 
==================================================================


        [WMIC PageFile list]


AllocatedBaseSize=34816
CurrentUsage=159
Description=C:\pagefile.sys
InstallDate=20191206075137.947821-300
Name=C:\pagefile.sys
PeakUsage=163
Status=
TempPageFile=FALSE
 
==================================================================
 
AutomaticManagedPagefile   
 
TRUE                     
 
==================================================================


        [Set AutomaticManagedPagefile = True]


Updating property(s) of '\\VICTORIA\ROOT\CIMV2:Win32_ComputerSystem.Name="VICTORIA"'
Property(s) update successful.
==================================================================
 
AutomaticManagedPagefile   
 
TRUE                     
 
==================================================================


        [BcdEdit /enum {badmemory}]


RAM Defects
-----------
identifier              {badmemory}
 
==================================================================


    Finished on Fri 09/01/2023 at 14:42:41.51
    It took 21 minutes and 34 seconds to complete the operations.

x BlueRobot · Sep 1, 2023

adamk33n3r said:
I've never gotten a 0xD1 so maybe it's a non issue for me. But I'll report back once I get another crash and dump.

There was only one Stop 0xD1 crash and it was for the video capture card you mentioned, all the other crashes have been Stop 0x133 though. I've been trying to download your dump file, 4th attempt now, it gets around half way and then just decides to stop!

adamk33n3r · Sep 1, 2023

x BlueRobot said:
There was only one Stop 0xD1 crash and it was for the video capture card you mentioned, all the other crashes have been Stop 0x133 though. I've been trying to download your dump file, 4th attempt now, it gets around half way and then just decides to stop!

Oh I didn't know it could have more information like that, I guess I missed it! That's unfortunate, but I hope (sounds weird to say haha) that I get another crash soon so I can get you a smaller file.

zbook · Sep 1, 2023

Looks good.

After completing the steps in post #4 monitor the computer using Reliability monitor.

View Reliability History in Windows 11 Tutorial

This tutorial will show you how to view reliability history for your Windows 11 device. The Reliability Monitor provides a system stability overview and details about events that impact reliability. It calculates the Stability Index shown in the System Stability Chart. Reliability Monitor...

www.elevenforum.com

There were 5 types of BSOD dump files and one may be related to malfunctioning RAM.

If there is downtime this weekend test RAM using Memtest86: 4 passes

It can run overnight while sleeping.

Take pictures > post images or share links

MemTest86 - Official Site of the x86 Memory Testing Tool

MemTest86 is the original self booting memory testing software for x86 and ARM computers. Supporting both BIOS and UEFI, with options to boot from USB.

www.memtest86.com

adamk33n3r · Sep 9, 2023

Update here, after doing a clean install of my gpu driver and also uninstalling the 3 drivers mentioned (didn't re-install yet). I've not had a crash in a week, using sleep every day!

zbook · Sep 9, 2023

Please post a new V2 share link into the newest post.

adamk33n3r · Sep 13, 2023

VICTORIA-(2023-09-13_18-46-40).zip

drive.google.com

zbook · Sep 13, 2023

The log files reported no BSOD or unexpected shutdowns and restarts since 08/31/2023.

Today is 09/13/2023.

That's terrific.

Glad to help.

You're welcome.