Intermittent BSOD - IRQL, PAGE_FAULT, etc

Hello,

Win 10, 20H2 build 19042.662

I am experiencing a BSOD that appears after a few hours of system up time. It varies what the errors are. I have tried out Memtest86, with both sticks installed, and separately. There were no issues reported.

Just to make sure it wasn't a PSU issue I ordered a PSU and swapped it out, still have the error.

Currently I am running a selective startup, with non-microsoft services disabled. BIOS is up-to-date. I have installed all drivers from the manufacturers website, and chipset drivers, and they are all up to date.

Interestingly, my system was stable with 1 ram stick, with selective startup. It crashes with normal startup, 1 stick. With 2 ram sticks installed, it crashes with selective startup. Nothing seems conclusive at this point, and I believe it is a hardware issue. CPU, RAM, or MOBO? Maybe GPU? I have a CPU RMA from AMD ready to go, so I might just go that route.

Perhaps it is the NVME?

Edit: I did reinstall Win10, and got a crash about 5 minutes into the fresh install.

I have attached the V2 log. Thanks.

- - - Updated - - -

Ran tuneup.bat, here is the output. Looks normal.

Code:

###########################################################
# The following commands will be run in sequence.         #
# The first 5 will take quite a while to run, be patient. #
###########################################################

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow

chkdsk /scan

wmic recoveros get autoreboot
wmic recoveros set autoreboot = false
wmic recoveros get autoreboot
wmic recoveros get DebugInfoType
wmic recoveros set DebugInfoType = 7
wmic recoveros get DebugInfoType

wmic pagefile list /format:list
wmic Computersystem where name="REAC-5" get AutomaticManagedPagefile
wmic Computersystem where name="REAC-5" set AutomaticManagedPagefile=True
wmic Computersystem where name="REAC-5" get AutomaticManagedPagefile

bcdedit /enum {badmemory}


C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.572

Image Version: 10.0.19042.662

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.572

Image Version: 10.0.19042.662

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
  349440 file records processed.
File verification completed.
 Phase duration (File record verification): 2.21 seconds.
  5121 large file records processed.
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 0.62 milliseconds.

Stage 2: Examining file name linkage ...
  195 reparse records processed.
  490074 index entries processed.
Index verification completed.
 Phase duration (Index verification): 6.82 seconds.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 260.00 milliseconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 0.65 milliseconds.
  195 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 2.40 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 42.86 milliseconds.
  70318 data files processed.
 Phase duration (Data attribute verification): 1.22 milliseconds.
CHKDSK is verifying Usn Journal...
  35254488 USN bytes processed.
Usn Journal verification completed.
 Phase duration (USN journal verification): 94.95 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

 487755746 KB total disk space.
 230597904 KB in 272505 files.
    165684 KB in 70319 indexes.
         0 KB in bad sectors.
    468162 KB in use by the system.
     65536 KB occupied by the log file.
 256523996 KB available on disk.

      4096 bytes in each allocation unit.
 121938936 total allocation units on disk.
  64130999 allocation units available on disk.
Total duration: 9.45 seconds (9453 ms).

C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
TRUE


C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\REAC-5\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Education|C:\\Windows|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
1


C:\Windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\REAC-5\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Education|C:\\Windows|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\Windows\system32>wmic pagefile list /format:list


AllocatedBaseSize=17408
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20201130152618.455084-420
Name=C:\pagefile.sys
PeakUsage=1
Status=
TempPageFile=FALSE




C:\Windows\system32>wmic Computersystem where name="REAC-5" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\Windows\system32>wmic Computersystem where name="REAC-5" set AutomaticManagedPagefile=True
Updating property(s) of '\\REAC-5\ROOT\CIMV2:Win32_ComputerSystem.Name="REAC-5"'
Property(s) update successful.

C:\Windows\system32>wmic Computersystem where name="REAC-5" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\Windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier              {badmemory}
Press any key to continue . . .

- - - Updated - - -

Just got a REFERENCE_BY_POINTER error, uploading the log. Was running HDTune error test, and it had just completed. No errors, will try to get the picture from a second run...

From a second run.

Attachment 309537

Hmm, the DIMM sockets on the motherboard may be damaged, there may also be some RAM bone screwed (although as it happens with every bone, I would bet on DIMM sockets). Check with a different motherboard

I think this is another example of the increase in recent BSODs associated with Ryzen 5 3600 CPUs. I am not sure if AMD and MS are addressing this or not. I have seen no official acknowledgement of a problem but I am seeing that something is not quite right.

My suspicion is that there is a setting in the BIOS that needs adjusting but I do not have any way to explore this myself. Some users have tried disabling simultaneous multithreading and had some success, others have played around with the power plan settings. Try looking on the AMD forums or motherboard manufacturers' forums for similar situations.

Thanks for the reply, I am familiar with the problems with C_States and SMT that other people have changed. I did try changing some C_state settings, it didn't seem to work. As well as changing Windows settings to the special "Ryzen balanced" mode due to apparent idling issues the chips have.

I am going to switch out the GPU here, and then see if it still crashes, and then move onto a motherboard switch out.

Part of me doing this is out of curiosity, boredom, and duty. Hopefully other people find this thread useful. I had an intimation that it was the CPU when this started happening, and I kind of want to find out if it is.

Okay, I swapped out the graphics card; still BSODs on the ASRock mobo.

Because I had already swapped the RAM out, tested the NVME, removed all extra drives, and swapped the GPU - and the system still had BSOD on the ASRock, I swapped it out with an ASUS.

I have ran the system now for a little less than 24 hours, and have received no Blue Screens of Death. I had a testing methodology that I used to crash the other system, that is not repeatable on this board.

So I was probably mistaken when thinking that the older RAM I had installed was not bad - it was the motherboard having issues.

ZBrook, I had ran tests on the older RAM that I swapped out - ran windows memory diagnostic on the new kit just to make sure, I really don't want to wait a few hours to test the swap out RAM when it seems to have been the mobo.

I'll wait about another day to see if the system remains stable, then I'll mark as solved.

Nice swap testing.
Reliability Monitor is the Best Windows Troubleshooting Tool You Aren’t Using