DPC_WATCHDOG_VIOLATION while gaming

TopSecretBSOD · Mar 19, 2025

When the card is under heavy load, whether gaming or running Salad, the PC crashes with a BSOD.

So far I have changed power management settings, DDUd multiple times, underclocked and god knows what else (TdrDelay = 8). The system was running well initially and then suddenly out of the blue. Errors. Sometimes I can play for 5 minutes, sometimes for hours. But it happens. Every time. It starts with sound stuttering and ends with a crash. Stress testing all drives did lead to nothing. Same for memory tests. I can trigger a crash with a DX12 GPU test most of the times.

The last two entries from the event viewer are:

Code:

The description for Event ID 153 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\Video3
UCodeReset TDR occurred on GPUID:100
The message resource is present but the message was not found in the message table

and

Code:

The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\Video13
0220694c 00000000 00000000 202a71ce 202a7338 00000000 00000000 00000000
The message resource is present but the message was not found in the message table

Min Dump points to: nvlddmkm

relevant files are in here:

BSOD - Google Drive

drive.google.com

I can provide more if necessary!

Thank you for your help

neves · Mar 19, 2025

How are the temperatures?

Do another clean install with DDU - using this older studio driver:

Driver Details | NVIDIA

Download the <dd~LanguageName> <dd~Name> for <dd~OSName> systems. Released <dd~ReleaseDateTime>

www.nvidia.com

Download GPU-Z Run it, click on Sensors and check Log To Filer (bottom left corner) - while selecting a destination like Desktop (wherever it's easier to find). And while it's running - try a game which used to cause BSOD.

Also, would recommend https://notepad-plus-plus.org/downloads/ to view the log file.

TopSecretBSOD · Mar 19, 2025

I have not DDUd yet, so this is from the current, most recent driver which was released yesterday.

While gaming:

During the time of crash:
Another thing I noticed is that there was audio stuttering during the crash.

I will install your suggested drivers tomorrow.

Thanks for the help

GPU-Z Log is in the initial google drive

zbook · Mar 20, 2025

The opening post did not report the use of WDV.

The opening post did not report recurrent drive file system corruption problems.

There were two misbehaving drivers.

1) Turn off WDV

2) If there are important files > back them up to another disk drive or the cloud > test the drives

3) Run Sea Tools Long generic test (all drives) > post images or share links

https://www.seagate.com/content/dam...ds/seatools/_shared/downloads/100869623_B.pdf

https://www.seagate.com/content/dam...shared/downloads/SeaToolsWindowsInstaller.exe

4) Run HD Tune (all drives) (run an old version so that it produces results for the whole drive)
HD Tune website
a) Health
b) Full error scan

5) Open administrative command prompt and copy and paste:

chkdsk /b /v

Run these chkdsk switches on all drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b /v E: etc.

Make sure that the windows drive runs overnight while sleeping.

C:\WINDOWS\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y

Reboot as needed.

6) After completing all chkdsk /b /v run:

https://www.tenforums.com/attachmen...-files-use-bsod-debugging-chkdskfromevent.bat

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

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

Make sure that this runs only after the prior three steps for each drive.

7) Run HD Sentinel (all drives) > post images or share links (do not run until posting results for each steps 5, 6, 7 and 8)

Hard Disk Sentinel - HDD health and temperature monitoring
a) Overview
b) Temperature
c) SMART

8) Please make sure that all of the above steps are performed in sequence

These steps / tests can be performed overnight while sleeping:
a) Memtest86+
b) Sea Tools Long generic test
c) HD Tune Full error scan
d) Chkdsk /b /v

Code:

Event[14294]
  Log Name: System
  Source: Ntfs
  Date: 2025-03-19T21:59:30.7360000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info 

  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: PC
  Description:
A corruption was discovered in the file system structure on volume C:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x1400000004069a.  The name of the file is "\$Extend\$Deleted\001400000004069A49187B44".
 

Event[14295]
  Log Name: System
  Source: Ntfs
  Date: 2025-03-19T21:59:30.7370000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info 

  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: PC
  Description:
A corruption was discovered in the file system structure on volume C:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x1200000004069b.  The name of the file is "\$Extend\$Deleted\001200000004069B49EE263E".
 

Event[14296]
  Log Name: System
  Source: Ntfs
  Date: 2025-03-19T21:59:30.7370000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info 

  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: PC
  Description:
A corruption was discovered in the file system structure on volume C:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x1000000004069c.  The name of the file is "\$Extend\$Deleted\001000000004069C66E4BC96".
 

Event[14297]
  Log Name: System
  Source: Ntfs
  Date: 2025-03-19T21:59:30.7370000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info 

  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: PC
  Description:
A corruption was discovered in the file system structure on volume C:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x1100000004069d.  The name of the file is "\$Extend\$Deleted\001100000004069D791FF7F1".
 

Event[14298]
  Log Name: System
  Source: Ntfs
  Date: 2025-03-19T21:59:30.7370000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info 

  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: PC
  Description:
A corruption was discovered in the file system structure on volume C:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x100000000406bc.  The name of the file is "\$Extend\$Deleted\00100000000406BC6484B82B".
 

Event[14299]
  Log Name: System
  Source: Ntfs
  Date: 2025-03-19T21:59:30.7370000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info 

  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: PC
  Description:
A corruption was discovered in the file system structure on volume C:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x180000000406c5.  The name of the file is "\$Extend\$Deleted\00180000000406C50FE042C8".
 

Event[14300]
  Log Name: System
  Source: Ntfs
  Date: 2025-03-19T21:59:30.7370000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info 

  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: PC
  Description:
A corruption was discovered in the file system structure on volume C:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0xf0000000406cd.  The name of the file is "\$Extend\$Deleted\000F0000000406CD5928301C".
 

Event[14301]
  Log Name: System
  Source: Ntfs
  Date: 2025-03-19T21:59:30.7380000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info 

  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: PC
  Description:
A corruption was discovered in the file system structure on volume C:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x180000000406ce.  The name of the file is "\$Extend\$Deleted\00180000000406CE065D3C0C".
 

Event[14302]
  Log Name: System
  Source: Ntfs
  Date: 2025-03-19T21:59:30.7380000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info 

  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: PC
  Description:
A corruption was discovered in the file system structure on volume C:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x140000000406cf.  The name of the file is "\$Extend\$Deleted\00140000000406CF25E61B9F".
 

Event[14303]
  Log Name: System
  Source: Ntfs
  Date: 2025-03-19T21:59:30.7380000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info 

  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: PC
  Description:
A corruption was discovered in the file system structure on volume C:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0xe0000000406da.  The name of the file is "\$Extend\$Deleted\000E0000000406DA0DB61EB4".

Code:

Event[6344]
  Log Name: Application
  Source: Microsoft-Windows-Wininit
  Date: 2025-03-19T22:03:46.9070000Z
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: PC
  Description:


Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.                         

Stage 1: Examining basic file system structure ...
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x130ed133 for possibly 0x1310 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x4068a is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x4068A.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x130e389f for possibly 0x1310 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x4068b is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x4068B.
  829184 file records processed.                                                       


File verification completed.
 Phase duration (File record verification): 3.60 seconds.
  19792 large file records processed.                                   


 Phase duration (Orphan file record recovery): 6.66 milliseconds.
  0 bad file records processed.                                     


 Phase duration (Bad file record checking): 0.48 milliseconds.

Stage 2: Examining file name linkage ...
  551 reparse records processed.                                     


Correcting error in index $I30 for file 1D.
Correcting error in index $I30 for file 1D.
Correcting error in index $I30 for file 1D.
Correcting error in index $I30 for file 1D.
The index bitmap $I30 in file 0x1d is incorrect.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 1D.
The two index entries of length 0x88 and 0x70 are either identical
or appear in the wrong order.
95 06 04 00 00 00 3e 00 88 00 72 00 00 00 00 00  ......>...r.....
1d 00 00 00 00 00 01 00 ec 60 16 b8 0b 99 db 01  .........`......
d1 a6 c2 61 10 99 db 01 d1 a6 c2 61 10 99 db 01  ...a.......a....
d1 a6 c2 61 10 99 db 01 00 70 31 01 00 00 00 00  ...a.....p1.....
44 6a 31 01 00 00 00 00 20 20 00 00 00 00 00 00  Dj1.....  ......
18 01 30 00 30 00 33 00 45 00 30 00 30 00 30 00  ..0.0.3.E.0.0.0.
30 00 30 00 30 00 30 00 34 00 30 00 36 00 39 00  0.0.0.0.4.0.6.9.
35 00 36 00 41 00 44 00 41 00 34 00 31 00 45 00  5.6.A.D.A.4.1.E.
44 00 16 b8 0b 99 db 01 ?? ?? ?? ?? ?? ?? ?? ??  D...............
----------------------------------------------------------------------
9c 06 04 00 00 00 10 00 70 00 52 00 01 00 00 00  ........p.R.....
1d 00 00 00 00 00 01 00 ec 60 16 b8 0b 99 db 01  .........`......
a5 64 c2 35 10 99 db 01 a5 64 c2 35 10 99 db 01  .d.5.....d.5....
a5 64 c2 35 10 99 db 01 00 70 31 01 00 00 00 00  .d.5.....p1.....
44 6a 31 01 00 00 00 00 20 20 00 00 00 00 00 00  Dj1.....  ......
08 02 30 00 30 00 31 00 30 00 30 00 30 00 7e 00  ..0.0.1.0.0.0.~.
33 00 30 00 30 00 30 00 01 00 00 00 00 00 00 00  3.0.0.0.........
Sorting index $I30 in file 1D.
Index entry 000202~1 of index $I30 in file 0x1d points to unused file 0x406aa.
Deleting index entry 000202~1 in index $I30 of file 1D.
The file reference 0x450000000406ce of index entry 0002FD~1 of index $I30
with parent 0x1d is not the same as 0x180000000406ce.
Deleting index entry 0002FD~1 in index $I30 of file 1D.
The file reference 0x47000000040696 of index entry 000FE4~1 of index $I30
with parent 0x1d is not the same as 0x14000000040696.
Deleting index entry 000FE4~1 in index $I30 of file 1D.
The file reference 0x1300000004068f of index entry 001300000004068F2BA17B72 of index $I30
with parent 0x1d is not the same as 0x3600000004068f.
Deleting index entry 001300000004068F2BA17B72 in index $I30 of file 1D.
The file reference 0x1300000004068f of index entry 001300~1 of index $I30
with parent 0x1d is not the same as 0x3600000004068f.
Deleting index entry 001300~1 in index $I30 of file 1D.
The file reference 0x410000000406b4 of index entry 002AA3~1 of index $I30
with parent 0x1d is not the same as 0x120000000406b4.
Deleting index entry 002AA3~1 in index $I30 of file 1D.
The file reference 0x3b00000004068b of index entry 003B00~4 of index $I30
with parent 0x1d is not the same as 0x2e00000004068b.
Deleting index entry 003B00~4 in index $I30 of file 1D.
The file reference 0x3c00000004068f of index entry 003C00000004068F3CDFEEBB of index $I30
with parent 0x1d is not the same as 0x3600000004068f.
Deleting index entry 003C00000004068F3CDFEEBB in index $I30 of file 1D.
The file reference 0x3c000000040694 of index entry 003C00000004069428D3651C of index $I30
with parent 0x1d is not the same as 0x14000000040694.
Deleting index entry 003C00000004069428D3651C in index $I30 of file 1D.
The file reference 0x3c00000004069a of index entry 003C00000004069A399EB00C of index $I30
with parent 0x1d is not the same as 0x1400000004069a.
Deleting index entry 003C00000004069A399EB00C in index $I30 of file 1D.
Index entry 003C0000000406AA441B9633 of index $I30 in file 0x1d points to unused file 0x406aa.
Deleting index entry 003C0000000406AA441B9633 in index $I30 of file 1D.
The file reference 0x3c0000000406ba of index entry 003C0000000406BA24F11068 of index $I30
with parent 0x1d is not the same as 0x140000000406ba.
Deleting index entry 003C0000000406BA24F11068 in index $I30 of file 1D.
The file reference 0x3c0000000406cb of index entry 003C0000000406CB76E99490 of index $I30
with parent 0x1d is not the same as 0x170000000406cb.
Deleting index entry 003C0000000406CB76E99490 in index $I30 of file 1D.
The file reference 0x3c00000004068f of index entry 003C00~1 of index $I30
with parent 0x1d is not the same as 0x3600000004068f.
Deleting index entry 003C00~1 in index $I30 of file 1D.
The file reference 0x3c0000000406ba of index entry 003C00~2 of index $I30
with parent 0x1d is not the same as 0x140000000406ba.
Deleting index entry 003C00~2 in index $I30 of file 1D.
Index entry 003C00~3 of index $I30 in file 0x1d points to unused file 0x406aa.
Deleting index entry 003C00~3 in index $I30 of file 1D.
The file reference 0x3c0000000406cb of index entry 003C00~4 of index $I30
with parent 0x1d is not the same as 0x170000000406cb.
Deleting index entry 003C00~4 in index $I30 of file 1D.
The file reference 0x3d000000040693 of index entry 003D000000040693796C5F27 of index $I30
with parent 0x1d is not the same as 0x14000000040693.
Deleting index entry 003D000000040693796C5F27 in index $I30 of file 1D.
The file reference 0x3d00000004069f of index entry 003D00000004069F1936D88A of index $I30
with parent 0x1d is not the same as 0x1500000004069f.
Deleting index entry 003D00000004069F1936D88A in index $I30 of file 1D.
The file reference 0x3d0000000406af of index entry 003D0000000406AF36578688 of index $I30
with parent 0x1d is not the same as 0x150000000406af.
Deleting index entry 003D0000000406AF36578688 in index $I30 of file 1D.
The file reference 0x3d0000000406ce of index entry 003D0000000406CE7CB149DE of index $I30
with parent 0x1d is not the same as 0x180000000406ce.
Deleting index entry 003D0000000406CE7CB149DE in index $I30 of file 1D.
The file reference 0x3d000000040693 of index entry 003D00~1 of index $I30
with parent 0x1d is not the same as 0x14000000040693.
Deleting index entry 003D00~1 in index $I30 of file 1D.
The file reference 0x3d0000000406af of index entry 003D00~2 of index $I30
with parent 0x1d is not the same as 0x150000000406af.
Deleting index entry 003D00~2 in index $I30 of file 1D.
The file reference 0x3d00000004069f of index entry 003D00~3 of index $I30
with parent 0x1d is not the same as 0x1500000004069f.
Deleting index entry 003D00~3 in index $I30 of file 1D.
The file reference 0x3d0000000406ce of index entry 003D00~4 of index $I30
with parent 0x1d is not the same as 0x180000000406ce.
Deleting index entry 003D00~4 in index $I30 of file 1D.
The file reference 0x3e000000040692 of index entry 003E0000000406922919CF17 of index $I30
with parent 0x1d is not the same as 0x15000000040692.
Deleting index entry 003E0000000406922919CF17 in index $I30 of file 1D.
The file reference 0x3e000000040695 of index entry 003E0000000406956ADA41ED of index $I30
with parent 0x1d is not the same as 0x16000000040695.
Deleting index entry 003E0000000406956ADA41ED in index $I30 of file 1D.
The file reference 0x220000000406b8 of index entry NVLOG~1.NVL of index $I30
with parent 0x2088e is not the same as 0x120000000406b8.
Deleting index entry NVLOG~1.NVL in index $I30 of file 2088E.
  1154066 index entries processed.                                                       


Index verification completed.
 Phase duration (Index verification): 9.97 seconds.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file 02C600~1 (A650) into directory file 1D.
Recovering orphaned file 02C600000000A6503EE82C90 (A650) into directory file 1D.
Recovering orphaned file 00FE00~1 (3FD1A) into directory file 1D.
Recovering orphaned file 00FE00000003FD1A03139225 (3FD1A) into directory file 1D.
Recovering orphaned file 009A00~1 (40613) into directory file 1D.
Recovering orphaned file 009A00000004061310CD2CDD (40613) into directory file 1D.
Recovering orphaned file 00B000~1 (4061B) into directory file 1D.
Recovering orphaned file 00B000000004061B12DB4DDC (4061B) into directory file 1D.
Recovering orphaned file 002200~1 (40633) into directory file 1D.
Recovering orphaned file 002200000004063307CBAF92 (40633) into directory file 1D.
Skipping further messages about recovering orphans.
  54 unindexed files scanned.                                       


  54 unindexed files recovered to original directory.
 Phase duration (Orphan reconnection): 965.66 milliseconds.
  0 unindexed files recovered to lost and found.                   


 Phase duration (Orphan recovery to lost and found): 3.73 milliseconds.
  551 reparse records processed.                                     


 Phase duration (Reparse point and Object ID verification): 3.93 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 74 unused index entries from index $SII of file 0x9.
Cleaning up 74 unused index entries from index $SDH of file 0x9.
Cleaning up 74 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 18.66 milliseconds.
Inserting data attribute into file 4068A.
Inserting data attribute into file 4068B.
  162444 data files processed.                                           


 Phase duration (Data attribute verification): 1.69 milliseconds.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

1953497087 KB total disk space.
1103786016 KB in 521063 files.
    396228 KB in 162443 indexes.
         0 KB in bad sectors.
    960027 KB in use by the system.
     65536 KB occupied by the log file.
 848354816 KB available on disk.

      4096 bytes in each allocation unit.
 488374271 total allocation units on disk.
 212088704 allocation units available on disk.
Total duration: 14.59 seconds (14597 ms).

Internal Info:
00 a7 0c 00 e8 6d 0a 00 5d 11 12 00 00 00 00 00  .....m..].......
03 01 00 00 24 01 00 00 00 00 00 00 00 00 00 00  ....$...........

Code:

Event[598]
  Log Name: Application
  Source: Microsoft-Windows-Wininit
  Date: 2025-02-20T10:46:50.0070000Z
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: PC
  Description:


Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.                         

Stage 1: Examining basic file system structure ...
Cleaning up instance tags for file 0x20e69.
  829184 file records processed.                                                       


File verification completed.
 Phase duration (File record verification): 6.25 seconds.
  23193 large file records processed.                                   


 Phase duration (Orphan file record recovery): 7.90 milliseconds.
  0 bad file records processed.                                     


 Phase duration (Bad file record checking): 0.51 milliseconds.

Stage 2: Examining file name linkage ...
  555 reparse records processed.                                     


The file reference 0x9400000004b5f8 of index entry 009400000004B5F800F24F44 of index $I30
with parent 0x1d is not the same as 0x9600000004b5f8.
Deleting index entry 009400000004B5F800F24F44 in index $I30 of file 1D.
The file reference 0x9400000004b5f8 of index entry 009400~1 of index $I30
with parent 0x1d is not the same as 0x9600000004b5f8.
Deleting index entry 009400~1 in index $I30 of file 1D.
  1155034 index entries processed.                                                       


Index verification completed.
 Phase duration (Index verification): 19.66 seconds.
CHKDSK is scanning unindexed files for reconnect to their original directory.
  1 unindexed files scanned.                                       


Recovering orphaned file 009600~1 (4B5F8) into directory file 1D.
Recovering orphaned file 009600000004B5F840D2EA60 (4B5F8) into directory file 1D.
  1 unindexed files recovered to original directory.
 Phase duration (Orphan reconnection): 959.29 milliseconds.
  0 unindexed files recovered to lost and found.                   


 Phase duration (Orphan recovery to lost and found): 1.45 seconds.
  555 reparse records processed.                                     


 Phase duration (Reparse point and Object ID verification): 3.97 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 689 unused index entries from index $SII of file 0x9.
Cleaning up 689 unused index entries from index $SDH of file 0x9.
Cleaning up 689 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 19.49 milliseconds.
  162926 data files processed.                                           


 Phase duration (Data attribute verification): 0.58 milliseconds.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

1953497087 KB total disk space.
 966048140 KB in 564595 files.
    417096 KB in 162927 indexes.
         0 KB in bad sectors.
    961515 KB in use by the system.
     65536 KB occupied by the log file.
 986070336 KB available on disk.

      4096 bytes in each allocation unit.
 488374271 total allocation units on disk.
 246517584 allocation units available on disk.
Total duration: 28.49 seconds (28493 ms).

Internal Info:
00 a7 0c 00 d6 19 0b 00 a2 19 13 00 00 00 00 00  ................
03 01 00 00 28 01 00 00 00 00 00 00 00 00 00 00  ....(...........

neves · Mar 20, 2025

For couple of driver versions up till now (while preparing for the release of RTX 5xxx) - there have been multiple reports of driver issues with Nvidia drivers - including BSOD (like yours). There seems to be a higher chance of occurrence for High End GPUs (like 4090) - based on the public reports. Above version (especially the Studio version) - shouldn't have this issue -but you'll have to do clean this recent driver installs with DDU - before installing that one. So hey, that way you'll know for sure - if the BSOD is caused by recent drivers or something else.

TopSecretBSOD · Mar 20, 2025

I created a full dump for Nvidia multiple times over the last few months, but nothing came back after the initial communication with them.

TopSecretBSOD · Mar 20, 2025

1.) Done
2.) Done
3.)

4.) Pending

@neves

I will DDU it once again when I am done with all those tests. Thank you

neves · Mar 20, 2025

Nvidia doesn't offer direct support (as far as I'm aware) - but if same issue is reported by multiple nvidia GPU users - they do seem to take into account (trying to solve that issue - with the upcoming drivers).

Anyway, i doubt you'll find any issue running all this tests - since the recent crash dumbs are tied to Nvidia GPU (and its drivers/software). While the older ones from 2024 - seem to be tied to the Realtek Ethernet Adapter (or at least that's what triggered it). Did you updated those drivers as well? Cause I see - you have the latest BIOS updated - so maybe, coincidentally - you solved those with that update - and shortly after - you bumped into the Nvidia driver issues...

Just for the sake of troubleshooting - would also recommend disabling EasyTuneEngineService - but first activate Smart Fan from BIOS - since disabling this service - will interfere with Q-Fan control (from Windows).

Would also uninstall Easeware DriverEasy - since this types of apps are a really bad idea, a main cause for random BSOD.

This days, a lot of apps - are set to have an active presence (even if you use them actively or not) - by being set to Auto-Start with Windows. Would Disable the ones you don't actually use - or need - actively. Even tho, you have capable hardware - they're troublesome in the long run (as can be seen - among your error reports).

TopSecretBSOD · Mar 20, 2025

I too doubt that my hard drives are having issues. Checked them multiple times before and there also no other issues outside of gaming or running other GPU high-intensity things. I just don't want to be uncooperative with people who are trying to help,

It took me a while to figure out that I have to update all the Realtek stuff through Device Manager rather than running their official .exe, which was crashing the PC as well. I updated them but only a few days ago. I saw it in the logs, and LatencyMon also hints at it. I updated Bios the other day and then all the RealTek stuff I could find. BSOD is still happening.

This is with Audio coming via BT on my Bose QC35.

And there is also the audio stuttering before the BSOD.

What would "disabling EasyTuneEngineService" do?
The rest is off in autostart and I have not used DriverEasy in some time. Especially GPU related stuff was always updated through NVIDIA App.

TopSecretBSOD · Mar 20, 2025

The results from the .bat file are in the original drive folder!

Some corrupt files here and there, but IMHO all in all the drives look ok.

TopSecretBSOD · Mar 20, 2025

@neves

I DDUd and installed your driver. The following was the result:

If I remember correctly, I was able to crash the PC with BSOD on the old drivers when running 3D Mark with a DX12 test. Can try tomorrow if necessary.

zbook · Mar 20, 2025

The latest chkdsk were good.

Was HD Tune run or was it skipped?

1) Create a new restore point

Create System Restore Point in Windows 11

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

2) Learn the methods to recover from BSOD caused by WDV by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail

Boot to Advanced Startup (WinRE) in Windows 11

This tutorial will show you how to boot to the advanced startup (WinRE) in Windows 11. The Windows Recovery Environment (WinRE) is a companion operating system installed alongside Windows 11, typically in a separate partition, that can help with troubleshooting, recovery, or booting from...

www.elevenforum.com

3) Plan to run the tool with various customized test settings.

a) Test all non-Microsoft drivers

b) Test no Microsoft drivers

4) Whenever the WDV tool is started if there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

Customized tests will then be posted for the next run of WDV.

WDV can run continuously during the testing.

For any BSOD post a new V2 share link into the newest post.

Please restart WDV with these three groups of customized tests:

Group 1
[ ] 0x00000010 I/O verification.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.

Group 2
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[ ] 0x00020000 DDI compliance checking.
[ ] 0x00080000 DDI compliance checking (additional).

Group 3
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

For each group post either a verifier /querysettings or V2 share link into the newest post.

Scannerman · Mar 21, 2025

neves said:
Nvidia doesn't offer direct support (as far as I'm aware) - but if same issue is reported by multiple nvidia GPU users - they do seem to take into account (trying to solve that issue - with the upcoming drivers).

Anyway, i doubt you'll find any issue running all this tests - since the recent crash dumbs are tied to Nvidia GPU (and its drivers/software). While the older ones from 2024 - seem to be tied to the Realtek Ethernet Adapter (or at least that's what triggered it). Did you updated those drivers as well? Cause I see - you have the latest BIOS updated - so maybe, coincidentally - you solved those with that update - and shortly after - you bumped into the Nvidia driver issues...

Sure. This is common. Practically the norm.

neves said:
Just for the sake of troubleshooting - would also recommend disabling EasyTuneEngineService - but first activate Smart Fan from BIOS - since disabling this service - will interfere with Q-Fan control (from Windows).

Yep

neves said:
Would also uninstall Easeware DriverEasy - since this types of apps are a really bad idea, a main cause for random BSOD.

This days, a lot of apps - are set to have an active presence (even if you use them actively or not) - by being set to Auto-Start with Windows. Would Disable the ones you don't actually use - or need - actively. Even tho, you have capable hardware - they're troublesome in the long run (as can be seen - among your error reports).

Yes. All too often these third party driver apps are a pain. Many of these will throw random beta drivers at your hardware when its the last thing you need. You are always better off sticking with the driver selected for your hardware by the manufacturer and getting it directly from that manufacturer. VOE.

NVIDIA lets you do clean uninstalls of your GFX drivers with their own driver app but you must register your hardware with them in order to run that app correctly. Anyone who would fork out that much cash for a 4090 should be willing to comply with this. Also in the event that you get some third party driver for your graphics card it may not uninstall so easily and traces of the old, unwanted driver could be floating around like orphaned files just waiting for the opportunity to re-attach themselves where they are not needed.

A spring cleaning could be in order.

neves · Mar 21, 2025

TopSecretBSOD said:
@neves

I DDUd and installed your driver. The following was the result:

View attachment 129012

If I remember correctly, I was able to crash the PC with BSOD on the old drivers when running 3D Mark with a DX12 test. Can try tomorrow if necessary.

To be expected, since this game takes into account driver based profiles - and was released on October 25, 2024 - while above driver was released on Oct 15, 2024. The thing is - was intentionally looking for an older driver - prior any of this driver related issues plaguing High End Nvidia GPUs. Thus, if you can't recreate a nvidia driver related BSOD (like the last crash reports) - than it was the drivers causing it. If still happens - then we can try other stuff.

neves · Mar 21, 2025

Scannerman said:
Yes. All too often these third party driver apps are a pain. Many of these will throw random beta drivers at your hardware when its the last thing you need. You are always better off sticking with the driver selected for your hardware by the manufacturer and getting it directly from that manufacturer. VOE.

They also throw - Drivers custom made by a different OEM - for slightly different hardware configuration - while using the same chip (thus, the similarity in Hardware ID). Even if you don't get a BSOD - they can still cause all kinds of issues (for example: sound drivers - not working when waking up from sleep mode or not detecting attached device).

With GPU or Ethernet drivers - the manufacturer (Nvidia , AMD or Intel) - is usually a safe bet (current issues with Nvidia drivers - tend to be an exception from the norm - but proof that it can happen). But with Sound chips - the OEM (just not any OEM) - is usually what works best (even here - with rare exceptions).

TopSecretBSOD · Mar 21, 2025

Regarding Nvidia and their support. I got hold of their support through work channels. But that was a few releases back. I was expecting them to pay attention to the last gen cards after having people pay 2k for them.

Could it be, that the DX issue takes too long to recover on the newer drivers and hence the violation?

TopSecretBSOD · Mar 21, 2025

I had salad running with the new driver and blasting at 100% load. But no crash.
I am unsure about the memory temperature and am thinking about replacing the pads on the card at some point.

DPC_WATCHDOG_VIOLATION while gaming

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Member

My Computer

Member

My Computer

Similar threads