Motherboard BSOD Crash Fix: WHEA Uncorrectable Error

Dealing with a motherboards blue screen crash with whea uncorrectable error fix starts in Event Viewer, not with a screwdriver. Windows records every WHEA failure with an error source and an APIC ID that pinpoints the faulting component. Most 0x124 crashes aren't dying hardware.

They're unstable settings you can correct in BIOS.

As of 2026, the majority of these crashes trace back to overclocking, XMP/EXPO memory profiles, or voltage configurations. Actual hardware failure is far less common than people think. Microsoft documents Bug Check 0x124 as a fatal hardware error, but the label covers any machine-check exception the CPU couldn't recover from.

A BIOS change resolves most of them.

What the WHEA Uncorrectable Error Actually Tells You

A WHEA error doesn't mean your hardware is dead. It means a component reported a machine-check exception that Windows couldn't recover from.

WHEA stands for Windows Hardware Error Architecture. It's the framework Windows uses to catch hardware-level faults before they corrupt your data. When a CPU detects a machine-check exception it can't resolve, Windows throws Bug Check 0x124, also known as WHEA_UNCORRECTABLE_ERROR.

The key word is uncorrectable. Your processor tried to repair the error on its own, and when it couldn't, it shut the system down to prevent damage. That's why the blue screen appears without warning and the PC restarts immediately.

Microsoft's bug check documentation describes 0x124 as a fatal hardware error. But the cause lives in the Event Viewer details, not in the blue screen text. Every WHEA-Logger event includes fields like "Error Source" and "APIC ID".

The APIC ID maps the error to a specific CPU core. If the same core keeps appearing, suspect a CPU cache or voltage problem. If the error source reads "Memory", suspect the memory controller or RAM.

Step 1: Find the Faulting Component in Event Viewer

The Event Viewer log tells you which component caused the crash before you touch a single screw. Every WHEA crash writes an error record that names the faulting part.

Open Event Viewer by pressing Windows Key + R, typing eventvwr.msc, and hitting Enter. Navigate to Windows Logs, then System. Click "Filter Current Log" in the right pane and enter event ID 18.

The WHEA-Logger source now shows every fatal hardware error your system recorded.

Event ID 18 is the primary code for fatal hardware errors. Event ID 19 logs corrected errors that didn't crash the system. If you see both, treat the 19s as early warnings and the 18 as the actual failure.

Click the latest event, open the Details tab, and select XML View to see the full error record.

The field that matters most is APIC ID. This number identifies which logical processor reported the fault. On a 6-core, 12-thread CPU, you'll see IDs from 0 through 11.

If the same ID keeps repeating, that core is the problem.

Next, check the "Error Source" field. It will state "Processor Internal", "Memory", "PCI Express", or "Bus/Interconnect". That single line determines which troubleshooting branch you follow next.

If you need to map APIC IDs back to your processor's layout, check how many cores your processor has to read the data correctly.

Step 2: Work the Branch That Matches Your Error Source

The Error Source field splits your fix into three paths, and each path has a different culprit.

Processor Internal errors point to CPU clocks, voltage, or microcode. Clear the CMOS to reset every BIOS setting to default. If the errors stop, an overclock or memory profile was the trigger.

If they continue, check whether a BIOS update includes a newer microcode revision. You can also try a small Vcore increase, but never exceed the manufacturer's rated voltage range. If you pull the cooler during this process, reapplying thermal grease before remounting it keeps heat from becoming a secondary problem.

Memory errors mean the memory controller or RAM is unstable. Disable XMP or EXPO so the system runs at standard JEDEC speeds. If the crashes stop, the faster profile was overstressing the memory controller.

Run MemTest86 on each stick individually to confirm whether the RAM itself is defective.

PCI Express or Bus errors point to GPUs, NVMe drives, or the motherboard's PCIe slots. Update chipset drivers first, then reseat the GPU and every NVMe drive. If the error follows a specific device after reseating, that device or its slot is failing.

Idle Crashes vs. Load Crashes: Why the Difference Matters

The crash timing is a diagnostic tool most people skip. A crash under heavy load points to a different fix than a crash at idle.

Crashes under load happen when the CPU demands sudden voltage. Gaming, rendering, and stress tests create rapid power spikes. Weak VRMs, unstable clocks, or insufficient Vcore fail under that spike.

The fix typically involves raising voltage slightly, tuning Load Line Calibration, or stepping down the overclock. This is also the time to check your CPU temperature readings, because heat degrades stability well before it triggers a shutdown.

Crashes at idle or during sleep are usually power state problems. Modern CPUs drop into low-power C-states when idle. If voltage sags too low or the BIOS power management has a bug, the CPU can't wake up cleanly.

Try disabling Global C-State Control in BIOS as a quick test. You can also raise the minimum processor state in Windows power settings.

Crash timing matters for memory profiles too. If the system dies within minutes of booting, before any real load, suspect memory training or an unstable Infinity Fabric clock. This is a known pattern on AMD Ryzen systems.

Reducing FCLK or loosening memory timings usually resolves it. If you're pushing an AMD chip and want the full safety approach, our guide to overclocking Ryzen processors walks through the stable path.

Overclocking, XMP, and C-States: The Most Common WHEA Triggers

The most common WHEA trigger is an unstable overclock, and one-click memory profiles count. Manual CPU overclocks, XMP/EXPO memory profiles, and GPU clock bumps all push hardware past rated specifications.

Manual CPU overclocks fail when Vcore can't keep up with the clock speed. The CPU's cache reports a machine-check exception the moment a calculation goes wrong. Lower the clock, raise the voltage within spec, or tune the LLC setting.

Never blindly increase voltage to silence the error. Overvoltage damages silicon faster than undervolting does. Before changing anything, verify your core voltage against the manufacturer's spec sheet.

XMP and EXPO profiles are the sneakiest WHEA source because the system looks stable at the desktop. The memory controller handles the rated speed fine during light work. Under load, the timings prove too tight for the actual silicon.

Disable the profile and run at default speeds as a test. If the crashes stop, manually loosen the timings or raise SoC voltage within safe limits.

C-state transitions produce random crashes at seemingly random moments. The CPU drops to a low-power state, then fails to return to full power when a task appears. Disable C-states in BIOS for a quick experiment.

If stability returns, the motherboard's power management was the problem.

Change one setting at a time. Reboot, then stress test for at least an hour with OCCT or Prime95. If you change three things at once, you won't know which one actually fixed the crash.

Mistakes That Make WHEA Errors Worse

The fastest way to break a CPU is raising Vcore every time the system crashes. Overvoltage degrades the silicon itself, not just your settings. Intel and AMD both publish maximum safe voltages, yet some motherboard BIOS defaults exceed them when you enable "auto" voltage tuning.

Another common slip is ignoring heat. A dust-clogged cooler or dried-out thermal paste produces WHEA errors that look identical to an unstable overclock. Pull the cooler, give it a proper cleaning, and apply fresh paste before changing any voltage.

It saves hours of wasted troubleshooting.

Panic buying new parts after one crash is a third mistake. Two crashes with the same APIC ID is a pattern. One crash after a BIOS update or an XMP change is a clue.

Log the event ID, date, and error source first.

Finally, don't flash BIOS during a thunderstorm. A failed flash can brick the board entirely. If you're on desktop, an uninterruptible power supply makes BIOS updates safe.

If you're on laptop, stay plugged in and don't close the lid mid-flash.

WHEA Uncorrectable Error FAQs

Can a WHEA crash damage my hardware?

The crash itself protects the system from corrupted data. The root cause can still harm parts over time. Excessive voltage degrades the CPU, and a failing PSU damages anything it feeds.

Treat repeated crashes as a hardware warning.

Is WHEAUNCORRECTABLEERROR always a hardware fault?

No. In our research, most crashes trace to unstable overclocks, XMP profiles, or BIOS bugs. Fresh Windows installs and driver corruption can also flag machine-check exceptions.

Reset to stock settings before replacing anything.

Why does my PC crash with WHEA only during gaming?

Gaming creates sudden power spikes that expose weak Vcore or a sagging PSU. The CPU also runs at its highest sustained boost clocks. Monitor temperatures and voltages in HWiNFO during a gaming session to find the weak link.

How long should I stress test after a WHEA fix?

Run OCCT or Prime95 for one hour minimum after each change. Then use your normal daily workload for a few days. Single-pass stress tests miss intermittent faults that only surface during real usage.

When to Stop Troubleshooting and Replace Hardware

There is a clear point where software stops being the problem. If your system crashes at stock BIOS settings, default memory speeds, and an updated chipset driver, the fault lives in one of four places: RAM, motherboard, PSU, or CPU.

Start with RAM. MemTest86 on each stick individually, one full pass, catches defective modules. Most DDR4 and DDR5 sticks carry lifetime warranties, so file a claim rather than buying a new kit.

Motherboard failures follow a pattern. Errors across random APIC IDs, boot loops, or USB dropouts point to the board. Bulging capacitors and scorched VRM areas are a visible confirmation.

CPUs rarely die. A persistent error on one APIC ID after a BIOS update and stock settings suggests a physical core fault. Both Intel and AMD cover desktop processors with three year warranties, so an RMA beats buying new.

Follow the proper procedure for swapping in a replacement chip when the time comes.

PSU problems hide behind everything. Voltage ripple under transient loads triggers WHEA errors with no consistent pattern. A multimeter or a known-good replacement unit confirms the diagnosis.

Modern power supplies carry 5 to 10 year warranties, so check yours before ordering anything.