Fixes / Windows · Checked September 30, 2026

Windows WHEA_UNCORRECTABLE_ERROR: what it means and how to fix it

Short answer

WHEA_UNCORRECTABLE_ERROR (stop code 0x124) means the processor or another hardware component reported a fatal error that Windows could not recover from, so it stopped the PC. It is almost always hardware: overclocking, XMP/EXPO memory profiles, heat, or a failing CPU, RAM or drive. The most likely fix is to reset the BIOS/UEFI to defaults, remove any overclock, and update the BIOS.

What this message means

WHEA stands for Windows Hardware Error Architecture, the part of Windows that receives error reports straight from the hardware. Bug check 0x124 means a component (usually the CPU, but also memory, the PCI Express bus or a device on it) signalled an error it could not correct, and Windows stopped rather than risk corrupting your data. Microsoft's documentation says it is typically caused by physical hardware: heat, defective memory, a failing processor, or overclocking. A driver causing it is possible but less likely. On Windows 11 24H2 and later the crash screen is black instead of blue, but the stop code is the same.

Common causes

Cause	How to tell
Overclocking, undervolting or an XMP/EXPO memory profile the system can't hold stable	Crashes began after enabling XMP/EXPO, a CPU overclock, a tuning utility (Intel XTU, Ryzen Master, MSI Afterburner) or a motherboard "auto OC" / "enhanced" performance mode. Crashes often happen under load such as gaming or rendering.
Intel Core 13th or 14th gen desktop CPU instability (Vmin shift) on an old BIOS	You have a Core i5/i7/i9 13xxx or 14xxx desktop CPU, crashes are random or during game shader compilation, and your BIOS is older than late 2024. Event Viewer shows WHEA-Logger errors naming a Processor Core.
Overheating or power delivery problems	Crashes happen during heavy load, fans are loud or clogged with dust, CPU temperatures reach 95 to 100 °C in a monitoring tool, or the PC also shuts off abruptly. On laptops, it may only happen on battery or only when charging.
Faulty or badly seated RAM	Windows Memory Diagnostic or MemTest86 reports errors, or the WHEA-Logger event names Memory as the component. Crashes stop when you run with one stick removed.
Failing CPU, graphics card, SSD or other PCI Express device	Event Viewer shows WHEA-Logger events pointing at a PCI Express Root Port or a specific device, the error persists at full default settings, or it follows one component when you swap parts.
Outdated BIOS, chipset or storage driver (less common)	Crashes started right after a Windows feature update or new driver, and a BIOS or chipset driver update is available on the PC or motherboard maker's support page.

How to fix it

1. Check Event Viewer to see which part reported the error

Right-click the Start button and select Event Viewer.
Go to Windows Logs > System, then select Filter Current Log in the right pane.
In Event sources, tick WHEA-Logger and select OK.
Open the most recent error (often Event ID 18, "A fatal hardware error has occurred") and read the Component line: Processor Core, Memory, or PCI Express Root Port.
Note the Error Source (for example Machine Check Exception) and use the component to decide which fix below to start with.

2. Remove overclocks and reset the BIOS/UEFI to defaults

Windows 10 and 11. On Windows 10 the path is Settings > Update & Security > Recovery.

Close or uninstall any overclocking or tuning utility (Intel XTU, Ryzen Master, MSI Afterburner, vendor "game boost" tools).
In Windows 11 go to Settings > System > Recovery, and next to Advanced startup select Restart now.
Choose Troubleshoot > Advanced options > UEFI Firmware Settings > Restart.
In the BIOS, choose Load Optimized Defaults (or Load Setup Defaults), and make sure XMP/EXPO is disabled and any CPU overclock or undervolt is off.
Save and exit (usually F10) and use the PC normally. If the crashes stop, re-enable XMP/EXPO alone later to see if it is the trigger.

3. Update the BIOS and chipset drivers

Find your exact model: press Windows + R, type msinfo32, and note System Model (or BaseBoard Product) and BIOS Version/Date.
Go to the PC or motherboard maker's support page for that model and download the latest BIOS and chipset driver.
If you have an Intel Core 13th or 14th gen desktop CPU, install a BIOS containing Intel microcode 0x12F or later and use the Intel Default Settings profile if the BIOS offers one.
Flash the BIOS using the maker's instructions, on mains power, without interrupting it.
Install the chipset driver and restart.

4. Check temperatures and cooling

Install a monitoring tool such as HWiNFO and watch CPU and GPU temperatures while gaming or under load.
If the CPU approaches 95 to 100 °C, shut down and clean dust from fans, heatsinks and filters.
Confirm every fan spins, including the CPU cooler and (on liquid coolers) the pump.
On a desktop, make sure all power connectors to the motherboard and graphics card are fully seated.
If temperatures stay high after cleaning, reseat the cooler with fresh thermal paste or have the laptop serviced.

5. Test and reseat the memory

Select Start, type Windows Memory Diagnostic, open it, and choose Restart now and check for problems (save your work first).
After Windows restarts, check results in Event Viewer > Windows Logs > System, source MemoryDiagnostics-Results.
For a more thorough test, run MemTest86 from a USB stick for at least 4 passes.
On a desktop, power off, unplug, and reseat each RAM stick. If errors appear, test one stick at a time to find the bad one and replace it.

6. Update drivers, check the drive and remove new hardware

Disconnect any recently added hardware (graphics card, PCIe card, USB devices) and see if the crashes stop.
Right-click Start > Device Manager, look for devices with a yellow exclamation mark, right-click them and select Update driver.
Install the latest graphics driver directly from NVIDIA, AMD or Intel.
Open Terminal (Admin) and run chkdsk C: /f /r, then restart to let it scan the system drive.
Install pending updates in Settings > Windows Update (Windows 10: Settings > Update & Security > Windows Update).

Next time, skip the search

Crade is an AI assistant for Mac and Windows that sees your screen. When a message like this pops up, ask “what does this mean?” and it explains the exact error in front of you, step by step.

Download Crade

Still not fixed?

If the error continues at full default settings with a current BIOS, a component is most likely failing. Crash dumps are saved in C:\Windows\Minidump; the WHEA-Logger event and the dump are what a technician or the manufacturer will ask for. If the PC or CPU is under warranty, contact the PC maker or CPU vendor (Intel extended warranties for affected 13th and 14th gen desktop CPUs). Otherwise, test by swapping parts one at a time, starting with RAM and the power supply, or take it to a repair shop with the Event Viewer details.

Questions people ask

Does WHEA_UNCORRECTABLE_ERROR mean my CPU is dead?

Not necessarily. It means the CPU reported a hardware error, which is often caused by overclocking, XMP settings, heat or an outdated BIOS rather than a dead chip. If it keeps happening at default settings with a current BIOS, the CPU or another part may be failing.

Can a software or driver problem cause WHEA_UNCORRECTABLE_ERROR?

It is possible but uncommon. Microsoft states this bug check is typically physical hardware, so rule out overclocking, heat and memory first, then update drivers and the BIOS.

Will reinstalling Windows fix it?

Usually not, because the error comes from the hardware, not Windows files. Reinstall only after the hardware checks come back clean.

Why do I get this error on an Intel 13th or 14th gen CPU?

Many 13th and 14th gen Core desktop CPUs became unstable because of excessive voltage requests. Intel released microcode fixes through BIOS updates (0x12F or later), and CPUs already damaged may need a warranty replacement.

Is it safe to keep using my PC?

Frequent crashes risk corrupting open files, so back up important data now. Keep using it lightly while you test, and stop overclocking or heavy loads until the cause is found.

Sources

Related errors