BSOD Issues for the Past Couple of Days - Windows 10 - Version 21H2

A few months ago I was experiencing BSOD issues, 2 over the course of about 2 days. I posted a thread here but managed to remedy the issue by running the System File Checker and repairing a corrupted system file. Yesterday I experienced the first crash since then and ran the WhoCrashed diagnostic which found the KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL in the bug check. I experienced another crash today and ran WhoCrashed again and found the SYSTEM_SERVICE_EXCEPTION bug check with the afd.sys driver or module in which the error occured. Any help is appreciated, thanks.

The SYSTEM_SERVICE_EXCEPTION bugcheck is almost certainly due to an outdated version of the Realtek network driver rt640x64.sys. The stack trace shows a networking operation in progress and rt640x64.sys is the only third-party driver called.

The version you have installed is old...

Code:

1: kd> lmDvmrt640x64
Browse full module list
start             end                 module name
fffff806`475f0000 fffff806`47706000   rt640x64 T (no symbols)           
    Loaded symbol image file: rt640x64.sys
    Image path: \SystemRoot\System32\drivers\rt640x64.sys
    Image name: rt640x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue May 26 11:25:13 2020 (5ECCD269)
    CheckSum:         0012323A
    ImageSize:        00116000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I would look for an update, either via Windows Update or your motherboard vendor's website.

The KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL bugcheck is not so clear-cut. The stack trace shows that some sort of inter-process messaging was taking place, but there is no indication of what components were involved. I don't believe in having two issues at the same time, so I would update the rt604x64.sys driver and see how things do.

The logs reported problems with a disk drive.



1) Run:

https://www.tenforums.com/attachment...p_plus_log.bat

Post a share link into this thread using one drive, drop box, or google drive.


2) Run HD Tune: (free or trial version) (all drives)
HD Tune website
Post images for results on these tabs:
a) Health
b) Benchmark
c) Full error scan



3) Run Sea Tools for Windows (all drives)
https://www.seagate.com/content/dam/...00869623_B.pdf
https://www.seagate.com/content/dam/...sInstaller.exe
Post images or share links displaying the results of the Long Generic Test



4) These tests can run overnight while sleeping:
a) HD Tune Full Error Scan
b) Sea Tools for Windows Long Generic Test




5) The BIOS: Version/Date American Megatrends Inc. 3001, 12/4/2020

Upgrade the BIOS: 3001 > 4602

PRIME X570-P｜Motherboards｜ASUS Global



6) After completing all of the above steps please open administrative command prompt and type or copy and paste:

chkdsk /b /v

Run these chkdsk switches on all disk drives using the syntax:

chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b /v E:, etc.

These chkdsk switches can take significant time so make sure that the Windows drive is run 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 need.

When all chkdsk switches have completed on all disk drives please run:

https://www.tenforums.com/attachment...kfromevent.bat

Post a share link into this thread using one drive, drop box, or google drive.

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 45.0 GB
Total Space: 953.2 GB
File System: NTFS
      Model: Samsung SSD 970 EVO 1TB

      Drive: D:
 Free Space: 5.0 GB
Total Space: 1907.7 GB
File System: NTFS
      Model: WDC WD20EARX-00PASB0

      Drive: E:
 Free Space: 0.2 GB
Total Space: 5723.0 GB
File System: NTFS
      Model: WDC WD60EZRZ-00GZ5B1

      Drive: F:
 Free Space: 0.3 GB
Total Space: 1907.6 GB
File System: NTFS
      Model: WDC WD2003FZEX-00Z4SA0

Tried updating the Ethernet drivers, the GPU driver, and the BIOS and still crashed.DESKTOP-CVJ9NOT-(2023-03-25_12-39-48).zip

When available update the progress with the steps in post #3.

Please post images or share links for each test result.

The most recent dump tends to match with what @zbook was saying earlier about storage drives. The driver that tripped the DPC watchdog was storport.sys, which is the Windows storage driver...

Code:

1: kd> !dpx
Start memory scan  : 0xffff908135de3e18 ($csp)
End memory scan    : 0xffff908135de4000 (ISR Stack Base)

0xffff908135de3e40 : 0xfffff8034c2fb320 : nt!KeDpcWatchdogProfileGlobalTriageBlock
0xffff908135de3e48 : 0xfffff8034bb1c66e : nt!KiConvertDynamicHeteroPolicy+0x1e
0xffff908135de3e78 : 0xfffff8034b928333 : nt!KeClockInterruptNotify+0x453
0xffff908135de3ea0 : 0xffff908135de3e00 : 0xfffff8034c2fb320 : nt!KeDpcWatchdogProfileGlobalTriageBlock
0xffff908135de3f28 : 0xfffff8034b927e1a : nt!HalpTimerClockIpiRoutine+0x1a
0xffff908135de3f40 : 0xfffff80350651500 : storport!RaidpAdapterDpcRoutine+0x1c0
0xffff908135de3f58 : 0xfffff8034b873e05 : nt!KiCallInterruptServiceRoutine+0xa5
0xffff908135de3fa8 : 0xfffff8034b9fc0aa : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
0xffff908135de3fd8 : 0xfffff8034b9fc877 : nt!KiInterruptDispatchNoLockNoEtw+0x37

The storport.sys driver isn't the root cause however, because it's a Microsoft driver. The function being called is interesting though; it's the RaidpAdapterDpcRoutine function. By looking at your drive configuration you're not running a RAID array so I'm wondering what this function call might be for? It's certainly the long-running DPC that caused this BSOD.

Do you have a RAID setup by mistake perhaps?

I've run diagnostics on all of my drives and found that one my storage drives had bad blocks so I disconnected it from my system, still crashing though. I ran a system file check, no integrity issues. I ran extensive diagnostics on my RAM and found one module was faulty so I removed it, still crashing. Neither my GPU nor my CPU have been showing symptoms of being faulty so it seems to be a driver issue but I don't know which one it might be.

First things first; you say you've removed one (faulty) RAM stick, yet in the 1st April dump there are still two RAM cards installed. However, the RAM installed on 1st April is different from the RAM that was installed in your previous file collection upload?

The only third-party driver on the call stack for the 1st April dump is the Nvidia graphics driver nvlddmkm.sys...

Code:

fffffc03`22e64988  ffffcc8e`d2012e80
fffffc03`22e64990  00000000`00000000
fffffc03`22e64998  fffff805`44e48d24 nvlddmkm+0x168d24
fffffc03`22e649a0  ffffcc8e`d91ec0a0
fffffc03`22e649a8  fffffc03`22e64a70
fffffc03`22e649b0  00000000`00000000
fffffc03`22e649b8  00000000`00000000
fffffc03`22e649c0  ffffcc8e`d91ec0a0
fffffc03`22e649c8  fffff805`44daa5fb nvlddmkm+0xca5fb
fffffc03`22e649d0  ffffcc8e`d91ec0a0
fffffc03`22e649d8  fffff805`44daa5fb nvlddmkm+0xca5fb
fffffc03`22e649e0  00000000`00000000
fffffc03`22e649e8  025000a0`00000000
fffffc03`22e649f0  00000000`00000000
fffffc03`22e649f8  fffff805`44e48d24 nvlddmkm+0x168d24

This is most unusual because according to the MSInfo32.nfo file you don't appear to have an Nvidia graphics card installed?

ubuysa said:

First things first; you say you've removed one (faulty) RAM stick, yet in the 1st April dump there are still two RAM cards installed. However, the RAM installed on 1st April is different from the RAM that was installed in your previous file collection upload?

The only third-party driver on the call stack for the 1st April dump is the Nvidia graphics driver nvlddmkm.sys...

Code:

fffffc03`22e64988  ffffcc8e`d2012e80
fffffc03`22e64990  00000000`00000000
fffffc03`22e64998  fffff805`44e48d24 nvlddmkm+0x168d24
fffffc03`22e649a0  ffffcc8e`d91ec0a0
fffffc03`22e649a8  fffffc03`22e64a70
fffffc03`22e649b0  00000000`00000000
fffffc03`22e649b8  00000000`00000000
fffffc03`22e649c0  ffffcc8e`d91ec0a0
fffffc03`22e649c8  fffff805`44daa5fb nvlddmkm+0xca5fb
fffffc03`22e649d0  ffffcc8e`d91ec0a0
fffffc03`22e649d8  fffff805`44daa5fb nvlddmkm+0xca5fb
fffffc03`22e649e0  00000000`00000000
fffffc03`22e649e8  025000a0`00000000
fffffc03`22e649f0  00000000`00000000
fffffc03`22e649f8  fffff805`44e48d24 nvlddmkm+0x168d24

This is most unusual because according to the MSInfo32.nfo file you don't appear to have an Nvidia graphics card installed?

I certainly only have just the one RAM module installed. After testing the RAM I decided to test the DIMM slots that I had my RAM slotted into using the one good stick of RAM that I have. I haven't used any different RAM, this is the only set that I have. I do have an Nvidia GPU installed so I don't know.