
Getting a WHEA_UNCORRECTABLE_ERROR blue screen on Windows? This crash means Windows detected a hardware fault it could not recover from. Unlike most blue screens, this one points directly at your hardware or the drivers controlling it with a stop code of 0x00000124.
WHEA stands for Windows Hardware Error Architecture, the part of Windows that monitors CPU, RAM, and device health. When it detects a critical fault, Windows stops everything and shows this blue screen rather than risk corrupting your data.
This guide covers the most effective fixes in order from quickest to most thorough. Most people solve it by Fix 2 or Fix 3. If your PC is overclocked, start with Fix 1 first.
What This Error Means at a Glance
- Windows detected an unrecoverable hardware error and forced a restart.
- Most common causes: overclocking, faulty RAM, bad device driver, or overheating CPU.
- Less common causes: failing hard drive or SSD, corrupted system files, bad Windows update.
- This is a hardware-level crash, not a typical app or software error.
- Affects Windows 10 and Windows 11. More common on overclocked or custom-built PCs.
Error Type
BSOD / Hardware
Root Cause
CPU / RAM / Driver
Affects
Windows 10 / 11
Difficulty
Beginner to advanced
Time to Fix
10 min – several hours
Video: How to Fix WHEA_UNCORRECTABLE_ERROR on Windows
Watch the full fix walkthrough for WHEA_UNCORRECTABLE_ERROR on Windows 10 and 11, covering the overclocking reset, driver update, RAM test, and SFC repair steps shown below.
What Causes WHEA_UNCORRECTABLE_ERROR?
This error has more possible causes than most blue screens. Check the list below and pick the fix that best matches your situation before working through the numbered steps.
Overclocking (Most Common)
Running your CPU, RAM, or GPU faster than stock speeds puts extra stress on the hardware. Even a previously stable overclock can cause this error after a Windows update, temperature spike, or power fluctuation.
Faulty or Incompatible RAM
Bad memory is one of the top hardware causes. This includes physically failing RAM sticks, RAM running at the wrong speed for your motherboard, or mismatched sticks that are not compatible with each other.
Bad or Outdated Drivers
GPU drivers, chipset drivers, and storage controller drivers are the most common driver culprits. A buggy driver update can trigger this error even on hardware that was working fine the day before.
Overheating CPU or GPU
When a processor gets too hot, it can trigger hardware-level errors that cause this blue screen. Common on laptops with blocked vents, desktops with dried-out thermal paste, or rigs running demanding workloads in a hot room.
Failing Hard Drive or SSD
A drive that is starting to fail can trigger hardware errors as Windows tries to read or write to bad sectors. This is more common on older HDDs but can also happen with SSDs that are near end of life.
Corrupted System Files
A failed Windows update, a sudden shutdown during an update, or malware can corrupt core Windows files. This is less common than hardware causes but worth checking if all hardware tests come back clean.
How to Fix WHEA_UNCORRECTABLE_ERROR
Work through these fixes in order. If your PC is overclocked, go straight to Fix 1 first. Otherwise start from the top and move down. Most people are done by Fix 3 or Fix 4.
Quick Checklist: What to Try First
| Fix | Time Needed | Best If |
|---|---|---|
| Disable overclocking / XMP | 5 – 10 min | PC is overclocked or XMP is enabled in BIOS |
| Update or roll back drivers | 10 – 20 min | Error started after a driver update |
| SFC and DISM scan | 15 – 30 min | Error appeared after a Windows update or crash |
| RAM test (MemTest86) | 1 – 3 hours | Crashes happen randomly with no obvious trigger |
| Check CPU temperature | 10 – 15 min | PC crashes under load (gaming, rendering) |
| Check drive health | 10 – 20 min | PC is old, drive makes clicking sounds, or slow to boot |
| Windows Update and BIOS update | 20 – 45 min | System is behind on updates or BIOS is very old |
Still Getting WHEA_UNCORRECTABLE_ERROR? Advanced Steps
Read the minidump file to identify the exact fault
Every BSOD creates a small crash log called a minidump. Open Event Viewer (search in Start), go to Windows Logs, then System, and look for Critical errors near the time of the crash. You can also use WhoCrashed (free tool from Resplendence) to read minidump files in plain language and see which driver or component caused the fault.
Run a malware scan
Malware can corrupt drivers and system files in ways that produce hardware-looking errors. If no hardware test has found a problem, run a full scan with Windows Defender before going further. For a deeper scan that also checks for damaged registry entries, Malwarebytes Premium is worth trying.
🔧 Tip: Want a faster way? Malwarebytes Premium can detect leftover infections and damaged system components in one scan.
Perform a clean boot to isolate the cause
A third-party service or startup program could be triggering the fault. Open System Configuration (search msconfig), go to Services, check Hide all Microsoft services, click Disable all, then restart. If the crashes stop, re-enable services one group at a time to find the conflict.
Test with one RAM stick and check other slots
If MemTest86 passed but crashes continue, try moving your RAM to different slots on the motherboard. A faulty RAM slot on the motherboard can cause the same symptoms as bad RAM itself. Consult your motherboard manual for the correct dual-channel slot pairing.
Reset Windows as a last resort
If all hardware tests come back clean and the crashes persist, a Windows reset (Settings, System, Recovery, Reset this PC) with the “Keep my files” option reinstalls Windows while leaving your personal files in place. If crashes continue after a clean Windows install, the fault is hardware and you will need to isolate and replace the failing component.
Frequently Asked Questions
What does WHEA_UNCORRECTABLE_ERROR mean?
It means Windows detected a hardware error it could not recover from. WHEA stands for Windows Hardware Error Architecture. The blue screen appears when the CPU, RAM, storage, or a device driver reports a critical fault that Windows cannot work around. It is not a software crash like most blue screens.
Is WHEA_UNCORRECTABLE_ERROR caused by hardware or software?
Usually hardware or drivers. Overclocking is the most common trigger. Faulty RAM, a failing drive, a corrupted device driver, or a CPU running too hot can all cause it. In some cases a bad Windows update or driver conflict is the culprit, which makes it fixable without replacing any hardware.
Can overclocking cause WHEA_UNCORRECTABLE_ERROR?
Yes, and it is the single most common cause. If your CPU, RAM, or GPU is running above stock speeds, resetting everything to default is the first thing to try. Even a “stable” overclock can become unstable after a Windows update or temperature change.
How do I know if my RAM is causing WHEA_UNCORRECTABLE_ERROR?
Run Windows Memory Diagnostic or MemTest86 overnight. If errors show up, your RAM is the likely cause. You can also try removing one RAM stick at a time and booting to see if the crashes stop with a specific stick removed.
Will WHEA_UNCORRECTABLE_ERROR damage my PC?
The blue screen itself will not damage your hardware. Windows forces a restart to protect your system when it detects the error. However, if the underlying cause is overheating or failing hardware, ignoring it repeatedly can shorten the life of those components.
Can a driver cause WHEA_UNCORRECTABLE_ERROR?
Yes. GPU drivers, chipset drivers, and storage controller drivers are common culprits. If the blue screen started after a driver update, roll it back. If you are not sure which driver, use DDU (Display Driver Uninstaller) to fully remove GPU drivers and reinstall the latest clean version.
Is WHEA_UNCORRECTABLE_ERROR fixable without reinstalling Windows?
In most cases, yes. Disabling overclocking, updating or rolling back drivers, running SFC and DISM, and testing RAM resolves the error for the majority of users. A Windows reinstall is only needed if system files are deeply corrupted and no other fix works.
Related Windows Error Fixes
- Fix: DRIVER_IRQL_NOT_LESS_OR_EQUAL
- Fix: CRITICAL_PROCESS_DIED
- Fix: Error 0xc000007b (Application was unable to start correctly)
- Fix: CrowdStrike Falcon BSOD Error on Windows
- Fix: Error 0xc0000005 (Application unable to start correctly)
- Fix: Error 0x80070005 (Access Denied)
- Fix: Error Code 43 (Device Manager)
Still stuck? Leave a comment below or contact us directly and we will help you figure it out.
Discover more from Windows Mode
Subscribe to get the latest posts sent to your email.