Interactive Troubleshooter

Published: Sep 6, 2026

WHEA_UNCORRECTABLE_ERROR: Hardware Diagnostic Guide

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

An interactive root-cause diagnostic tree to isolate and resolve the WHEA_UNCORRECTABLE_ERROR (Stop code 0x00000124) blue screen. Troubleshoot CPU core voltage drops, thermal throttling, unstable XMP/EXPO memory profiles, PCIe bus faults, and BIOS microcode issues.

Full Diagnostic Tree & Step-by-Step Overview

Under what specific system load, hardware state, or crash condition does the WHEA_UNCORRECTABLE_ERROR (0x00000124) occur?

Crash occurs under heavy CPU processing load, stress testing, or when running custom CPU overclocks/undervolts.
Crash occurs during high disk I/O, NVMe SSD file transfers, or GPU-intensive rendering over PCIe lanes.
Crash occurs under heavy RAM load, gaming, or when XMP / EXPO memory profiles are enabled in BIOS.
Crash occurs randomly while idle, during light desktop browsing, or after system low-power sleep transitions.

Which CPU voltage, clock frequency, or thermal threshold matches your system's current state?

CPU is running custom frequency overclocks, Vcore offset undervolting, or modified Load-Line Calibration (LLC).
CPU core or motherboard VRM temperatures exceed 90°C–95°C immediately before the system crashes.
CPU is running completely stock settings, but microcode stability issues or Vmin voltage shift affects the processor.

Reset CPU Overclocking, Curve Optimizer, and Adjust Load-Line Calibration (LLC)

Solution:

Root Cause: Insufficient CPU Core Voltage (Vcore) Under Transient Load

The WHEA_UNCORRECTABLE_ERROR (BugCheck code 0x00000124) is triggered directly by the Windows Hardware Error Architecture when the central processor's Machine Check Architecture (MCA) reports an uncorrectable hardware error. When running custom overclocks, negative Curve Optimizer offsets (AMD PBO), or aggressive Vcore undervolting, the voltage supplied to execution cores drops below the minimum required threshold during sudden load transitions, causing bit flips in the L1/L2/L3 cache or execution pipeline.

Step-by-Step Fix:

1Boot into System UEFI/BIOS:

Restart your PC and tap Del or F2 repeatedly during POST to open BIOS.

2Revert CPU Clocks and Voltages to Factory Defaults:

Navigate to Save & Exit and select Load Optimized Defaults (or press F9/F5 depending on motherboard vendor).

If running Precision Boost Overdrive (PBO), set PBO to Auto or Disabled and clear all negative Curve Optimizer magnitude offsets.

3Tune Load-Line Calibration (LLC):

If running manual fixed voltage, navigate to Digi+ VRM / Voltage Configuration.

Adjust Load-Line Calibration (LLC) to a medium preset (e.g., Level 3 or Level 4 on ASUS/MSI) to prevent Vdroop voltage drops under full processing load.

4Save and Test Stability:

Press F10 to save BIOS settings and restart into Windows. Run a stress test tool like OCCT or Prime95 for 30 minutes to verify stability.

Inspect Thermal Interface Material, CPU Cooling Hardware, and VRM Airflow

Solution:

Root Cause: Critical CPU Thermal Throttling and VRM Thermal Degradation

When CPU core junction temperature ($T_j\text{max}$) exceeds safety limits (typically 100°C for Intel and 95°C for AMD), the processor throttles clock speeds and voltages dynamically to prevent silicon melting. If heat dissipation is insufficient—due to pump failure in All-In-One (AIO) liquid coolers, dried thermal paste, or inadequate motherboard VRM cooling—transient thermal spikes cause internal gate logic timing failures, generating an uncorrectable MCA hardware trap.

Step-by-Step Fix:

1Monitor Temperatures in Real Time:

Download and launch HWInfo64 (Sensors-only mode).

Observe CPU Core Temperatures, CPU Package Temp, and VRM MOS Temp during idling and light work.

2Verify Cooler Pump and Fan Operation:

Check BIOS hardware monitor to ensure the AIO pump RPM is reading above 2000 RPM (if using liquid cooling).

Ensure CPU fan headers are securely connected to CPU_FAN or AIO_PUMP motherboard headers.

3Repaste CPU Thermal Interface Material (TIM):

Power off PC, unplug power cord, and remove the CPU cooler block.

Clean old thermal paste off the CPU IHS and cooler cold plate using 99% isopropyl alcohol and a lint-free cloth.

Apply a pea-sized grain of high-performance thermal paste to the center of the CPU IHS and reinstall the cooler evenly using a cross-pattern screw tightening method.

4Clear Airflow Obstructions:

Ensure intake and exhaust fans are spinning freely and dust filters are clean.

Update Motherboard BIOS Microcode and Enforce Intel/AMD Baseline Power Profiles

Solution:

Root Cause: CPU Microcode Voltage Algorithm Flaw (Vmin Shift)

Certain desktop processor architectures (such as Intel 13th and 14th Gen Core processors) experience microcode algorithm defects that request elevated Vcore voltage targets from motherboard VRMs. Over time, these incorrect voltage requests cause high operating voltage exposure, Vmin degradation, and bus stability failure. Detailed hardware error reporting parameters are documented in the Microsoft Official Bug Check Reference.

Step-by-Step Fix:

1Obtain the Latest BIOS Version for Your Motherboard:

Visit your motherboard manufacturer's official support page (ASUS, MSI, Gigabyte, ASRock) and locate the latest BIOS release containing updated microcode patches.

2Flash BIOS via USB Drive / Flashback:

Format a USB flash drive to FAT32, place the downloaded .CAP or .ROM file on it, and launch EZ Flash / M-Flash within BIOS.

Complete the firmware flashing process without turning off system power.

3Apply Factory Default Power Limits:

After updating, enter BIOS and enable Intel Default Settings or AMD AGESA Default Profile.

Ensure baseline limits like PL1 / PL2 (Power Limit 1 and 2) are enforced to factory wattage standards rather than unlocked motherboard limits (4096W).

4Boot to OS and verify stability using Event Viewer to monitor WHEA-Logger entries.

Which PCIe device, NVMe drive, or bus power management behavior is present?

Crash occurs during NVMe SSD file reading/writing or lists a PCIe Root Port error in Event Viewer.
Crash occurs when high-speed PCIe Gen 4 or Gen 5 expansion cards (GPU, riser cables) are used.
NVMe M.2 Solid State Drive is physically overheating, dropping offline, or failing SMART tests.

Disable Active State Power Management (ASPM) for PCIe and NVMe Drives

Solution:

Root Cause: PCIe Active State Power Management (ASPM) Latency Failure

Active State Power Management (ASPM) reduces power consumption by placing idle PCIe links into low-power states (L0s, L1, L1 Substates). High-performance NVMe SSDs and PCIe devices sometimes fail to wake up from lower power states within the tight time window mandated by the PCIe specification. When an I/O request times out, the PCIe Root Complex logs a fatal bus error, prompting WHEA to force a bugcheck.

Step-by-Step Fix:

1Adjust Windows Power Plan Options:

Press Win + R, type powercfg.cpl, and press Enter.

Click Change plan settings next to your active power plan, then click Change advanced power settings.

Expand PCI Express > Link State Power Management.

Set both On battery and Plugged in to Off.

2Disable PCIe ASPM in BIOS:

Restart into BIOS, navigate to Advanced > PCI Subsystem Settings or Platform Power Management.

Set ASPM Support or Native PCIe ASPM to Disabled.

3Update NVMe Controller Drivers:

Open Device Manager (devmgmt.msc), expand Storage controllers, right-click your NVMe SSD controller, and update to official manufacturer drivers (e.g., Samsung NVMe driver).

Force Lower PCIe Generation Speeds (Gen 3 / Gen 4) in Motherboard BIOS

Solution:

Root Cause: Signal Degradation over PCIe Gen 4 / Gen 5 Expansion Lanes

PCIe Gen 4 and Gen 5 signaling protocols operate at extremely high frequencies (16 GT/s and 32 GT/s respectively), requiring strict trace length constraints and signal integrity. Vertical GPU riser cables, dirty motherboard slot contacts, or poor trace shielding cause electromagnetic interference (EMI) and signal loss, leading to high Bit Error Rates (BER) that exceed PCIe hardware forward error correction (FEC) limits.

Step-by-Step Fix:

1Enter Motherboard UEFI Settings:

Access BIOS during system boot (Del / F2).

2Locate PCIe Link Speed Configuration:

Navigate to Advanced > PCIe Configuration or Onboard Devices Configuration.

3Manually Downscale Slot Speed:

Change the Primary PCIe Slot (or M.2 Slot) mode from Auto / Gen 5 to Gen 4 or Gen 3.

4Clean and Reseat Hardware:

Power off PC, remove GPU / M.2 SSD from slot.

Clean gold pin contacts on the expansion card using a clean microfiber cloth moistened with 99% isopropyl alcohol.

Reseat hardware directly into the top motherboard slot (bypassing third-party riser cables if testing).

Perform NVMe Health Diagnostics and Replace Degrading Solid-State Storage

Solution:

Root Cause: NVMe Controller Fatal Error or Bad NAND Flash Blocks

When a primary NVMe SSD suffers from controller degradation or defective flash memory cells, internal drive firmware halts I/O processing to prevent data corruption. Because the operating system paging file (pagefile.sys) or core system drivers reside on this drive, sudden disk unresponsiveness generates an uncorrectable hardware exception handled by WHEA-Logger Event ID 1.

Step-by-Step Fix:

1Read SMART Diagnostic Logs via PowerShell:

Open PowerShell as Administrator and run:

powershell
     Get-PhysicalDisk | Get-StorageReliabilityCounter | Format-List

Check ReadErrorsTotal, WriteErrorsTotal, and Temperature readings.

2Run Vendor Diagnostic Tools:

Download official SSD management software (Samsung Magician, Western Digital Dashboard, or Crucial Executive).

Perform a Full Diagnostic Scan and review S.M.A.R.T. health percentages.

3Check Event Viewer for WHEA-Logger Events:

Press Win + X, open Event Viewer > Windows Logs > System.

Filter for Event Source WHEA-Logger and inspect the detailed raw hex data for device location IDs.

4Replace Failing Storage Drive:

If SMART health reports failure or critical warnings, back up data immediately and replace the NVMe SSD.

Which memory configuration, XMP/EXPO state, or RAM diagnostic result applies to your system?

Crash occurs when XMP, EXPO, or DOCP extreme memory profiles are active in BIOS.
Crash occurs randomly across stock memory frequencies, suggesting physical RAM module damage.
System uses 4 individual RAM modules across all motherboard DIMM slots on a dual-channel controller.

Disable XMP / EXPO and Adjust CPU Integrated Memory Controller (IMC) Voltage

Solution:

Root Cause: Unstable Memory Overclocking and IMC Subsystem Desynchronization

XMP (Intel Extreme Memory Profile) and EXPO (AMD Extended Profiles for Overclocking) are automated memory overclocks. Pushing high-frequency DDR4/DDR5 speeds (e.g., DDR5-6000MHz+) requires both the RAM modules and the CPU's Integrated Memory Controller (IMC) to operate in sync. If IMC voltage (VDD_IMC / CPU VDDQ / System Agent VCCSA) is slightly inadequate, parity errors occur across the memory bus, resulting in 0xC0000124 crashes.

Step-by-Step Fix:

1Disable Overclocked Memory Profiles in BIOS:

Enter BIOS setup (Del / F2).

Set XMP, EXPO, or DOCP to Disabled (Default JEDEC speeds, e.g., 4800MHz for DDR5).

2Test System at JEDEC Baseline:

Save BIOS settings (F10) and boot to Windows. Verify if WHEA crashes cease at default memory speeds.

3Incremental Voltage Tuning (Advanced Users):

If you wish to retain XMP/EXPO, re-enable the profile and locate memory controller voltages in BIOS.

On Intel, slightly increase CPU VCCSA (System Agent) or VDDQ in small increments (+0.02V to max 1.25V).

On AMD Ryzen, adjust VSOC (SoC Voltage) up to a safe maximum limit of 1.20V - 1.25V.

4Save settings and verify stability.

Isolate Faulty RAM Modules Using Windows Memory Diagnostic and MemTest86

Solution:

Root Cause: Physical Memory Cell Degradation or Damaged RAM Module

A physically degraded memory cell in a DDR4 or DDR5 RAM chip fails to hold electrical charge accurately. When system memory allocation places critical OS kernel buffers or driver code into degraded memory address ranges, hardware parity/ECC logic traps uncorrectable read/write discrepancies and initiates a WHEA blue screen shutdown.

Step-by-Step Fix:

1Execute Built-In Memory Diagnostic:

Press Win + R, type mdsched.exe, and select Restart now and check for problems.

Allow the test to complete during reboot. Review results in Windows Event Viewer under MemoryDiagnostics-Results.

2Run Deep Bootable Memory Tests:

Create a bootable USB drive using MemTest86.

Boot into MemTest86 and execute 4 passes of memory testing.

3Single Stride Isolation Testing:

If errors are detected, power off PC and remove all RAM modules.

Insert a single RAM stick into the primary DIMM slot (slot A2).

Test each stick individually until the corrupted module triggering errors is identified.

4Replace damaged RAM kit.

Reconfigure 4-DIMM RAM Topology and Reduce Memory Frequency

Solution:

Root Cause: Signal Reflection and Capacitive Load on 4-DIMM Motherboard Configurations

Consumer desktop motherboards utilize a Daisy-Chain memory trace topology optimized for 2 RAM modules. Filling all 4 DIMM slots significantly increases electrical signal reflections and capacitive load on the memory bus. Operating 4 modules at high XMP/EXPO frequencies frequently exceeds the Integrated Memory Controller's capability, causing bit corruption.

Step-by-Step Fix:

1Install RAM in Optimal Dual-Channel Slots:

If running 2 modules on a 4-slot motherboard, verify modules are installed in slots A2 and B2 (slots 2 and 4 from the CPU socket).

2Reduce Memory Frequency manually for 4-DIMM Setups:

If running 4 modules, enter BIOS with XMP/EXPO enabled.

Manually drop the Memory Frequency multiplier (e.g., drop DDR5-6000 down to DDR5-5600 or DDR5-5200).

3Increase Command Rate / Gear Mode:

Set Command Rate (CR) from 1T to 2T in memory timing settings.

For DDR5, set Gear Mode to Gear 2 (Intel) or UCLK=MEMCLK/2 (AMD).

4Save and reboot.

Which idle state, power supply, or OS driver anomaly describes your situation?

Crash occurs when the PC enters low-power sleep mode, idle states, or instantly upon waking up.
Crash occurs during sudden GPU/CPU power transient spikes, accompanied by PSU clicking or hard shutdowns.
System files, chipset INF software, or Windows power delivery drivers are corrupted.

Disable CPU Global C-States and Configure Power Supply Idle Control

Solution:

Root Cause: CPU Core Voltage Under-run During Deep C-State Sleep Transitions

To save energy, modern CPUs enter low-power sleep states (C6, C7, C8, C10) when idle, dropping core voltages down to near zero. Power supplies with poor low-amp regulation or motherboards with aging capacitors fail to maintain stable voltage rails during these ultra-low current idle transitions. When the CPU wakes up, Vcore fails to rise rapidly enough, causing a execution failure flagged by WHEA.

Step-by-Step Fix:

1Disable CPU C-States in Motherboard BIOS:

Restart PC and enter BIOS setup.

Navigate to Advanced > CPU Power Management Configuration.

Set Global C-State Control or C-States to Disabled.

2Adjust Power Supply Idle Control (AMD Systems):

In BIOS, navigate to Advanced > AMD CBS > Power Supply Idle Control.

Change value from *Auto* / *Low Current Idle* to Typical Current Idle.

3Change Windows Power Plan Settings:

In Windows, open Power Options (powercfg.cpl).

Select the High Performance power plan to prevent Windows from dropping CPU minimum power states below stable operational thresholds.

Inspect 12V EPS Cables and Replace Undersized or Degrading Power Supply (PSU)

Solution:

Root Cause: Power Supply Unit (PSU) Transient Response Failure and Voltage Rail Sag

Modern CPUs and GPUs exhibit massive transient power spikes lasting microseconds. If the Power Supply Unit (PSU) lacks sufficient wattage overhead, has degrading capacitors, or fails to satisfy ATX 3.0 transient response requirements, the +12V power rail sags. When the VRM receives insufficient input voltage, Vcore drops instantly, triggering a WHEA hardware fault.

Step-by-Step Fix:

1Inspect Internal Physical Cable Connections:

Power off PC and disconnect the main AC power cord.

Inspect the 24-pin ATX connector and all 8-pin EPS / 12VHPWR CPU power connectors on the motherboard and PSU side.

Ensure connectors are fully seated and check for signs of melted plastic or loose pin housings.

2Avoid Daisy-Chained Power Cables:

Ensure separate, independent PCIe power cables are connected to the graphics card rather than a single split daisy-chain cable.

3Verify PSU Wattage Overhead:

Ensure the PSU wattage meets or exceeds total system power requirements (e.g., minimum 850W for modern high-end GPUs/CPUs).

4Test with a Replacement Power Supply:

Swap the PSU with a known-good, high-quality 80-Plus Gold/Platinum rated power unit to verify if crashes resolve.

Reinstall Official Chipset Drivers and Repair Windows System Image

Solution:

Root Cause: Corrupted Motherboard Chipset INF Drivers and ACPI Power Drivers

Windows relies on motherboard chipset drivers (Intel Management Engine / AMD Chipset Driver) to manage low-level hardware ACPI communication, PCIe bus routing, and processor power management. Corrupted chipset drivers send invalid power state requests or interrupt requests (IRQs) directly to hardware controllers, causing execution halts that Windows interprets as uncorrectable hardware errors.

Step-by-Step Fix:

1Download Latest Chipset Drivers:

Visit the official vendor driver site (AMD.com or Intel.com) and download the latest chipset installer package for your specific motherboard socket.

2Clean Install Chipset Package:

Run the downloaded installer and choose Clean Install or allow it to overwrite existing driver stacks.

3Repair Windows System Files via Command Prompt:

Click Start, type cmd, right-click Command Prompt, and select Run as administrator.

Execute the following commands in order:

cmd
     sfc /scannow
     dism /online /cleanup-image /restorehealth

4Restart Computer and verify system operational status.

Related Diagnostic Guides

Windows Update Error 0x80070002 Missing Files Diagnostic Guide

System Restore Failed 0x80070005 Antivirus Conflict Tree

Windows Photo Viewer Not Showing Thumbnails: Codec Diagnostic

Safe Mode Password Not Working With Microsoft Account Fix

Clipboard History Not Working Windows 11: Sync Service Tree

Subscribe to StepDiag

Embed Guide on Your Website