> ## Content Index > Fetch the complete content index at: https://techbytefix.com/llms.txt > Use this file to discover other available public pages before exploring further. # How to Fix WHEA_UNCORRECTABLE_ERROR and Stop the Crashes - URL: https://techbytefix.com/fix-whea-uncorrectable-error/ - Published: 2026-10-25T00:19:41.000Z - Updated: 2026-10-25T00:19:41.000Z - Author: Jake Whitman - Tags: Troubleshooting, Windows WHEA\_UNCORRECTABLE\_ERROR means Windows detected a hardware-level failure it could not recover from; it does not prove that one specific part has failed. The usual fixes are to remove overclocking, correct overheating, update firmware or drivers, test memory and storage, and isolate failing hardware. Back up your files first, and stop using the PC if it overheats, smells electrical, corrupts files, or crashes during light use. ## What WHEA\_UNCORRECTABLE\_ERROR usually means The blue screen normally displays this message: ```text WHEA_UNCORRECTABLE_ERROR ``` Error WHEA is the Windows Hardware Error Architecture. It collects reports from components such as the processor, memory subsystem, storage controller, PCIe devices, and motherboard firmware. The error does not prove that one specific part has failed, but repeated WHEA crashes are a hardware-stability warning rather than an ordinary application fault. A one-off crash can follow a temporary firmware problem, a bad driver, or a brief power or thermal event. Repeated crashes deserve a structured check, especially if they happen during games, compiling, video work, or other CPU- or GPU-heavy tasks. The minidump may contain a more specific stop code or hardware error record, but the absence of a useful dump does not show that the hardware is healthy. Do not begin by reinstalling Windows or deleting drivers at random. First return the machine to known-safe settings, check temperatures, and preserve your data. These steps are reversible and help distinguish an unstable configuration from a failing component. ## Should you keep using the computer? Use the PC only long enough to back up important files if it shows signs of physical danger or rapid deterioration. Shut it down and disconnect power if you notice a burning smell, smoke, unusual electrical noise, a fan that is not spinning, or temperatures that rise abnormally fast. Do not repeatedly power-cycle a machine that is overheating. Back up documents, photos, browser data, and any other irreplaceable files before stress testing. If Windows stays up long enough, copy the files to an external drive or another computer. Do not leave the affected PC as the only place where the backup exists. Stop normal use and seek hardware service promptly if you see any of these signs: - Crashes occur during light use or immediately after startup. - Files become corrupted, disappear, or fail integrity checks. - The system cannot complete a memory or disk test. - The computer freezes before Windows loads. - A recent hardware change was followed by crashes and removing it does not help. - The system shuts down from heat or repeatedly loses power. These instructions apply to supported Windows 10 and Windows 11 systems. You need an Administrator account for many repairs and a restart for firmware, driver, Safe Mode, and memory-test changes. Before changing anything, record recent hardware or software changes, note whether the crash has a pattern, and check whether the cooling fans and air intakes are blocked. Do not open a power supply or continue operating hardware with visible physical damage. ## Fix it in this order Work through the steps in order. After each meaningful change, use the computer normally long enough to see whether the same workload still causes a crash. If Windows is too unstable to complete a step, use Safe Mode. 1. Remove overclocking and return firmware settings to their defaults. Enter UEFI or BIOS setup during startup using the key shown by the manufacturer. Disable CPU, GPU, and RAM overclocking, including CPU undervolting, enhanced motherboard performance profiles, and memory profiles such as XMP or EXPO. Save the settings and restart. If you cannot identify the changed settings, use the firmware option named `Load Optimized Defaults`, `Load Setup Defaults`, or similar. Do not change unrelated boot or storage settings while doing this. A system can be unstable even when an overclock passed an earlier test. A BIOS update, warmer room, aging component, or new driver can change its margin of stability. If crashes stop at default settings, the configuration was not stable. Leave the defaults in place or reduce the performance settings rather than immediately restoring the old profile. If the crashes continue, proceed to temperature and hardware checks. 1. Check temperatures while the workload is running. Use the monitoring utility supplied by your motherboard, laptop, CPU, or GPU manufacturer, or another reputable hardware-monitoring program. Watch CPU and GPU temperatures, clock speeds, fan operation, and whether the readings rise sharply before the crash. Compare the readings with the component manufacturer's documented limits; there is no single safe temperature for every processor or graphics card. Power the computer off before cleaning it. Clear dust from vents and heatsinks with appropriate compressed air, make sure all fans spin, and confirm that a desktop's cooler is firmly mounted. A laptop should sit on a hard surface rather than fabric. If temperatures remain excessive after cleaning, stop stressing the system and have the cooling system inspected. 1. Install firmware and driver updates from the correct manufacturer. Start with the PC or motherboard manufacturer's support page for BIOS or UEFI, chipset, storage-controller, network, and system drivers. For a discrete graphics card, use the GPU manufacturer's current driver. Read the release notes and follow the vendor's update procedure; keep the computer connected to reliable power during a firmware update. For Windows Update, open the following path: ```text Settings > Windows Update > Check for updates ``` Settings path Install available updates, restart, and check again. In Device Manager, look for warning icons, but do not assume that an automatic driver search has found the best version. Avoid third-party driver-updater tools. If the crash began immediately after a driver or firmware update, use the manufacturer's documented rollback option or Windows recovery option instead of installing several unrelated versions. The expected result is a stable system after the restart; if the crashes continue, continue with memory and storage testing rather than repeatedly changing drivers. 1. Test the memory. Save your work, close applications, and run Windows Memory Diagnostic: ```text Start > type Windows Memory Diagnostic > Run as administrator > Restart now and check for problems ``` Settings path The test runs before Windows starts. Results usually appear after the next login. You can also open Event Viewer as Administrator and inspect `Windows Logs > System` for `MemoryDiagnostics-Results`. If the test reports errors, shut down the PC, disconnect power, and reseat the memory only if you are comfortable doing so. Test one module at a time and use the motherboard manual's recommended slot arrangement. Disable XMP or EXPO while testing. Any reproducible memory error is a hardware or memory-settings problem, not something to repair with Windows files; replace the failing module or have the system serviced. A clean Windows Memory Diagnostic result does not prove the RAM is perfect. Intermittent errors can require a longer bootable memory test or testing in a different system, particularly when crashes continue with default firmware settings. If the test could not complete, treat that as a reason to stop normal use and arrange service. 1. Check the system drive and Windows files. Open Command Prompt as Administrator and run the system-file checker: ```cmd sfc /scannow ``` Command Prompt (run as Administrator) Expected output is a message such as `Windows Resource Protection did not find any integrity violations` or a message saying that Windows repaired corrupted files. If SFC says it could not repair some files, run the component-store repair and then run SFC again: ```cmd DISM.exe /Online /Cleanup-Image /RestoreHealth sfc /scannow ``` Command Prompt (run as Administrator) Next, check the file system. Replace `C:` with the affected Windows volume if necessary: ```cmd chkdsk C: /scan ``` Command Prompt (run as Administrator) The expected result is a report with no file-system errors. If Windows says that repairs require an offline scan, schedule it only after backing up your data and accepting the restart. Do not interrupt a repair that is already running. Check the drive's health with the drive manufacturer's diagnostic utility or the PC manufacturer's hardware diagnostics. A warning for reallocated, pending, uncorrectable, or rapidly increasing errors points toward a failing drive. Replace it after securing the backup; do not rely on `chkdsk` to repair physically failing storage. 1. Use Safe Mode to separate Windows software from hardware instability. Open the recovery options with either method: ```text Settings > System > Recovery > Advanced startup > Restart now ``` Settings path Or hold `Shift` while selecting `Restart` from the Start menu. Then choose `Troubleshoot > Advanced options > Startup Settings > Restart`, and press `4` for Safe Mode or `5` for Safe Mode with Networking. Safe Mode loads a limited set of drivers. If the crashes stop there, remove a recently installed driver, utility, antivirus component, or hardware-control program from `Settings > Apps` or Device Manager. Restart normally after each removal and test the workload that caused the crash. If WHEA crashes continue in Safe Mode, software becomes less likely and firmware or hardware deserves more attention. Safe Mode is not proof that a component is healthy if the PC simply has not yet reached the workload that triggers the failure. 1. Use System Restore if the problem began after a recent change. Open the recovery tool from Windows Search or the recovery environment: ```text Control Panel > Recovery > Open System Restore ``` Settings path Choose a restore point created before the crashes began and review the affected programs before confirming. System Restore normally does not remove personal documents, but it can remove drivers and applications installed after the selected point. It does not repair failing hardware or restore personal files. If Windows cannot stay running, enter the recovery environment using `Shift` \+ `Restart` or repeated failed starts, then select `Troubleshoot > Advanced options > System Restore`. If no restore point exists, skip this step rather than forcing a reset. The expected result is that the recent software or configuration change is undone and the crashes stop. If WHEA continues, restore the evidence you recorded and proceed with hardware isolation. 1. Inspect recent hardware changes and isolate components. Remove newly installed RAM, PCIe cards, storage devices, or USB hardware one change at a time, using the manufacturer's shutdown and handling instructions. Reseat power and data cables in a desktop, and check that the graphics card's power connectors are fully inserted. Do not disconnect a boot drive while Windows is running. If the PC is stable with one RAM module, one storage device, or a removed expansion card, the isolated part, its slot, its cable, or its driver becomes the leading suspect. If it remains unstable at default settings with clean memory and disk results, a motherboard, CPU, power supply, or board-level fault is increasingly likely. At that point, further stress testing can cause more crashes and data loss; arrange professional diagnosis or use the manufacturer's warranty service. ## How to confirm the problem is solved After applying a fix, restart Windows and repeat the workload that previously caused the crash. Do not treat one successful boot as proof. Use the computer normally, then run the affected game, build, export, or other task for a reasonable period without deliberately pushing a system that is showing heat or electrical symptoms. Check Reliability Monitor for a readable timeline: ```text Start > type View reliability history > Open ``` Settings path Look for new Windows failures, hardware-error events, and application crashes on the dates you tested. A stable timeline with no new WHEA events is a good sign, but an application crash by itself is not proof of a hardware fault. The expected verification result is that the triggering workload completes and no new WHEA failures appear. Event Viewer provides more detail: ```text Event Viewer > Windows Logs > System ``` Settings path Filter or search for `WHEA-Logger`, `Kernel-Power`, and events near the crash time. `Kernel-Power` often means only that Windows did not shut down cleanly; it does not identify the failed part. Repeated WHEA-Logger events, especially with the same reported processor, bus, cache, memory, or PCIe information, are more useful. Save the event details before clearing logs or reinstalling Windows. Interpret the results with the tests together: - Errors stop after disabling an overclock: the prior settings were unstable. - Memory-test errors follow a module or slot: suspect the RAM, slot, or memory controller. - Disk diagnostics report worsening media errors: replace the drive. - Crashes occur only with a particular PCIe device or driver: inspect that device, its driver, and its power connection. - Crashes continue at default settings, across Safe Mode, with clean memory and storage tests: suspect the motherboard, CPU, power supply, or another hardware path. If the same WHEA failure returns after defaults, updates, clean tests, and component isolation, do not keep reinstalling Windows. Record the stop code, WHEA event details, minidump files if available, test results, and the hardware configuration for the manufacturer or repair technician. ## Conclusion Back up your files, remove all overclocking, and work through the checks in order. If WHEA crashes continue at default settings after memory, storage, temperature, Safe Mode, and component checks, stop heavy use and have the system diagnosed rather than reinstalling Windows again. ## Frequently Asked Questions ### Can a bad driver cause WHEA\_UNCORRECTABLE\_ERROR? Yes. A driver can expose or trigger a failing hardware path, particularly for graphics, storage, chipset, or PCIe devices. If repeated WHEA events remain after firmware returns to default settings, investigate the hardware and firmware as well as the driver; do not assume the driver is the only cause. ### Will reinstalling Windows fix WHEA\_UNCORRECTABLE\_ERROR? Only if damaged Windows software is the cause, which is not the most common explanation for repeated WHEA failures. Reinstalling Windows does not repair overheating, unstable memory settings, a failing drive, weak power delivery, or a defective motherboard. Use it only after backing up your files and completing the hardware checks. ### Is WHEA\_UNCORRECTABLE\_ERROR always a sign that hardware must be replaced? No. Overclocking, outdated firmware, drivers, heat, and loose connections can produce the error. Replacement becomes more likely when failures continue at default settings, diagnostics report repeatable errors, or the same WHEA hardware record returns after software and configuration fixes.