Intermittent BSOD - IRQL, PAGE_FAULT, etc


  1. Posts : 4
    Windows 10 Education 20H2
       #1

    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
      My Computer


  2. Posts : 1,318
    Windows 8.1 Enterprise x64
       #2

    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
      My Computer


  3. Posts : 4
    Windows 10 Education 20H2
    Thread Starter
       #3

    Pepka, was thinking that. I am slowly getting components tested. I did also run 1 stick in the slots, went from A1, A2, B1, B2. The system didn't seem to crash out, but didn't test it long enough to be conclusive. My logic is that the system should be stable with two sticks installed.

    If it was a memory slot, wouldn't that produce errors in Memtest86? For what it's worth, ran 2 passes of Memtest86+ v 5.31b, and had no errors.

    I also removed the NVME drive, and installed a copy of Windows to a spare HDD. During initial Windows setup I got two BSOD's. Afterwards, I was able to run Prime95 for 4.5 hours. When I shut Prime95 down, I got an immediate crash. Same thing after that happened yesterday after running HDTune and it finishing. So it isn't the NVME.

    I think the pattern is this: high loads -> idle = crash. Not sure why, but the system does seem pretty stable in games, it's only when doing less demanding tasks that it crashes like this.

    I'll upload the latest v2 logs from the new windows installation sans the NVME.

    Note: I haven't installed any third party drivers, and let Windows do all the updating. Want to eliminate as much guess work as possible.

    Latest V2 logs

    DESKTOP-7CCNF0C-(2020-12-07_14-49-38).zip - Google Drive

    - - - Updated - - -

    Okay, small update. One stick just crashed. We'll call it stick 2. Stick 1 was the one I had installed before with no crashes. So I am now trying stick 1 to see if it doesn't crash.

    Just goes to show, that I ran both memtest86 (2 * 4 passes), and memtest86+ (2 passes), and had no errors reported. So it looks like it might be that one of the sticks was just bad. I am hoping it is just this.

    - - - Updated - - -

    Got a new set of RAM installed, but just got a DPC_WATCH_DOG_VIOLATION. System ran for a good 12 hours without issues, before it was pretty consistent.

    - - - Updated - - -

    Alright,

    It was not the RAM, as the system is still crashing frequently. Tomorrow I plan to switch out the motherboard, and get a tester GPU. Pretty sure it is either CPU, or mobo at this point.

    Weird how the system was stable for a bit, then started crashing after switching the ram. Why would this happen?
    Last edited by Nawsyont; 08 Dec 2020 at 13:42.
      My Computer

  4. philc43's Avatar
    Posts : 5,069
    64bit Win 10 Pro ver 20H2 Build 19042.985 and W10 Insider Preview Build 21376
       #4

    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.
      My Computers


  5. Posts : 4
    Windows 10 Education 20H2
    Thread Starter
       #5

    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.
      My Computer


  6. Posts : 38,664
    windows 10 professional version 1607 build 14393.969 64 bit
       #6

    Nvidia GPU drivers were seen in 2 bugchecks: nvlddmkm.sys

    12/3: F7
    12/7: 193


    27.21.14.5751


    When available post reports from the GPU swap.


    1) Please post a share link for:
    C:\Windows\LiveKernelReports\WATCHDOG-20201206-1941.dmp

    Code:
    LastWriteTime        Size (MB) FullName                                               
    -------------        --------- --------                                               
    12/6/2020 7:41:56 PM    868.74 C:\Windows\LiveKernelReports\WATCHDOG-20201206-1941.dmp




    2) Run Memtest86 version 8.4 (or newer version if available) for four passes.
    Repeat the test so that eight passes are performed.

    MemTest86 - Official Site of the x86 Memory Testing Tool

    Use a camera or smart phone camera to take pictures and post images into the thread.
    In case there are any problems uploading images use share links (one drive, drop box, or google drive)

    Memtest86 has a feature to produce a text report.
    Please post this in addition to the images.


    When available post Memtest86 results for 2 tests each with 4 passes = 8 passes
    CMW16GX4M2C3200C16






    Code:
    Name	NVIDIA GeForce GTX 1080 Ti
    PNP Device ID	PCI\VEN_10DE&DEV_1B06&SUBSYS_447119DA&REV_A1\4&2283F625&0&0019
    Adapter Type	GeForce GTX 1080 Ti, NVIDIA compatible
    Adapter Description	NVIDIA GeForce GTX 1080 Ti
    Adapter RAM	(1,048,576) bytes
    Installed Drivers	C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_372920ce6be76248\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_372920ce6be76248\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_372920ce6be76248\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_372920ce6be76248\nvldumdx.dll
    Driver Version	27.21.14.5751
    INF File	oem16.inf (Section046 section)
    Color Planes	Not Available
    Color Table Entries	4294967296
    Resolution	3440 x 1440 x 143 hertz
    Bits/Pixel	32
    Memory Address	0xFB000000-0xFBFFFFFF
    Memory Address	0xD0000000-0xDFFFFFFF
    Memory Address	0xE0000000-0xE1FFFFFF
    IRQ Channel	IRQ 54
    Driver	C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPI.INF_AMD64_372920CE6BE76248\NVLDDMKM.SYS (27.21.14.5751, 31.53 MB (33,066,392 bytes), 12/2/2020 9:36 AM)
    Last edited by zbook; 10 Dec 2020 at 02:40.
      My Computer


  7. Posts : 4
    Windows 10 Education 20H2
    Thread Starter
       #7

    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.
      My Computer


  8. Posts : 38,664
    windows 10 professional version 1607 build 14393.969 64 bit
       #8
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 10:33.
Find Us




Windows 10 Forums