What WHEA_UNCORRECTABLE_ERROR actually means
WHEA stands for Windows Hardware Error Architecture. When the CPU reports a machine-check error it can’t fix, Windows stops with WHEA_UNCORRECTABLE_ERROR. The software isn’t the root cause here; Windows is reporting what the hardware said.
In practice, the most common triggers are CPU or memory overclocks (including automatic “performance boost” and XMP/EXPO profiles), outdated BIOS microcode, insufficient cooling or power, and drives or CPUs that are starting to fail. Event Viewer’s WHEA-Logger entries often name the component (cache, bus, memory, PCIe).
How it shows up
- Blue screen: “Stop code: WHEA_UNCORRECTABLE_ERROR”.
- Crashes under heavy load (gaming, rendering) or at idle with aggressive undervolts.
- Event Viewer shows WHEA-Logger errors.
Why WHEA_UNCORRECTABLE_ERROR happens
- Overclocking, undervolting or memory XMP/EXPO instability.
- Outdated BIOS/UEFI or chipset firmware.
- Overheating or an inadequate power supply.
- Failing CPU, RAM, motherboard or storage.
How to fix it, step by step
- Return to stock settingsEnter the BIOS/UEFI and choose Load Optimized Defaults. Remove tuning tools (Ryzen Master, Intel XTU, MSI Afterburner overclocks).
- Update BIOS and chipset driversInstall the latest BIOS from the motherboard or PC maker and current chipset drivers. Many CPU stability fixes ship as microcode updates.
- Check temperatures and powerMonitor CPU temperature under load with a tool like HWiNFO. Sustained readings near the CPU's limit point to cooling problems. Make sure the PSU is adequate and cables are seated.
- Read WHEA-Logger eventsOpen Event Viewer → Windows Logs → System and filter for source WHEA-Logger. The error type helps identify CPU, memory or PCIe devices.
- Test RAM and storageRun
mdsched.exe, and check drive health with the manufacturer's tool or runGet-PhysicalDiskin PowerShell (the old wmic command is removed in recent Windows 11 versions). - Get hardware checkedIf crashes persist at default settings with normal temperatures, have the CPU, RAM and motherboard tested. This error can indicate a failing part.
Keeping it from coming back
Keep BIOS updated, keep temperatures in check, and validate any overclock with long stability tests.
