Jump to content

Computer Bluescreens with WHEA_UNCORRECTABLE_ERROR

NahoBoofy
By NahoBoofy
in Troubleshooting
 Share
Posted

I've been getting the same blue screen error every once in a while for the past year now. Using chkdsk /f /r /x has been able to fix it usually up until now. I thought the issue was with my >10 year old HDD so I ordered a new SAMSUNG 870 EVO SATA III SSD 1TB 2.5” Internal Solid State Drive. However when I tried installing Windows 10 64bit using a USB, it would either crash while installing or crash when the installation required the my PC to restart.

 

Got Windows 10 installed on a fresh SSD but I'm still getting the same error.

Link to post
Share on other sites
Posted
Just now, NahoBoofy said:

How can I test if my mobo, cpu. or gpu is the problem?

you cant, at least not without swapping components, and even then it's not a full certainty you found the actual problem.

 

the first step is re-making the installer media, so you can at least exclude the easy ones.

 

given that you mention you're hunting down a recurring crashing issue, the answer is probably burried somewhere inside your windows logs.

Link to post
Share on other sites
Posted
  • Author
On 9/29/2023 at 3:35 PM, manikyath said:

you cant, at least not without swapping components, and even then it's not a full certainty you found the actual problem.

 

the first step is re-making the installer media, so you can at least exclude the easy ones.

 

given that you mention you're hunting down a recurring crashing issue, the answer is probably burried somewhere inside your windows logs.

So I managed to get windows installed by reseating the CMOS battery, but then I got the same BSOD Whea error after a little while.

Link to post
Share on other sites
Posted

WHEA is a hardware error recorded by the CPU. The CPU logs errors for itself and PCIe devices. Not SATA, not RAM. 

 

Go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

 

If you are not getting dump files that makes the NVMe SSD (If you have one) the main suspect. If you are not getting dump you can make the BSOD screen display more info.  

 

To make the BSOD screen display the additional info on the BSOD screen we need to add a field to the registry. If you are not comfortable editing the registry then do not do this step. Navigate to 

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl

Right click on the empty area on the right section and select New → DWORD value with the name "DisplayParameters". Right click on it, modify and set the value data to 1 (Does not matter if you use Hexadecimal or Decimal). It should look like this once done. Reboot to apply the registry change."

 

The next time you BSOD, you should have these extra numbers in the top left corner. I want a picture of this. If it's automatically restarting and you need more time at the BSOD screen for the picture, look at this guide for changing dump type and at this screen uncheck automatically restart. Just use the power button to restart. 

Link to post
Share on other sites
Posted
16 hours ago, NahoBoofy said:

Here you go, thank you

mindu.zip 137.78 kB · 0 downloads

This shows a hardware error in the CPU when reading data from the L0 cache. Go into the BIOS and do two things.

 

  • Find PBO (Precision Boost Overdrive) and set it to Disabled.
  • Set the XMP to 3200MHz or lower.

If the CPU is overclocked then remove that as well. 

 

PBO is fairly aggressive automatic overclocking that a good amount of CPUs can't handle. The default setting is Automatic and was meant to mean Disabled, but some motherboard vendors have changed what Automatic means with BIOS updates.

 

With regards to the XMP, this error can't be an issue with the RAM, but when you increase the RAM speed you also increase the speed of the memory controller which is in the CPU. 3200MHz is the highest officially supported speed by that CPU.

 

You can also try updating the BIOS. You are on a pretty old one. Updating the BIOS on an unstable machine can be risky as a crash during the BIOS update can brick the motherboard. It doesn't look like your board has any features to recover from a corrupt BIOS. Because of the risk, doing this is up to you if you want to do it or not.

 

If none of this helps then a faulty CPU is the main suspect. 

Link to post
Share on other sites
Posted
  • Author
2 hours ago, Bjoolz said:
  • Find PBO (Precision Boost Overdrive) and set it to Disabled.
  • Set the XMP to 3200MHz or lower.

I can't seem to find options for either of these settings in my BIOS. The manual for my motherboard doesn't make mention of them either.

Link to post
Share on other sites
Posted
2 hours ago, NahoBoofy said:

I can't seem to find options for either of these settings in my BIOS. The manual for my motherboard doesn't make mention of them either.

Oh, sorry, when going back to the dump file later to find the motherboard model, RAM speed, etc, I opened the dump file of a different user. So the error is correct, all the suggestions are not. You hav a 4790K and which is part of the Devil's Canyon architecture. All of the CPUs with this architecture has an issue where they get WHEA crashes if the temp goes above 90°C.

 

Check the CPU temp. If it's above 90°C then re-paste the CPU cooler. 

Link to post
Share on other sites
Posted
  • Author
2 hours ago, Bjoolz said:

Check the CPU temp. If it's above 90°C then re-paste the CPU cooler. 

Thank you, I will be sure to when I get home. 
 

I am curious if you have any ideas for solutions if it doesn't reach 90 Celcius

Link to post
Share on other sites
Posted
26 minutes ago, NahoBoofy said:

Thank you, I will be sure to when I get home. 
 

I am curious if you have any ideas for solutions if it doesn't reach 90 Celcius

Replacing the CPU if nothing is overclocked. Unfortunately. 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×