WHEA Uncorrectable Error in Windows 11: How to Fix It

The WHEA_UNCORRECTABLE_ERROR is a Windows stop error that often points to a hardware fault, unstable settings, overheating, or a driver problem. Work through the checks below from least disruptive to most; you will need administrator access, and should back up important files before advanced repairs.

What You’ll Need

Administrator access to the PC and a little time to restart it between checks.
A backup of important files, especially before changing firmware settings or running disk repairs.
If the PC cannot start normally, access to Windows Recovery Environment (Windows RE). A second device can help you look up your PC or component maker’s instructions.

Step-by-Step

Note when the error occurs. Write down the stop code and any displayed “What failed” filename. Note whether it started after a Windows update, driver installation, new hardware, a drop, or a change to BIOS/UEFI settings. This information can help distinguish a software trigger from a hardware problem.
Undo recent hardware or performance changes. Shut down and disconnect power before removing an external device; then test with nonessential USB devices, docks, and accessories disconnected. If you recently installed a component, reseat it only if you are comfortable doing so and the computer’s service instructions permit it. Remove overclocking or undervolting and restore firmware defaults using the device maker’s instructions. Do not open a laptop or power supply unless qualified.
Check temperatures, ventilation, and power. Make sure vents are clear and fans can turn freely; use the PC on a firm surface. If the error happens during demanding work, stop and let the machine cool. A failing or unsuitable power supply, loose internal connection, or overheating can cause hardware errors; do not keep stress-testing a PC that repeatedly crashes or smells hot.
Install Windows and device updates. If Windows stays up, open Settings > Windows Update, select Check for updates, install applicable updates, and restart. For graphics, storage, chipset, or other device drivers, use Windows Update’s optional driver updates or the computer/component manufacturer’s support page for the exact model. Avoid third-party driver-updater utilities.
Check Windows system files. Right-click Start, open Terminal (Admin) or Windows PowerShell (Admin), and approve the prompt. Run DISM.exe /Online /Cleanup-Image /RestoreHealth and wait for it to finish. Then run sfc /scannow. These commands repair or report Windows component and system-file issues; they cannot repair defective hardware. Restart when both commands are done.
Check the drive. Back up files first. Open Terminal (Admin) and run chkdsk C: /scan to check the Windows volume online. If it reports errors that need an offline repair, follow its instructions; a repair may require a restart. Check drive health with a diagnostic tool supplied for your PC or drive, if available. Back up immediately if you hear unusual drive noises or see repeated disk errors, and avoid repeated repair attempts on a drive that may be failing.
Test memory and review crash clues. Search Start for Windows Memory Diagnostic, open it, and choose to restart and check. Save your work first. If it reports errors, or the blue screen continues, arrange a memory test or service through the PC maker; results may not identify every intermittent fault. You can also review Event Viewer > Windows Logs > System around the crash time, but a logged hardware event is a clue, not a diagnosis.
Use Safe Mode or Windows RE if Windows will not stay open. If you can reach the sign-in screen, hold Shift while selecting Power > Restart. Alternatively, let startup fail several times to enter recovery. Choose Troubleshoot > Advanced options > Startup Settings > Restart, then select Safe Mode. From there, remove a recently added driver or app, or use System Restore if a suitable restore point exists. Menu availability can vary. If device encryption or BitLocker is enabled, recovery may request its key; locate it before proceeding.
Escalate persistent crashes. If the error remains after updates, file checks, and removing recent changes—or appears before Windows loads—contact the PC or component maker or a qualified repair service. Provide the stop code, crash timing, recent changes, and any diagnostic results. Reinstalling Windows should be a last resort, not the first response to a likely hardware fault.

Common Mistakes

Assuming every WHEA error is a Windows bug. The message means Windows received a serious hardware-error report; the source still needs investigation.
Updating or flashing BIOS/UEFI firmware as a first step. Firmware changes carry risk. Use only instructions and files for the exact model, keep reliable power connected, and do not interrupt an update.
Changing several settings at once. Make one change, restart, and see whether the error returns so you can identify what helped.
Running disk repairs repeatedly without a backup, or continuing to use a drive that is showing signs of failure.
Using “registry cleaners,” unofficial driver tools, or random driver downloads. These can create new instability and make the cause harder to find.

Tips

Keep a record of the date, activity, recent updates, and whether the PC was hot when each crash happened.
Change only one variable at a time and restart after a driver, settings, or hardware change.
Keep a current backup. If the PC is stable only in Safe Mode, use that opportunity to copy essential files before further troubleshooting.
Use manufacturer documentation for model-specific hardware checks. Stop if a repair requires tools or disassembly you are not equipped to handle.

Troubleshooting

The commands report that repairs could not be completed: Restart and run DISM again, then rerun sfc /scannow. If the commands still fail, use Windows Update or Windows recovery options, and preserve files before attempting a reset.

The error returns immediately after a driver update: In Safe Mode, open Device Manager, expand the relevant device category, right-click the device, and choose Properties > Driver > Roll Back Driver if available. Otherwise, uninstall the recent driver and install a compatible one from the manufacturer. Do not remove storage or boot-critical drivers unless you have a recovery plan.

You cannot reach Windows RE: On another device, check the computer maker’s recovery instructions. Windows installation media can provide recovery tools, but use the correct Windows edition and avoid choosing an install or reset option until files are backed up. A BitLocker recovery key may be required.

The crash continues after software checks: Treat it as a possible hardware fault. Stop repeated resets and stress tests; seek diagnostics for memory, storage, cooling, power, or the motherboard. A technician can interpret WHEA records and test components safely.

Frequently Asked Questions

What does WHEA_UNCORRECTABLE_ERROR mean?
Windows detected a serious hardware error it could not recover from. A driver or unstable configuration can contribute, but the stop code alone does not identify the failed part.

Can I fix it without reinstalling Windows?
Often, yes. Check recent changes, update compatible drivers, repair system files, and test the hardware first. Reinstalling Windows will not fix a defective component.

Is it safe to keep using the PC?
If it crashes repeatedly, overheats, or shows signs of drive failure, stop using it for demanding tasks and back up important data if you can do so safely. Arrange a diagnosis rather than ignoring the error.

Should I update BIOS/UEFI?
Only when the exact PC or motherboard maker recommends an update relevant to your issue, and you can follow its instructions. A failed firmware update can make a PC unusable.

What if the error started after adding RAM or another component?
Power down and undo the change if you can safely follow the manufacturer’s service instructions. Test the PC in its prior configuration; if the error remains, seek hardware diagnosis.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →