When gaming: WHEA_UNCORRECTABLE_ERROR

Page 1 of 3 123 LastLast

  1. Posts : 12
    Windows 10 Pro
       #1

    When gaming: WHEA_UNCORRECTABLE_ERROR


    Hi guys

    Specs:
    Ryzen 7 3700x
    Klevv KD4AGU880-32A160U BOLT X Gaming 32GB
    Aorus B550I Pro AX
    Gigabyte Geforce GTX 1080
    Windows 10 Pro 2004 (Build: 19041.572)

    I hope you can help, I am facing the following BSOD when playing games, this does seem to occur at random other times but mostly when the GPU is under load.
    WHEA_UNCORRECTABLE_ERROR

    I have the mini dump location set to D:\Minidump but the BSOD never seems to complete the dump and gets stuck at 0%.

    Instead I will link you the v2 collector zip that I have poured over but honestly my skills lie with *nix not Windows so I'm not really sure what to look for.

    Any help would be appreciated.
      My Computer


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

    Check in Windows Update if there any updates of system
    Update AMD chipset driver - https://www.amd.com/en/support/chips...ocket-am4/b550
      My Computer


  3. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #3

    No dumps makes it difficult to debug the problem.

    Run Tuneup.bat from the BSOD batch repository. Follow Part One, Part Two and Part Three to Download, Run and Collect output data from the batch file to post here.

    You can see what the batch file does when you click on the above link.
      My Computers


  4. Posts : 12
    Windows 10 Pro
    Thread Starter
       #4

    Here is the output of tuneup.bat:


    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="VIDAR" get AutomaticManagedPagefile
    wmic Computersystem where name="VIDAR" set AutomaticManagedPagefile=True
    wmic Computersystem where name="VIDAR" 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.19041.572
    
    [==========================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.19041.572
    
    [==========================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.
    Volume label is OS NTFS.
    
    Stage 1: Examining basic file system structure ...
      523776 file records processed.
    File verification completed.
     Phase duration (File record verification): 8.57 seconds.
      9650 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.82 milliseconds.
    
    Stage 2: Examining file name linkage ...
      254 reparse records processed.
        Found an unneeded link ($FILE_NAME: "SYSTEM~1") in index "$I30" of directory "\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft <0x2,0x14000>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "c728efb32d94b737_0") in index "$I30" of directory "\Users\agent\AppData\Roaming\discord\Code Cache\js <0xa,0x220a1>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "C728EF~1") in index "$I30" of directory "\Users\agent\AppData\Roaming\discord\Code Cache\js <0xa,0x220a1>"
            ... repaired online.
      687744 index entries processed.
    Index verification completed.
     Phase duration (Index verification): 27.40 seconds.
      4 unindexed files scanned.
     Phase duration (Orphan reconnection): 0.00 milliseconds.
      4 unindexed files recovered to lost and found.
        Found 4 lost files (...\Certificates <0x1,0x14b80>, ...\CRLs <0x1,0x14b81>, ...); requesting reconnection to index "$I30" of directory "\??\C:\found.000"
            ... repaired online.
     Phase duration (Orphan recovery to lost and found): 0.00 milliseconds.
      254 reparse records processed.
     Phase duration (Reparse point and Object ID verification): 4.60 milliseconds.
    
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
     Phase duration (Security descriptor verification): 77.01 milliseconds.
      81985 data files processed.
     Phase duration (Data attribute verification): 0.44 milliseconds.
    CHKDSK is verifying Usn Journal...
    Usn Journal verification completed.
    Windows has found problems and some were fixed online;
    the remaining problems must be fixed offline.
    Please run "chkdsk /f" to fix the issues.
    
     499468346 KB total disk space.
      96144196 KB in 299747 files.
        274132 KB in 81988 indexes.
             0 KB in bad sectors.
        608710 KB in use by the system.
         65536 KB occupied by the log file.
     402441308 KB available on disk.
    
          4096 bytes in each allocation unit.
     124867086 total allocation units on disk.
     100610327 allocation units available on disk.
    Total duration: 38.80 seconds (38801 ms).
    
    C:\Windows\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE
    
    
    C:\Windows\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\VIDAR\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk1\\Partition3"'
    Property(s) update successful.
    
    C:\Windows\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE
    
    
    C:\Windows\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7
    
    
    C:\Windows\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\VIDAR\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk1\\Partition3"'
    Property(s) update successful.
    
    C:\Windows\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7
    
    
    C:\Windows\system32>wmic pagefile list /format:list
    
    
    AllocatedBaseSize=2048
    CurrentUsage=0
    Description=C:\pagefile.sys
    InstallDate=20200920035244.872423+600
    Name=C:\pagefile.sys
    PeakUsage=0
    Status=
    TempPageFile=FALSE
    
    
    
    
    C:\Windows\system32>wmic Computersystem where name="VIDAR" get AutomaticManagedPagefile
    AutomaticManagedPagefile
    TRUE
    
    
    C:\Windows\system32>wmic Computersystem where name="VIDAR" set AutomaticManagedPagefile=True
    Updating property(s) of '\\VIDAR\ROOT\CIMV2:Win32_ComputerSystem.Name="VIDAR"'
    Property(s) update successful.
    
    C:\Windows\system32>wmic Computersystem where name="VIDAR" get AutomaticManagedPagefile
    AutomaticManagedPagefile
    TRUE
    
    
    C:\Windows\system32>bcdedit /enum {badmemory}
    
    RAM Defects
    -----------
    identifier              {badmemory}
    badmemorylist           0x537f8
                            0x537f9
                            0x537fa
                            0x537fb
                            0x537fc
                            0x537fd
                            0x537fe
                            0x537ff
    Press any key to continue . . .
    I note the badmemorylist however this RAM is brand new and was in fact an RMA for some RAM that failed memtest86+.
    After seeing this badmemorylist I booted into memtest and ran a few passes which reported no errors, however I am skeptical. Is their anything that could be killing RAM?

    In addition I updated the AMD chipset drivers and will run the machine under load later today to see if we can trigger a BSOD and I can then provide a memory dump assuming it will complete.

    Thanks
      My Computer


  5. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #5

    Clear the bad memory list and lets see if it regenerates:

    bcdedit /deletevalue {badmemory} badmemorylist
      My Computers


  6. Posts : 41,481
    windows 10 professional version 1607 build 14393.969 64 bit
       #6

    Code:
    Windows has found problems and some were fixed online;
    the remaining problems must be fixed offline.
    Please run "chkdsk /f" to fix the issues.

    Open administrative command prompt and type or copy and paste:
    chkdsk /r /v
    This may take hours to run so plan to run overnight.
    Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

    C:\Windows\system32>chkdsk /r /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


    Use the information in this link to find the chkdsk report in the event viewer.
    Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
    Read Chkdsk Log in Event Viewer in Windows 10


    Code:
    ------------------------
    Disk & DVD/CD-ROM Drives
    ------------------------
          Drive: C:
     Free Space: 383.8 GB
    Total Space: 487.8 GB
    File System: NTFS
          Model: ADATA SX6000NP
    
          Drive: D:
     Free Space: 218.8 GB
    Total Space: 953.9 GB
    File System: NTFS
          Model: ST1000LM014-1EJ164
      My Computer


  7. Posts : 12
    Windows 10 Pro
    Thread Starter
       #7

    Thanks for the suggestions everyone.

    The Badmemorylist has not regenerated yet but I will rerun the command every few hours that I can and check up on it.

    chkdisk returned no errors.

    After running furmark for several hours I had a BSOD with the same error and no crashdump, it hung at 0% for 6 hours.

    I finally rebooted and ran the collector again which is attached here: VIDAR-(2020-12-16_22-02-08).zip - Google Drive

    This all seems to point to the GPU, however I have replaced all components recently bar the GPU and PSU, I am happy to replace either but could a fault PSU cause this? I have only ever had a bad PSU cause immediate power off and erratic shutdowns, never BSOD so I am unsure.

    Thanks again for your continued help.
      My Computer


  8. Posts : 41,481
    windows 10 professional version 1607 build 14393.969 64 bit
       #8

    agentsquirrel said:
    chkdisk returned no errors.

    Please post the chkdsk /r /v results for each drive.
      My Computer


  9. Posts : 12
    Windows 10 Pro
    Thread Starter
       #9

    zbook said:
    Please post the chkdsk /r /v results for each drive.
    Sorry zbook, I forgot to include them:

    This first one is drive D:

    Code:
    The type of the file system is NTFS.
    Volume label is Media NTFS.
    
    Stage 1: Examining basic file system structure ...
      324352 file records processed.
    File verification completed.
     Phase duration (File record verification): 8.97 seconds.
      128 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.48 milliseconds.
    
    Stage 2: Examining file name linkage ...
      128 reparse records processed.
      373428 index entries processed.
    Index verification completed.
     Phase duration (Index verification): 1.04 minutes.
      0 unindexed files scanned.
     Phase duration (Orphan reconnection): 127.67 milliseconds.
      0 unindexed files recovered to lost and found.
     Phase duration (Orphan recovery to lost and found): 28.70 milliseconds.
      128 reparse records processed.
     Phase duration (Reparse point and Object ID verification): 3.11 milliseconds.
    
    Stage 3: Examining security descriptors ...
    Cleaning up 173 unused index entries from index $SII of file 9.
    Cleaning up 173 unused index entries from index $SDH of file 9.
    Cleaning up 173 unused security descriptors.
    Security descriptor verification completed.
     Phase duration (Security descriptor verification): 16.21 milliseconds.
      24539 data files processed.
     Phase duration (Data attribute verification): 0.54 milliseconds.
    CHKDSK is verifying Usn Journal...
      37317872 USN bytes processed.
    Usn Journal verification completed.
     Phase duration (USN journal verification): 387.65 milliseconds.
    
    Stage 4: Looking for bad clusters in user file data ...
      324336 files processed.
    File data verification completed.
     Phase duration (User file recovery): 2.67 hours.
    
    Stage 5: Looking for bad, free clusters ...
      55402646 free clusters processed.
    Free space verification is complete.
     Phase duration (Free space recovery): 0.00 milliseconds.
    
    Windows has scanned the file system and found no problems.
    No further action is required.
    
     976760831 KB total disk space.
     754578088 KB in 268516 files.
        115216 KB in 24540 indexes.
             0 KB in bad sectors.
        456939 KB in use by the system.
         65536 KB occupied by the log file.
     221610588 KB available on disk.
    
          4096 bytes in each allocation unit.
     244190207 total allocation units on disk.
      55402647 allocation units available on disk.
    Total duration: 2.69 hours (9688624 ms).
    and this next one is C:
    Code:
    Checking file system on C:
    The type of the file system is NTFS.
    Volume label is OS NTFS.
    
    
    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 ...
      523776 file records processed.                                                         
    File verification completed.
     Phase duration (File record verification): 6.89 seconds.
      9650 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.64 milliseconds.
    
    Stage 2: Examining file name linkage ...
      254 reparse records processed.                                       
      687746 index entries processed.                                                        
    Index verification completed.
     Phase duration (Index verification): 24.17 seconds.
      0 unindexed files scanned.                                         
     Phase duration (Orphan reconnection): 343.24 milliseconds.
      0 unindexed files recovered to lost and found.                     
     Phase duration (Orphan recovery to lost and found): 2.48 seconds.
      254 reparse records processed.                                       
     Phase duration (Reparse point and Object ID verification): 3.33 milliseconds.
    
    Stage 3: Examining security descriptors ...
    Cleaning up 1371 unused index entries from index $SII of file 0x9.
    Cleaning up 1371 unused index entries from index $SDH of file 0x9.
    Cleaning up 1371 unused security descriptors.
    Security descriptor verification completed.
     Phase duration (Security descriptor verification): 53.68 milliseconds.
      81986 data files processed.                                            
     Phase duration (Data attribute verification): 0.69 milliseconds.
    CHKDSK is verifying Usn Journal...
      35179896 USN bytes processed.                                                            
    Usn Journal verification completed.
     Phase duration (USN journal verification): 144.03 milliseconds.
    CHKDSK discovered free space marked as allocated in the
    master file table (MFT) bitmap.
    
    Windows has made corrections to the file system.
    No further action is required.
    
     499468346 KB total disk space.
      95751000 KB in 299700 files.
        274192 KB in 81987 indexes.
             0 KB in bad sectors.
        643330 KB in use by the system.
         65536 KB occupied by the log file.
     402799824 KB available on disk.
    
          4096 bytes in each allocation unit.
     124867086 total allocation units on disk.
     100699956 allocation units available on disk.
    Total duration: 34.23 seconds (34235 ms).
    
    Internal Info:
    00 fe 07 00 00 d3 05 00 5c 5c 0a 00 00 00 00 00  ........\\......
    a9 00 00 00 55 00 00 00 00 00 00 00 00 00 00 00  ....U...........
    
    Windows has finished checking your disk.
    Please wait while your computer restarts.
    Nothing of note there or am I missing something?

    I will note that another BSOD has occurred and still no dump has been made after 6 hours of waiting.
      My Computer


  10. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #10

    Run through this tutorial and make sure everything is setup correctly: How to Configure Windows 10 to Create Dump Files on BSOD

    Also, from a Elevated Command Prompt, run

    bcdedit /enum {badmemory}

    to see if the list has accumulated any more bad memory.
      My Computers


 

  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 15:25.
Find Us




Windows 10 Forums