Fix WHEA_UNCORRECTABLE_ERROR on Windows 11
Short answer: WHEA_UNCORRECTABLE_ERROR (0x00000124) is one of the few BSODs that genuinely means hardware — the CPU reported an error it could not self-correct. Check Event Viewer under WHEA-Logger for the source. Common culprits are unstable overclocks or XMP/EXPO memory profiles (disable them first), an overheating CPU, a failing PSU, or on Intel 13th/14th-gen chips the known voltage degradation.
WHEA stands for Windows Hardware Error Architecture. When you see this blue screen, the CPU itself reported a hardware error that it couldn’t correct on its own. Stop code 0x00000124. This is one of the few BSODs that genuinely means hardware — not a driver crash, not a software bug, not a corrupted file. The processor’s error-correcting hardware detected something wrong with either the CPU, the motherboard’s voltage regulation, or the memory bus, and it couldn’t self-correct. Windows had no choice but to crash.
Check Event Viewer for the specifics. Win+X, Event Viewer, Windows Logs, System. Look for WHEA-Logger events — they contain an “Error Source” field that tells you what hardware subsystem reported the problem. “Machine Check Exception” (MCE) means the CPU core itself faulted. “Corrected Machine Check” means the CPU has been catching and fixing errors silently, and you only blue-screened because it finally got one it couldn’t fix. “PCIe Bus Error” points at a graphics card, NVMe drive, or other PCIe device losing connection.
If Event Viewer shows kernel corruption rather than MCE or PCIe errors, you might be looking at CRITICAL_STRUCTURE_CORRUPTION instead — similar territory but different diagnostic path, especially on Intel 13th/14th gen.
A guy’s Ryzen 7 5800X build was crashing once every two or three days. Event Viewer showed MCE errors on Core 4 specifically. Every single crash, same core. Swapped RAM sticks, tested the PSU, ran every software diagnostic. None of that mattered because the CPU die itself had a defect. AMD warranty replacement fixed it. Took three weeks to get the chip back but the new one has been clean for eight months.
Overclocking and Voltage
If you’re overclocking — CPU, RAM with XMP/EXPO, GPU — this is the crash that tells you to stop. An unstable overclock is the single most common trigger for WHEA errors on otherwise healthy hardware. The CPU is running at a voltage or frequency it can’t reliably sustain, and the error correction catches it.
Disable XMP in BIOS first. If the crashes stop, XMP was pushing the memory controller past what your particular CPU can handle. Try the default 2133 MHz (DDR4) or 4800 MHz (DDR5) for a week. If stable, re-enable XMP at a lower speed — step down one tier at a time until you find what’s stable.
If you’ve overclocked the CPU manually, reset everything to stock. If you haven’t touched anything, check whether your motherboard’s “auto overclock” feature is enabled — many boards ship with something like ASUS’s “AI Overclock Tuner” or MSI’s “Game Boost” turned on by default, pushing the CPU beyond Intel or AMD’s spec without telling you. Disable it.
Genuine Hardware Failure
If you’re running everything at stock settings and WHEA errors keep happening, something is actually failing. The Event Viewer MCE details narrow it down:
CPU: errors consistently naming the same core, or showing “MISCV” (Miscellaneous Register Valid) with cache-related codes. Intel and AMD both have warranty programs for defective CPUs. If the chip is under three years old, contact the manufacturer.
Motherboard VRM: errors during load but not at idle, especially if the VRM heatsink is extremely hot to touch. The voltage regulators are failing to deliver clean power to the CPU. VRM failures are more common on budget boards paired with high-TDP processors — a 65W board trying to run a 125W chip.
PCIe: “Bus/Interconnect Error” in Event Viewer. Could be a GPU not seated properly, an NVMe SSD with a bad connection, or a dying motherboard PCIe slot. Reseat the GPU first — pull it out, clean the contacts with isopropyl alcohol, push it back firmly until both clips lock. Try a different PCIe slot if your board has one.
Install HWiNFO and check if thermal throttling or abnormal voltages precede the crashes. CPU hitting 100°C? The overheating is the real problem and WHEA is the symptom. VCore fluctuating wildly under load? PSU or VRM issue.
This is the one BSOD where “run SFC and update drivers” is genuinely useless advice. WHEA means hardware. If the Event Viewer points at a specific component and you can’t fix it yourself, send us the WHEA-Logger events and we can tell you exactly what’s failing and whether it’s worth repairing or replacing.
Frequently Asked Questions
What does WHEA_UNCORRECTABLE_ERROR mean?
The CPU itself detected a hardware error it couldn't self-correct. WHEA stands for Windows Hardware Error Architecture. Unlike most blue screens caused by driver bugs, this one genuinely points at hardware — the processor, motherboard voltage regulators, or PCIe bus reported a fault that Windows couldn't recover from.
Is WHEA_UNCORRECTABLE_ERROR always hardware?
Almost always. The most common exception is an unstable overclock — XMP memory profiles, CPU overclocks, or motherboard auto-overclock features pushing components past their stable limit. Reset everything to stock first. If WHEA errors continue at stock settings with no overclocking, it's genuine hardware failure.
Can XMP cause WHEA blue screens?
Yes. XMP pushes the memory controller beyond Intel or AMD's official specification. Some CPUs handle it, some can't. Disable XMP in BIOS and run at default speeds for a week. If crashes stop, your CPU's memory controller can't sustain the XMP profile — try re-enabling at a lower speed.
How do I find which hardware is failing from WHEA?
Open Event Viewer, Windows Logs, System, filter for WHEA-Logger events. The Error Source field tells you: Machine Check Exception means CPU. PCIe Bus Error means GPU, NVMe, or slot issue. If the same CPU core is named in every crash, the CPU die has a defect — contact the manufacturer for warranty replacement.