How to Fix WHEA_UNCORRECTABLE_ERROR on Windows
In this article
WHEA_UNCORRECTABLE_ERROR is a Windows blue screen caused by a hardware fault Windows can't correct: usually the CPU, RAM, drivers, BIOS settings, or a failing drive. Work through the software fixes first; if it persists, suspect failing hardware and protect your data before it's lost.
- Update Windows, chipset, and storage drivers, and reset overclocks to default in BIOS.
- Check temperatures and reseat RAM; run Windows Memory Diagnostic to rule out bad RAM.
- If the error returns and your drive is the cause (read errors, slow boots, bad sectors), back up now and consider professional hard drive data recovery.
The WHEA_UNCORRECTABLE_ERROR is a Windows blue screen (BSOD) that means your computer detected a hardware problem it can't correct on its own. WHEA stands for Windows Hardware Error Architecture. When this stop code appears, Windows is telling you that something physical failed: your CPU, RAM, hard drive, SSD, or motherboard. This is one of several blue screen errors that can indicate storage problems. The good news is that some causes are fixable with basic troubleshooting. Overheating, outdated drivers, bad BIOS settings. The bad news? If the error keeps coming back, you're probably looking at a hardware failure. And if your storage drive is the culprit, your data could be at risk.
Sometimes it's a simple overheating issue and the customer fixes it by cleaning out dust. Other times, the drive has bad sectors spreading across the platters, and recovery is the only way to save the files. The key is figuring out which situation you're in before you lose anything important.
If you're getting this blue screen repeatedly and you're worried about your data, our data recovery team can evaluate your drive. No obligation, just answers.
What Is the WHEA_UNCORRECTABLE_ERROR?
WHEA is a system built into Windows (Vista and later) that monitors hardware components for errors. Your CPU, memory controller, PCIe bus, and storage controllers all report errors through WHEA. Most of the time, WHEA catches and corrects small errors silently in the background. You never even notice.
The blue screen happens when WHEA encounters an error it cannot correct. Something has gone wrong at the hardware level, and Windows decides the safest thing to do is stop everything immediately rather than risk data corruption or further damage. That's what "uncorrectable" means. Windows tried to fix it, failed, and pulled the emergency brake.
The stop code is 0x00000124. You'll usually see it displayed on the blue screen itself, along with the text WHEA_UNCORRECTABLE_ERROR. Windows 10 and 11 show a sad face emoji and the stop code. Older versions show the classic wall of white text on blue.
What Windows Is Actually Telling You
When you get this BSOD, Windows creates a memory dump file with details about the error: which component failed, the error type, and sometimes a specific error code. Most people never look at these dumps. But tools like WinDbg from Microsoft or the free BlueScreenView utility can parse them and tell you exactly which component flagged the error.
Common Causes of This Blue Screen
The WHEA_UNCORRECTABLE_ERROR has several possible causes. Some are cheap fixes. Others mean a trip to the repair shop or data recovery lab.
Overheating (CPU or GPU)
Your CPU has built-in thermal protection. When it gets too hot, it starts throttling performance. If it gets dangerously hot (typically above 100C), it triggers a machine check exception, which WHEA catches and reports as uncorrectable.
Common overheating causes:
- Dust buildup in fans and heatsinks
- Dried-out thermal paste (common on laptops older than 3-4 years)
- Failed or dying CPU fan
- Blocked air vents (laptops on soft surfaces like beds or couches)
- Overclocked CPU without adequate cooling
Faulty or Failing RAM
RAM errors come in two types: soft errors (caused by electrical interference, usually temporary) and hard errors (caused by physical damage to the memory cells, permanent). WHEA can't correct hard RAM errors, so you get the blue screen.
RAM failures can be random and frustrating. Your computer might run fine for hours, then crash. Then run fine for two more days. Then crash three times in one afternoon. That inconsistency is actually a strong sign of bad RAM.
Hard Drive or SSD Failure
This is the cause that worries us most from a data recovery standpoint. When your storage drive starts failing, the storage controller reports read/write errors to WHEA. If enough errors stack up or a critical sector becomes unreadable, WHEA flags it as uncorrectable.
For hard drives, this usually means bad sectors are spreading. The drive's heads can't read certain areas of the platters, and the drive's own error correction can't compensate anymore. For SSDs, it often means the NAND flash cells are wearing out. Check our guide on signs your SSD is failing for the full list of warning signs. Each cell has a limited number of write cycles, and once they're exhausted, the cell can't hold data reliably.
If your WHEA errors coincide with slow file access, missing files, or strange noises from your hard drive, your drive is likely failing. Don't ignore that combination of symptoms.
Overclocking Instability
If you've overclocked your CPU, GPU, or RAM, the WHEA error might just be telling you that your overclock isn't stable. Pushing hardware beyond its rated specifications increases the chance of computation errors. At stock speeds, the error correction built into modern CPUs can handle occasional bit flips. At overclocked speeds, the error rate goes up and the correction can't keep pace.
Easy test: reset everything to stock speeds and see if the error goes away.
Driver or Firmware Issues
Outdated or buggy drivers, especially for your storage controller, chipset, or GPU, can trigger WHEA errors. The driver sends bad commands to the hardware, the hardware responds with an error, and WHEA catches it. BIOS/UEFI firmware bugs can cause similar problems.
Motherboard Problems
Failing capacitors, damaged PCIe slots, or a degrading voltage regulator module (VRM) on the motherboard can all produce uncorrectable hardware errors. These are harder to diagnose because they don't always show obvious physical signs. Sometimes a motherboard works fine at idle but fails under load when the VRMs can't deliver stable power to the CPU.
Step-by-Step Fixes for WHEA_UNCORRECTABLE_ERROR
Start with the simplest fixes first. Work your way down the list. If a step resolves your issue, you're done.
1 Check Your Temperatures
Download a free monitoring tool like HWiNFO or Core Temp. Check your CPU temperature under load. If it's regularly hitting 90C or above, overheating is your likely culprit.
Fix: Clean dust from your fans and heatsink with compressed air. If you have a desktop, consider reapplying thermal paste. For laptops, make sure vents aren't blocked and consider a cooling pad.
2 Remove Any Overclocks
If you've overclocked your CPU, RAM, or GPU, reset everything to default speeds. Enter your BIOS/UEFI (usually by pressing DEL or F2 during boot) and load optimized defaults. Also check if XMP/EXPO is enabled for your RAM. While XMP is technically "supported" by the memory manufacturer, it's still an overclock of the memory controller. Try disabling it temporarily.
Fix: Load BIOS defaults. If the WHEA error stops, your overclock was unstable.
3 Run Windows Memory Diagnostic
Press Win + R, type mdsched.exe, and hit Enter. Choose "Restart now and check for problems." Windows will reboot and test your RAM. This takes about 15-20 minutes.
For a more thorough test, download MemTest86 and boot from a USB drive. Let it run for at least 4 passes. If it finds errors, you have bad RAM.
Fix: If you have multiple RAM sticks, remove them one at a time and test with each individually. This identifies the bad stick. Replace it.
4 Update Your Drivers
Outdated chipset, storage controller, and GPU drivers can trigger WHEA errors. Go to your motherboard manufacturer's website (not Windows Update) and download the latest chipset drivers. Do the same for your GPU from NVIDIA, AMD, or Intel.
Pay special attention to your storage controller drivers. If you're running an NVMe SSD, make sure you have the manufacturer's NVMe driver installed rather than the generic Microsoft one. Samsung, Western Digital, and Intel all have their own NVMe drivers that are more stable.
5 Update BIOS/UEFI Firmware
Motherboard manufacturers regularly release BIOS updates that fix hardware compatibility issues. Check your motherboard manufacturer's support page for the latest BIOS version. Follow their instructions carefully. A failed BIOS update can brick your motherboard, so don't skip any steps and don't lose power during the process.
Note: On laptops, check the manufacturer's support page (Dell, HP, Lenovo, ASUS, etc.) for both BIOS and firmware updates specific to your model.
6 Check Your Hard Drive or SSD Health
Open Command Prompt as Administrator and run:
wmic diskdrive get status
If it says anything other than "OK," your drive has reported a problem. For more detail, download CrystalDiskInfo (free). It reads the SMART data from your drive and gives you a health status. Look for:
- Reallocated Sector Count (for HDDs). Any number above 0 means the drive has bad sectors.
- Current Pending Sector Count. Sectors waiting to be reallocated. Bad sign.
- Media Wearout Indicator / Percentage Used (for SSDs). Shows how much life the SSD has left.
- Overall status showing "Caution" or "Bad." Back up your data immediately.
For a deeper guide on this, read our post on signs your hard drive is failing.
7 Run SFC and DISM
These won't fix hardware problems, but they'll rule out corrupted Windows system files that might be misreporting errors. Open Command Prompt as Administrator and run:
sfc /scannow
Wait for it to finish, then run:
DISM /Online /Cleanup-Image /RestoreHealth
If SFC finds and fixes corrupted files, restart and monitor for the WHEA error.
Advanced Fixes for Persistent WHEA Errors
If the basic steps didn't resolve your issue, the problem is deeper. These fixes require a bit more technical knowledge.
Reseat PCIe Cards and Check Connections
If you recently installed or moved a GPU, NVMe SSD, or any PCIe expansion card, reseat it. A card that's not fully seated in the slot can cause intermittent hardware errors. Check that all power cables are firmly connected too. A loose GPU power connector causes voltage drops under load.
Test with Minimal Hardware
Strip your system down to basics. One stick of RAM, no GPU (use integrated graphics), disconnect all drives except boot drive. If the WHEA error stops, add components back one at a time to find the culprit. Tedious but effective.
Check Event Viewer for WHEA Details
Windows logs detailed WHEA error information in Event Viewer. Here's how to find it:
- Press Win + R, type eventvwr.msc, press Enter.
- Navigate to Windows Logs > System.
- Look for entries with Source = "WHEA-Logger" and Level = "Error" or "Critical".
- Click on an entry and check the Details tab.
The error details will tell you which component reported the failure. Common entries include:
| Error Type | Component | What It Means |
|---|---|---|
| Machine Check Exception | CPU | Processor detected an internal error it can't correct |
| PCIe Error | GPU, NVMe, or expansion card | Device on the PCIe bus reported a failure |
| Memory Error | RAM | Memory controller found uncorrectable bit errors |
| NMI Error | Various | Non-maskable interrupt, often power or bus related |
| Generic Error | Storage or chipset | Broad category, needs further investigation |
Update or Reinstall Storage Controller Drivers
This one catches people off guard. Windows ships with generic storage drivers (storahci, stornvme) that work but aren't always optimized for your specific hardware. Your motherboard manufacturer or SSD manufacturer might have a dedicated driver that handles error correction better.
For Intel systems, check for the Intel Rapid Storage Technology (RST) driver. For AMD systems, look for AMD RAID/AHCI drivers. For NVMe SSDs, Samsung's NVMe driver, WD's dashboard driver, or Intel's SSD Toolbox driver can all improve stability.
When the WHEA Error Points to a Dying Drive
This is where things get serious. If your WHEA_UNCORRECTABLE_ERROR is caused by a failing hard drive or SSD, the blue screen is just the symptom. The real problem is that your data is sitting on a device that's breaking down.
Signs Your Drive Is the Problem
Look for these alongside the WHEA blue screen:
- Slow boot times. Your computer takes noticeably longer to start up.
- File access delays. Opening folders or files takes seconds instead of being instant.
- Disappearing files. Files or folders that were there yesterday are suddenly gone.
- Clicking or grinding noises from a hard drive (SSDs are silent, so no sound doesn't mean no problem).
- CrystalDiskInfo showing "Caution" or "Bad" status.
- CHKDSK finding bad sectors every time it runs.
- Frequent freezes before the blue screen appears.
If you're seeing three or more of these symptoms alongside the WHEA error, your drive is failing. It's not a question of if, but when. Could be days. Could be hours.
Hard Drive vs. SSD Failure Patterns
Hard drives fail mechanically. Heads degrade, motors weaken, platters develop bad spots. By the time WHEA triggers, the drive's own error correction has been overwhelmed for a while.
SSDs fail electronically. NAND flash cells wear out after thousands of write cycles. When cells fail faster than the controller can remap them, WHEA starts firing. SSD WHEA errors often mean the drive is running on borrowed time. For more on SSD failures, see our SSD data recovery page.
Protecting Your Data During WHEA Errors
If you're getting WHEA blue screens and you haven't backed up your data, do it now. Don't wait until after you've tried all the fixes. Back up first, troubleshoot second. A drive that's throwing WHEA errors today could be completely dead tomorrow.
If the Drive Still Boots
- Don't install anything on the failing drive. Writing new data forces the drive to use sectors that might be going bad.
- Copy your most important files first. Photos, documents, projects. Don't waste time on things you can re-download.
- Use an external drive or cloud storage. Copy files TO a different drive, not to another location on the same drive.
- Work quickly but calmly. The drive might not crash again for hours, or it might crash in five minutes. Prioritize ruthlessly.
If the Drive Won't Boot
Try booting from a Linux USB drive (Ubuntu or Linux Mint) to access files without loading Windows. Or pull the drive and connect it to another PC via a USB-to-SATA adapter. If the drive clicks, doesn't show up, or freezes when accessed, stop and contact a professional data recovery lab.
When You Need Professional Data Recovery
Some WHEA errors caused by dying drives can't be solved with a driver update or a temperature fix. When the storage hardware itself is failing, the only way to get your data back is professional recovery.
When to Call a Lab
- Your drive won't boot and won't show up as an external drive either.
- Your hard drive makes clicking, grinding, or beeping sounds.
- CrystalDiskInfo shows hundreds or thousands of reallocated sectors.
- You've tried booting from Linux USB and the drive errors out or freezes.
- The WHEA errors started after a power surge, drop, or liquid exposure.
Modern SSD recovery depends on a viable controller and encryption path. The lab assesses original-board repair, controlled reading, and firmware or virtual-translator access supported for the exact device. Independent raw-NAND chip-off cannot bypass encryption, and a lost controller path can make recovery impossible.
For pricing details, visit our data recovery pricing page.
Preventing Future WHEA Errors
Once you've fixed the immediate problem, a few habits will keep it from coming back.
Clean your cooling system regularly. Blow out your fans and heatsinks every 6 months. Replace thermal paste every 2-3 years on desktops, 3-4 years on laptops.
Use a UPS. Even a basic $50-60 UPS from APC or CyberPower protects against power surges and gives you time to shut down during an outage.
Monitor drive health. Install CrystalDiskInfo and let it run at startup. It alerts you when SMART data shows warning signs, so you can back up and replace a drive before it starts throwing blue screens.
Keep drivers and BIOS updated. Check for chipset and storage controller updates quarterly. BIOS updates less often, but always apply ones that address stability issues.
Stress test your overclocks. If you overclock, run Prime95 for CPU, MemTest86 for RAM, and FurMark for GPU. If it crashes during testing, dial it back. "It works fine most of the time" is not stable.
Frequently Asked Questions
Can the WHEA_UNCORRECTABLE_ERROR damage my data?
The error itself doesn't damage data. It's a warning that something already went wrong at the hardware level. But the underlying cause, whether it's a failing drive, bad RAM, or overheating CPU, absolutely can damage your data. A failing hard drive with bad sectors will continue to lose data as more sectors go bad. A bad RAM stick can corrupt files currently in memory. So while the blue screen is just a messenger, the message should be taken seriously.
Why does the WHEA error only happen during gaming or heavy workloads?
Heavy workloads push your hardware harder. Your CPU runs hotter, your GPU draws more power, your RAM handles more data simultaneously, and your storage drive reads and writes faster. Hardware that's marginally stable at idle can fail under load. This is especially common with overclocked systems or components that are on the edge of failure. If the error only happens under load, temperature and power delivery are the first things to check.
Is the WHEA_UNCORRECTABLE_ERROR always a hardware problem?
Bad drivers can cause hardware to misbehave, which then triggers the WHEA error. In those cases, updating or rolling back the driver fixes the problem even though it technically manifested as a hardware error. The error needs diagnosis to distinguish a hardware fault from other causes.
Can a Windows update cause the WHEA_UNCORRECTABLE_ERROR?
Indirectly, yes. Windows updates sometimes include new drivers that don't play well with certain hardware. If the error started immediately after a Windows update, try rolling back the update through Settings > Windows Update > Update History > Uninstall Updates.
Should I replace my hard drive if I keep getting WHEA errors?
If diagnostics confirm the drive is failing (bad SMART data, bad sectors, CrystalDiskInfo showing "Caution" or "Bad"), then yes, replace it. But replace it after you've secured your data, not before. If the drive still works well enough to copy files, back up everything first. If it's too far gone for that, contact a professional data recovery service before swapping the drive.
Does the WHEA error mean my SSD is dying?
It can, but not always. SSDs trigger WHEA errors when their internal error correction can't keep up with the number of failing NAND cells. Check your SSD's health using the manufacturer's tool (Samsung Magician, WD Dashboard, Intel Memory and Storage Tool, etc.) or CrystalDiskInfo. If the drive shows high wear levels, low remaining life percentage, or uncorrectable error counts, it's time to back up and plan a replacement. SSDs tend to fail more abruptly than hard drives, so don't put it off.
Can I fix WHEA_UNCORRECTABLE_ERROR without reinstalling Windows?
Since the error is hardware-related, reinstalling Windows won't fix the root cause. A fresh Windows install on a failing hard drive will still produce WHEA errors. Focus on the hardware: check temperatures, test RAM, update drivers, and evaluate your storage drive's health. The only time a reinstall might help is if corrupted system files or driver conflicts are the trigger, and even then, SFC and DISM should handle that without a full reinstall.
WHEA Uncorrectable Error: When To Protect The Data First
A WHEA uncorrectable error is Windows reporting a serious hardware fault. WHEA stands for Windows Hardware Error Architecture, and the blue screen usually appears when the processor, memory, motherboard, storage device, power delivery, or a connected PCIe device reports an error Windows cannot recover from. It is not a normal software crash, and treating it like one can put data at risk.
The key question is whether the error is connected to the storage device. If the computer blue screens while copying files, opening large folders, booting from a specific SSD, or waking from sleep, the drive may be dropping commands or returning bad data. NVMe SSD problems are especially important because they can fail intermittently before disappearing entirely from BIOS. Hard drives can also trigger system instability when they hang the storage bus or return unreadable sectors during boot.
Do not start with repeated resets, Windows reinstall attempts, aggressive driver cleaners, or stress tests if the only copy of important files is on that machine. Those steps may be fine for a gaming PC with backups, but they are not data safe on a suspect drive. Stress testing can heat failing components, and reinstalling Windows can overwrite user data or trigger SSD cleanup behavior.
A safer order is simple. First, decide whether the data is already backed up and verified. If it is not, stop troubleshooting from the same drive. If the system still boots, copy the most important files first, not the easiest ones. If copying causes freezing, clicking, disconnects, or another WHEA blue screen, stop and do not keep retrying. If the drive is removable, leave it powered off until it can be imaged properly.
After the data is protected, hardware troubleshooting can proceed more freely: memory testing, BIOS updates, temperature checks, power supply checks, driver review, and component swaps. But if the storage device is part of the failure, recovery comes before repair. Our SSD data recovery and hard drive recovery workflows focus on imaging unstable media before Windows or diagnostic utilities cause more damage.
Can WHEA uncorrectable error be caused by a failing SSD?
Yes. A failing SATA or NVMe SSD can trigger WHEA blue screens when it stops responding, returns controller errors, overheats, or drops from the PCIe bus. If the crashes happen during boot, file copies, updates, or heavy disk activity, protect the data before running stress tests or reinstalling Windows.
Should I reinstall Windows to fix WHEA uncorrectable error?
Only after the data is backed up or recovered. Reinstalling Windows can overwrite files, change partitions, and increase writes to a drive that may already be unstable. WHEA is often hardware related, so a reinstall may not fix the root cause anyway. Secure the files first, then troubleshoot the hardware.
How MDrepairs can help
Real cases like this come through our New Jersey lab every week. If you are dealing with one now, start here.
