[SOLVED] WHEA_UNCORRECTABLE_ERROR - Hellllp! FIX: I changed my faulty m.2 SSD with a new one (also a new gpu).

W

WellYes

Active member
Joined
Dec 21, 2022
Posts
35
I have been trying to troubleshoot BSODs on my pc. It has gotten so bad that anytime i load a game and start to play it would BSOD (cant recall original error message). I went through multiple troubleshooting steps over the past few days based on things I've found on various forums, such as..

sfc scan
dism
chkdsk
updated drivers
updated bios
windows repair
memtest - no errors were found
tested both my HDD and SSD using their makers software

still was getting BSODs, This was when i think the BSOD started showing the WHEA_UNCORRECTABLE_ERROR sooo I tried...

Clean Install of Windows cleaning both my HDD and SSD (Windows installed to SSD)

Once fresh install was done i did the following..

downloaded and installed all windows updates
ensured drivers were update - required me to download certain things like geforce experience to install GPU drivers.
installed Steam -> installed a game like Destiny 2 -> went to play and BSOD.

My pc was and still is running just fine... until I try to play a game. I have only experienced BSOD when going to play a game. Originally i could play the game for a variable amount of time before BSOD'ing -> now its just to the point where i shortly started to get into the game (usually not even to the point of playing). On top of all this, dump files will no longer generate.. when it BSODs - it freezes on the BSOD screen. Even if i leave it, it stays at 0% for creating the log and i have to force shut my pc off... Came across this program being suggested for these scenarios and hoping to find someone who can assist me.. i am at a loss. Attached is the zip generated from Sysnative.

  • A brief description of your problem (but you can also include the steps you tried) - see above
  • System Manufacturer? - n/a, built by me
  • Laptop or Desktop? - Desktop
  • Exact model number (if laptop, check label on bottom) - N/A
  • OS ? (Windows 11, 10, 8.1, 8, 7, Vista) - Windows 10
  • x86 (32bit) or x64 (64bit)? - x64
  • (Only for Vista, Windows 7) Service pack? - N/A
  • What was original installed OS on system? - Windows 10
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? - full retail version
  • Age of system? (hardware) - 2 years, i think.. will verify
  • Age of OS installation? - running a clean install as of today (12/21/2022)
  • Have you re-installed the OS? - Yes, see above answer
  • CPU - AMD Ryzen 3900x
  • RAM (brand, EXACT model, what slots are you using?) - G.Skill F4-3600C16-8GTZN
  • Video Card - NVIDIA GeForce RTX 3080 Founders Edition
  • MotherBoard - (if NOT a laptop) -ASUS ROG CROSSHAIR VIII HERO (WI-FI)
  • Power Supply - brand & wattage (if laptop, skip this one) - Corsair RM850x
  • Is driver verifier enabled or disabled? - Disabled, but at the start of all my troubleshooting i had it enabled trying to see if driver issues were the cause of my BSOD
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth) - Windows Defender is enabled i believe since the clean install of Win10
  • Are you using proxy, vpn, ipfilters or similar software? - None
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software) - None
  • Are you currently under/overclocking? Are there overclocking software installed on your system? - None
 

Attachments

Last edited:
Doing my best to recall things over the past few days... at one point when i started getting the BSODs i was seeing an issue with ene.sys in event viewer -> i followed a bunch of troubleshooting back then where I uninstalled all lighting programs and ran a batch job from G.Skill that removed all the drivers. Did not fix the BSOD issue then. I remember around this time i enabled driver verifier and was generating dump files which i was viewing with bluescreenview -> i kept seeing ene.sys and ntoskrnl.exe.. This was all stuff i was attempting before attempting repairing windows. Not sure if this is relevant at all since i have since done a clean install of windows and wipe of my drives.
.

If relevant, here is the microsoft forum post i saw, Redirecting which linked to this in a post [Trident Z Lighting Control] Driver Conflict / Clean Uninstall Guide - G.SKILL TECH FORUM
 
Hi,

Could you specify which tests you ran for the memory?

I would suggest removing the ASUS software, it has a history of causing problems and I would like to rule it out as a potential cause.
 
I ran memtest86, but only for 4 passes. I read somewhere last night u need to run it 8 times at least, so I'm in the process of running it again... It takes like 7 hours to finish.. currently on/almost done with pass 2 of 4 without any errors.

I also ran some kind of windows memory diagnosis overnight a few days ago but never saw the results. Didn't run it again since I ran memtest86.

Asus armoury crate is no longer on my PC since I did the clean install and wipe of my drives. I did not reinstall it.
 
I am at a loss on what i should be trying next.. I just want to be able to play games with my friends again. I've been trying to get dump files to create, but cant. Checking event viewer i see Event ID 161 - Dump file creation failed due to error during dump creation when im crashing. Also when i get the BSOD it says its collecting data, but its just frozen never changes from 0% regardless of how long i leave it. Not sure if that info helps anyone help me..

I paid attention to my CPU and GPU temps when starting to play a game and BSOD. my CPU got to 52 degrees and my GPU got close to 63 degrees. I did turn on display parameters in the registry.
 
Just trying random things now... I am needing someone with way more knowledge than I on this stuff to determine if this helps narrow things down... I kind of was thinking if i BSOD 2-3 minutes into a game, that stress testing my CPU or GPU for that long would also result in a BSOD - if they were the problem.

Ran Prime95 for 10 or 15 minutes. No BSOD happened, no errors. Max temp got to 90 degrees and i stopped it because i didnt feel comfortable with anything higher than that.

Ran FurMark for 5 minutes on 1440p resolution. No BSOD happened, no errors. Max temp got to 74 degrees.
 
When i enable driver verifier, i get a different BSOD error of PAGE_FAULT_IN_NONPAGED_AREA for ntoskrnl.exe - This did generate a dump file which is attached. Ive also experienced a couple of random restarts since this WITHOUT hitting a blue screen... unsure if either of these things are relevant to whats going on with my PC.
 

Attachments

Open notepad and task manager. In task manager right click on the notepad process and select create dump file, does it create a dump file successfully?
 
When you get a BSOD and the progress freezes, could you note down any errors mentioned. That may give clues to the cause.

Have you attempted to play a game with just 8GB, assuming any game will crash you shouldn't need 32GB of RAM for now. Also did you use chkdsk only for the Windows partition or any other partition as well?
 
When I get the BSOD the screen displays the message about generating a report and stays at 0% the only other thing it displays is the WHEA_UNCORRECTABLE_ERROR message. I don't think it says anything else but let me check. EDIT: attached two screenshots, it shows something in the top left. I think this is because I followed some instructions to add display parameters in the registry trying to troubleshoot.

Yesterday after the 2 memtest86 runs I actually took all 4 sticks out and put only 1 in at a time and loaded up destiny 2. I BSOD with all 4 sticks separately. Tried a different slot on the mobo too just in case. I would think this all would rule out my RAM, right?

I don't recall what I did with chkdsk.. I think I just ran chkdsk /r. If I need to do something further with that please let me know some instructions on what to try. Appreciate your help so far!!!
 

Attachments

  • PXL_20221223_005642357.jpg
    PXL_20221223_005642357.jpg
    81.1 KB · Views: 4
  • PXL_20221223_005640567.jpg
    PXL_20221223_005640567.jpg
    67.6 KB · Views: 4
Last edited:
The WHEA is surprisingly a driver-based crash. I looked into the last dump you provided and I would recommend using driver verifier with the instructions from here Driver Verifier - BSOD related - Windows 11, 10, 8.1 and 8

Some of the settings you used with driver verifier are quite dangerous when used recklessly and have the potential of triggering false positives too.
 
To clarify, once i set up driver verify, do i leave my pc alone for 24 hours like the linked guide says ("- Driver Verifier needs to run for 24 hours minimum - even if the status screen appears clear."). Else do i enable it -> re boot -> go to play a game to trigger the BSOD?
 
Use your computer like you normally would for triggering a BSOD, preferably try to trigger a crash multiple times until 48h has passed (24 is the minimum but I would recommend 48h).
 
Once I get it enabled it only takes me 2-3 minutes to hit the bsod.. I literally go into the game strat to do something and it happens :/ it has never bsod without me playing a game. I will get logs shortly though.
 
I'd need at least a few crashes to have occurred before you provide the logs.
 
Driver Verifier has been set up based on the link you posted in post #14. Ive hit the BSOD twice since, but no new dump files are being generated. Thoughts?

system failure settings.PNG
 
Hit the BSOD another three times, then post new Sysnative logs.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top