WHEA_UNCORRECTABLE_ERROR Frustration
1 hour ago, Bustedgizmo said:
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.



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 accountSign in
Already have an account? Sign in here.
Sign In Now