Fix WHEA_UNCORRECTABLE_ERROR on Windows 10/11 (Exact Steps)

The fast answer. WHEA_UNCORRECTABLE_ERROR (stop code 0x00000124) means the hardware itself reported a fatal error to Windows — this is almost never fixed by a repair command. Start by removing every overclock: enter BIOS/UEFI setup, load the default settings (this also turns off XMP/EXPO memory profiles), save, and reboot. Then check temperatures and read the WHEA error record to see which component failed:

Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-WHEA-Logger'} | Format-List TimeCreated, Id, Message

If the crashes stop at stock settings, the overclock was unstable. If they don't, test the RAM and update the BIOS before suspecting the CPU, motherboard, or power supply.

Why this happens

Overclocking or XMP/EXPO — a CPU, GPU, or memory overclock (including a RAM profile the system can't hold) is the most common trigger on desktops.
Heat — a failed fan, clogged heatsink, or dried-out thermal paste pushes the CPU or VRMs past stable limits.
Defective or failing hardware — bad RAM, a degrading CPU, a faulty motherboard, or a PCIe device (GPU, NVMe SSD) throwing uncorrectable errors.
Power delivery — a weak or failing power supply, or CPU voltage set too low by undervolting.
Outdated BIOS or a driver — less common, but old firmware/microcode or a bad driver can make the hardware fail this way.

Step-by-step fix

Step 1 — Remove overclocks and load BIOS defaults

Enter BIOS/UEFI setup (usually Del or F2 at power-on) and choose Load Optimized Defaults or Load Setup Defaults (the name varies by maker). This resets CPU multipliers, voltages, and XMP/EXPO. Also remove any overclocking or undervolting utility running in Windows. Save, reboot, and use the PC normally. If WHEA crashes stop, re-enable changes one at a time to find the unstable one — or leave it at stock.

Step 2 — Check cooling and power

Confirm every fan spins, clean dust out of heatsinks and filters, and on a laptop make sure the vents aren't blocked. Watch CPU and GPU temperatures under load with a monitoring tool. On desktops, reseat the RAM, GPU, and the 24-pin and CPU power cables. If the crash happens under heavy load (gaming, rendering), a weak or failing power supply is a real suspect.

Step 3 — Read the WHEA error record

Windows logs each hardware error to the System event log under the source WHEA-Logger. Open Event Viewer → Windows Logs → System and filter by that source, or run this in an admin PowerShell:

Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-WHEA-Logger'} | Format-List TimeCreated, Id, Message

Read the Error Source, Error Type, and Reported by component lines in each message. "Processor Core" or "Cache Hierarchy Error" points at the CPU or its voltage; "PCI Express" errors point at a GPU, SSD, or other card in a PCIe slot; memory errors point at RAM. These fields narrow down which hardware to test — they don't by themselves prove a part is dead.

Step 4 — Test the RAM

Run the built-in Windows Memory Diagnostic (press Win+R):

mdsched.exe

Choose Restart now and check for problems. Press F1 during the test to select the Extended test mix for a more thorough pass. Results appear after Windows restarts. A clean pass doesn't fully clear the RAM — for a deeper test, boot MemTest86 from a USB stick and let it run several passes. If you have more than one stick, test them one at a time to find the bad one.

Step 5 — Update the BIOS and chipset drivers

Download the latest BIOS/UEFI firmware and chipset drivers from your PC or motherboard maker's support page for your exact model, and follow their update instructions. Firmware updates often ship CPU microcode and stability fixes. Do this on stable stock settings and never cut power during a BIOS flash.

Step 6 — Rule out drivers and system files

If the crashes began right after a driver install, open Device Manager, right-click the device, choose Properties → Driver → Roll Back Driver. If Windows crashes before you can do this, use WinRE Troubleshoot → Advanced options → Startup Settings → Restart, then press 4 for Safe Mode. Then repair system files from an admin Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

These fix software damage only. They won't fix a hardware fault, so don't expect them to stop a true WHEA crash.

Step 7 — Isolate the failing part

Still crashing at stock settings with good temperatures and clean RAM tests? Run your PC maker's built-in hardware diagnostics (most major brands include one) and the SSD maker's drive tool. On desktops, remove nonessential cards and drives, try a known-good power supply, and swap the GPU if the WHEA record named a PCI Express device. If the record keeps naming the processor core at stock settings, the CPU or motherboard is likely failing — that's a warranty or replacement job, not a software fix.

Data safety: A PC throwing WHEA crashes can halt mid-write at any moment, and if the fault is in the RAM or storage path, files being written can be corrupted. Back up your important files now, while the machine still runs, before you stress-test it, flash the BIOS, or run long diagnostics. If the drive itself shows errors, image it to a known-good external disk first, and never run repairs on the only copy of irreplaceable data.

GRAM tip: WHEA crashes usually leave Windows bootable between crashes, so GRAM applies directly. Plug in GRAM — a free portable repair toolkit that runs from a USB inside Windows — to analyze the crash dumps, pull the WHEA-Logger history from the event logs, and check SMART disk health, then let its AI agent help pin down whether it's the overclock, RAM, CPU, or a PCIe device.

Download GRAM free See AI pricing →

FAQ

Can I fix this without a second working computer?

Yes. Most of these steps happen in BIOS setup or inside Windows, which usually still boots between WHEA crashes. If it crashes before the desktop, Windows Recovery (WinRE) lives on the broken PC itself — force three failed boots to trigger Automatic Repair, or boot from any Windows install USB — and you can start Safe Mode from there. You'd only need another PC to create a MemTest86 USB or a Windows install USB. (GRAM runs inside Windows rather than from boot media — use it once the machine boots to check disk health and confirm the root cause.)

Does WHEA_UNCORRECTABLE_ERROR mean my CPU is dead?

Not necessarily. The error means a hardware component reported a fatal fault, but overclocks, XMP profiles, heat, and power problems cause it far more often than a dead CPU. Only suspect the CPU or motherboard after stock settings, good cooling, clean RAM tests, and an updated BIOS still give the same WHEA record.

Will sfc or DISM fix a WHEA error?

Rarely. They repair Windows system files, and this stop code comes from the hardware error architecture reporting a hardware fault. Run them to rule out software damage, but don't expect them to cure a true hardware problem.

Is it safe to leave XMP/EXPO turned off?

Yes. With XMP/EXPO off the RAM runs at its standard default speed, which is slower but within spec. If the crashes stop, you can try the profile again after a BIOS update, or set a slightly lower memory speed, and test stability before relying on it.