Jump to content

WHEA_UNCORRECTABLE_ERROR Frustration

Go to solution Solved by Bjoolz,
1 hour ago, Bustedgizmo said:

Bjoolz,

 

As requested. Thanks in advance. 

Screenshot 2025-07-01 011257.png

Screenshot 2025-07-01 011313.png

Screenshot 2025-07-01 011340.png

Screenshot 2025-07-01 011350.png

062825-8593-01.zip 4.25 MB · 0 downloads

To decode the WHEA events I would need a copy paste of the data in the RawData fields. That's the error packet. When we have the dump files it's most likely not needed though because it's very unlikely that they are separate issues.

 

Four of the dump files were WHEA_Uncorrectable_Error crashes showing CPU errors when interacting with the L1 cache. The final one was a Hypervisor_Error which was triggered from an NMI. NMI is Non-Maskable Interrupt and is a type of interrupt where the CPU has to drop everything it's doing and handle it immediately. So it's reserved for more serious stuff like hardware issues. We can't see what sent the NMI or why, but on consumer PCs it's almost always the CPU itself. 

 

Before we do anything, disable any and all overclocking or undervolting. That includes making sure that Precision Boost Overdrive is set as Disabled in the BIOS. If you are using XMP, the speed you have is fine. There  should be no issues with 2666MT/s it's currently set to (If you didn't mean for it to be 2666MT/s, don't enable the 3600 the RAM is rated for. The memory controller could be unhappy with it and we want as little risk as possible while troubleshooting). 

 

So a faulty CPU is the main suspect. We have seen a lot of voltage issues with 5000 series, especially the higher end CPUs like the 5800x, 5900x (Like you have) and the 5950x. So we can try tweaking those voltages first.

 

  • The first is if your motherboard has a setting for a voltage offset. If it does, set the CPU Core and SoC voltage offsets to +0.050v (Please read this number twice. Not 0.5v, but 0.05v).
  • The second is setting a static voltage for the Core and SoC. We set a static voltage of 1.3v to the Core and 1.1v to the SoC.

The first one is more general 5000 series related when you get errors from the CPU memory controller which is less likely the issue here, but it's harmless to test. The second is something we've found helpful for a wide range of issues with those higher end 5000 series CPUs.

 

You are on the second latest BIOS so updating that is unlikely to help, especially when the notes for the new BIOS mainly points to security fixes. You do have Flashback so there shouldn't be any risk in trying. If it crashes during an update and corrupts the BIOS, Flashback should be able to recover it. 

Hi!

 

SYSTEM:

  • OS: Windows 11
  • x86 (32-bit)
  • Age of system: About 3 years
  • Age of OS installation: Reinstalled OS about 2 months ago
  • CPU model: AMD Ryzen 9 5900X 12-Core
  • Video Card model: ASUS The SFF-Ready Prime GeForce RTX™ 4070 Ti Super OC Edition 16GB GDDR6X Graphics Card
  • Motherboard: MSI MAG X570S Tomahawk Wi-Fi Motherboard
  • Power Supply: Seasonic FOCUS GX-650 - 650W - 80+ Gold
  • RAM: CORSAIR VENGEANCE RGB PRO DDR4 RAM 32GB (2x16GB) 3600MHz
  • Storage: SAMSUNG 970 EVO Plus SSD 1TB NVMe M.2

 

ISSUE:

I keep getting BSOD with "WHEA_ Uncorrectable_Error". 

 

BREAKDOWN:

Quick rundown on what I have done and history:

  • Had this issue with the old GPU and the new GPU.
  • Installed one stick of ram at a time. Same issue. Also ran MemTest86. Came back clean, no errors.
  • Reinstalled a clean version of Windows 11.
  • I have gone through the drivers to ensure all are up to date.
  • I have been monitoring temps, voltage and usage via OCCT. Seems all within range. Spikes for loading games and Blender.
  • Cleaned fans and case recently (less than 1 month).
  • Ran test on storage and came back clean. 

 

This seems to happen nearly 100% of the time when closing Helldivers 2. It does happen with other programs but with less frequency (Sketchup, Blender and other video games).

 

QUESTIONS:

  1. Is there a test to verify that the motherboard and the CPU are in good working condition?
  2. At this point should I just replace the motherboard and CPU?
  3. Could it be the Storage?
  4. Anything I am missing in my testing?

 

I am slowly working towards a full replacement but I would like to avoid that. I appreciate any help. Thank you. 

 

Link to comment
https://linustechtips.com/topic/1616603-whea_uncorrectable_error-frustration/
Share on other sites

Link to post
Share on other sites

4 minutes ago, Bustedgizmo said:

QUESTIONS:

  1. Is there a test to verify that the motherboard and the CPU are in good working condition?
  2. At this point should I just replace the motherboard and CPU?
  3. Could it be the Storage?
  4. Anything I am missing in my testing?
  1. CPU you can always run some stress test and run it into another computer. Sure this is not 100% reliable but it is the best you can do. As for the motherboard, there ain't much you can do. This is a process of elimination. Once all other components are proven good, then the motherboard is probably faulty.
  2. It depends mainly on your finances. It can be a valid test to replace the motherboard and CPU to prove that the rest of the computer is in working order. Make sure you can return the motherboard + CPU in case you don't keep them.
  3. It certainly can be a SSD problem. Best way to test it is to use another SSD.
  4. You did not clear the CMOS memory and you did not test with another PSU. 
9 minutes ago, Bustedgizmo said:

I keep getting BSOD with "WHEA_ Uncorrectable_Error". 

It means hardware error. Not very useful but at least it should not be a driver issue.

Good luck !

Link to post
Share on other sites

Sawa, 

 

Thank you so much for your reply.

 

I did forget to mention I did replace the PSU and I did reset the CMOS before I replaced the GPU. I thought I lost my PSU and I reset the CMOS as last ditch before replacing the GPU. 

 

I think your advise is sound and about the same conclusion I came too, just been out of the loop for a bit and wasn't sure if I was on the right track.  

Link to post
Share on other sites

1 hour ago, Bustedgizmo said:

Hi!

 

SYSTEM:

  • OS: Windows 11
  • x86 (32-bit)
  • Age of system: About 3 years
  • Age of OS installation: Reinstalled OS about 2 months ago
  • CPU model: AMD Ryzen 9 5900X 12-Core
  • Video Card model: ASUS The SFF-Ready Prime GeForce RTX™ 4070 Ti Super OC Edition 16GB GDDR6X Graphics Card
  • Motherboard: MSI MAG X570S Tomahawk Wi-Fi Motherboard
  • Power Supply: Seasonic FOCUS GX-650 - 650W - 80+ Gold
  • RAM: CORSAIR VENGEANCE RGB PRO DDR4 RAM 32GB (2x16GB) 3600MHz
  • Storage: SAMSUNG 970 EVO Plus SSD 1TB NVMe M.2

 

ISSUE:

I keep getting BSOD with "WHEA_ Uncorrectable_Error". 

 

BREAKDOWN:

Quick rundown on what I have done and history:

  • Had this issue with the old GPU and the new GPU.
  • Installed one stick of ram at a time. Same issue. Also ran MemTest86. Came back clean, no errors.
  • Reinstalled a clean version of Windows 11.
  • I have gone through the drivers to ensure all are up to date.
  • I have been monitoring temps, voltage and usage via OCCT. Seems all within range. Spikes for loading games and Blender.
  • Cleaned fans and case recently (less than 1 month).
  • Ran test on storage and came back clean. 

 

This seems to happen nearly 100% of the time when closing Helldivers 2. It does happen with other programs but with less frequency (Sketchup, Blender and other video games).

 

QUESTIONS:

  1. Is there a test to verify that the motherboard and the CPU are in good working condition?
  2. At this point should I just replace the motherboard and CPU?
  3. Could it be the Storage?
  4. Anything I am missing in my testing?

 

I am slowly working towards a full replacement but I would like to avoid that. I appreciate any help. Thank you. 

 

WHEA means a hardware issue with the CPU or a PCIe device.

 

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 don't have any dump files it makes the NVMe SSD the main suspect, but we can check something else to confirm. Open Event Viewer → Windows Logs → System and find the Kernel-Power event from the WHEA crash. Go to the Details tab and screenshot what it says here. 

Link to post
Share on other sites

1 hour ago, Bustedgizmo said:

Bjoolz,

 

As requested. Thanks in advance. 

Screenshot 2025-07-01 011257.png

Screenshot 2025-07-01 011313.png

Screenshot 2025-07-01 011340.png

Screenshot 2025-07-01 011350.png

062825-8593-01.zip 4.25 MB · 0 downloads

To decode the WHEA events I would need a copy paste of the data in the RawData fields. That's the error packet. When we have the dump files it's most likely not needed though because it's very unlikely that they are separate issues.

 

Four of the dump files were WHEA_Uncorrectable_Error crashes showing CPU errors when interacting with the L1 cache. The final one was a Hypervisor_Error which was triggered from an NMI. NMI is Non-Maskable Interrupt and is a type of interrupt where the CPU has to drop everything it's doing and handle it immediately. So it's reserved for more serious stuff like hardware issues. We can't see what sent the NMI or why, but on consumer PCs it's almost always the CPU itself. 

 

Before we do anything, disable any and all overclocking or undervolting. That includes making sure that Precision Boost Overdrive is set as Disabled in the BIOS. If you are using XMP, the speed you have is fine. There  should be no issues with 2666MT/s it's currently set to (If you didn't mean for it to be 2666MT/s, don't enable the 3600 the RAM is rated for. The memory controller could be unhappy with it and we want as little risk as possible while troubleshooting). 

 

So a faulty CPU is the main suspect. We have seen a lot of voltage issues with 5000 series, especially the higher end CPUs like the 5800x, 5900x (Like you have) and the 5950x. So we can try tweaking those voltages first.

 

  • The first is if your motherboard has a setting for a voltage offset. If it does, set the CPU Core and SoC voltage offsets to +0.050v (Please read this number twice. Not 0.5v, but 0.05v).
  • The second is setting a static voltage for the Core and SoC. We set a static voltage of 1.3v to the Core and 1.1v to the SoC.

The first one is more general 5000 series related when you get errors from the CPU memory controller which is less likely the issue here, but it's harmless to test. The second is something we've found helpful for a wide range of issues with those higher end 5000 series CPUs.

 

You are on the second latest BIOS so updating that is unlikely to help, especially when the notes for the new BIOS mainly points to security fixes. You do have Flashback so there shouldn't be any risk in trying. If it crashes during an update and corrupts the BIOS, Flashback should be able to recover it. 

Link to post
Share on other sites

1 hour ago, Bustedgizmo said:

I will work on this later today but I attached a SS of what I think you are asking for.

Screenshot 2025-07-01 083010.png

Copy paste. I would need to transcribe the data which is there is no way I'm doing from a screenshot, way too much data. 

 

But again, this is likely not needed because it's very unlikely that it's different from the BSODs. 

Link to post
Share on other sites

  RawData

435045521002FFFFFFFF040001000000020000007F070000321F0500010719140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BB5209217149EADB01020000000000000000000000000000000000000000000000A00100005000000000030000010000001411BCA5646FDE4EB8633E83ED7C83B100000000000000000000000000000000010000000000000000000000000000000000000000000000F0010000C00000000003000000000000ADCC7698B447DB4BB65E16F193C4F3DB00000000000000000000000000000000010000000000000000000000000000000000000000000000B0020000A80400000003000000000000011D1E8AF94257459C33565E5CC3F7E80000000000000000000000000000000001000000000000000000000000000000000000000000000058070000270000000003000000000000A13248C3C302524CA9F19F1D5D7723FC000000000000000000000000000000000300000000000000000000000000000000000000000000000200000000000000000000000000000000386A2C0F00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007F010000000000000002040300010000120FA20000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000000000000000000040000000200000038BD187249EADB0108000000000000000000000000000000000000000100000059080C06000880BC00386A2C0F00000000000000FE0F12D00A0000000800000000000000B00001000000000000000000F9010000030000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000FF00000000000000000000000000000000000000000000000000

 

 

 

 

 

 

This?

Link to post
Share on other sites

3 hours ago, Bustedgizmo said:
  RawData

435045521002FFFFFFFF040001000000020000007F070000321F0500010719140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BB5209217149EADB01020000000000000000000000000000000000000000000000A00100005000000000030000010000001411BCA5646FDE4EB8633E83ED7C83B100000000000000000000000000000000010000000000000000000000000000000000000000000000F0010000C00000000003000000000000ADCC7698B447DB4BB65E16F193C4F3DB00000000000000000000000000000000010000000000000000000000000000000000000000000000B0020000A80400000003000000000000011D1E8AF94257459C33565E5CC3F7E80000000000000000000000000000000001000000000000000000000000000000000000000000000058070000270000000003000000000000A13248C3C302524CA9F19F1D5D7723FC000000000000000000000000000000000300000000000000000000000000000000000000000000000200000000000000000000000000000000386A2C0F00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007F010000000000000002040300010000120FA20000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000000000000000000040000000200000038BD187249EADB0108000000000000000000000000000000000000000100000059080C06000880BC00386A2C0F00000000000000FE0F12D00A0000000800000000000000B00001000000000000000000F9010000030000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000FF00000000000000000000000000000000000000000000000000

 

 

 

 

 

 

This?

Yes. It's showing an error with the memory controller (Which is in the CPU). So try the voltage tweaks. Up to you which one you try first. 

Link to post
Share on other sites

21 hours ago, Bustedgizmo said:

Bjoolz, 

 

I had to do both voltage tweaks. It seems to be holding. 

 

Is this issue a sign that the CPU is dying? Or should this remedy handle this issue?

 

Also, thank you so much for your time and help. 

Doing both shouldn't be possible, you have to choose between either an offset or a static voltage. Unless I've just never seen a board that allows both, I don't really do any overclocking so that part of the BIOS has never been much of a focus for me so maybe I just never noticed.

 

As for if it could mean that the CPU has started failing, we don't know yet. Haven't had anyone it worked for come back yet and say that it stopped working at least. So no idea really.

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

×