whea_uncorrectable_error
A whea_uncorrectable_error is a serious hardware BSOD in Windows. Read our guide to diagnose CPU, RAM, or voltage issues and restore system stability permanently.
The whea_uncorrectable_error (often accompanied by the stop code 0x00000124) is one of the most critical Blue Screen of Death (BSOD) errors a Windows user can encounter. WHEA stands for Windows Hardware Error Architecture. When you see this error, Windows has detected a fatal hardware issue that it cannot bypass, ignore, or correct via software. To protect your data from corruption and your hardware from further physical damage, the operating system immediately halts all operations and crashes the system.
Understanding the WHEA Error
Unlike software or driver-related blue screens (like IRQL_NOT_LESS_OR_EQUAL), a WHEA error is generated directly by your computer's hardware. Modern processors (CPUs) feature Machine Check Architecture (MCA), a mechanism that monitors the physical health of the silicon and the data flowing through the system bus. If the CPU detects an anomaly—such as a bit flipping incorrectly in the cache, a voltage drop, or an instruction failing to execute—it flags a Machine Check Exception (MCE). Windows interprets this MCE and triggers the whea_uncorrectable_error.
Because the error stems from the lowest hardware level, troubleshooting it requires a methodical approach, often involving BIOS tweaks, stress testing, and physical hardware inspection.
Common Causes
- Aggressive Overclocking and Undervolting: The most common cause. If a CPU or RAM is pushed to a frequency it cannot sustain, or if it is deprived of the necessary voltage to maintain stability, math errors occur in the silicon, triggering the WHEA halt.
- Failing Hardware: A dying CPU, degrading RAM sticks, or a failing motherboard VRM (Voltage Regulator Module) can cause these hardware-level faults.
- Thermal Throttling / Overheating: If the CPU cooler is improperly mounted, the thermal paste has dried out, or the pump on a liquid cooler fails, temperatures can spike instantly, causing the hardware to fault.
- Outdated BIOS: Modern processors (especially Ryzen and Intel Core architectures) rely heavily on motherboard BIOS microcode to manage voltage and stability. Outdated BIOS versions can lead to WHEA errors.
Step-by-Step Solutions
1. Reset BIOS to Default Settings
If you have tweaked your BIOS settings, restoring them to factory defaults is the first and most vital step.
- Restart your PC and repeatedly press the BIOS key (usually Delete, F2, or F12) during startup.
- Look for an option labeled Load Optimized Defaults, Reset to Default, or similar.
- Save changes and exit. This will disable any CPU overclocks and disable RAM XMP/EXPO profiles. If the system is stable afterward, you know an overclock was the culprit.
2. Update Your Motherboard BIOS
Motherboard manufacturers frequently release BIOS updates that improve system stability and memory compatibility. Identify your motherboard model, visit the manufacturer's official support page, download the latest stable BIOS version, and flash it using the built-in BIOS flashing tool (usually via a USB flash drive).
3. Monitor System Temperatures
Download a hardware monitoring tool like HWiNFO64 or HWMonitor. Run a stress test or use the PC normally and watch the CPU Package temperatures. If temperatures exceed 90-95°C under moderate loads, you have a cooling issue. You may need to clean your fans, remount your CPU cooler, and apply fresh thermal paste.
4. Test Your Memory (RAM)
Faulty RAM can trigger WHEA errors if the CPU reads corrupted data from the memory modules.
- Press the Windows key, type Windows Memory Diagnostic, and run the tool.
- For a more thorough test, download MemTest86, put it on a bootable USB drive, and run it overnight. If any errors are found, you must replace the faulty RAM stick.
5. Reseat Hardware Components
Sometimes, vibrations or moving a PC can slightly dislodge components. Turn off your PC, unplug it, and manually reseat the RAM sticks, the graphics card, and all power supply cables connecting to the motherboard (especially the 8-pin CPU power cable).
Frequently Asked Questions
Can a software or driver issue cause a whea_uncorrectable_error?
It is incredibly rare but technically possible. A severely bugged low-level driver (like a chipset driver or kernel-level anti-cheat) could theoretically command the hardware to do something impossible, but 99% of the time, WHEA is a strict hardware or BIOS configuration issue.
Is my CPU completely broken if I get this error?
Not necessarily. While a degraded CPU can cause this, it is far more likely to be an unstable overclock, bad RAM, outdated BIOS, or a power supply failing to deliver clean voltage.
Will reinstalling Windows fix a WHEA error?
Generally, no. Because the error originates at the hardware level before Windows even fully processes the data, a fresh Windows installation will likely crash with the same error if the underlying hardware fault remains.
What does stop code 0x00000124 mean?
The hex code 0x124 is the specific bug check code designated by Microsoft for the WHEA_UNCORRECTABLE_ERROR. It just serves as a technical identifier for developers and system administrators diagnosing the memory dump.
Related Articles
-
err_ssl_protocol_error
Learn how to fix the err_ssl_protocol_error in your browser. This comprehensive guide covers common causes like date/time issues, cached data, and antivirus settings.
-
err_http2_protocol_error
Encountering the err_http2_protocol_error? Discover the root causes behind this HTTP/2 connection failure and follow our detailed solutions to restore access.
-
err_quic_protocol_error
Resolve the err_quic_protocol_error quickly with our step-by-step troubleshooting guide. Fix connection issues by disabling QUIC, resetting flags, or checking extensions.
-
ssl_error_bad_cert_domain
Fix the ssl_error_bad_cert_domain warning by understanding why a website's SSL certificate domain doesn't match the URL you visited and how to bypass it safely.
-
ssl_error_no_cypher_overlap
The ssl_error_no_cypher_overlap occurs when the client and server share no common encryption ciphers. Find out how to update protocols and bypass this barrier safely.
-
ssl_error_rx_record_too_long
Struggling with ssl_error_rx_record_too_long? Learn how to fix this Firefox-specific secure connection error caused by server misconfigurations or port conflicts.
-
dxgi_error_device_removed
Fix the dxgi_error_device_removed crash. Find out why your system thinks the graphics card was physically removed and how to resolve driver and power supply issues.
-
dxgi_error_device_hung
The dxgi_error_device_hung error usually signals a GPU communication timeout. Learn how to update drivers, tweak DirectX settings, and stabilize your system.
Reviews
No approved reviews yet.