Do not hide a hardware error with more voltage
Return overclocking, undervolting, XMP/EXPO and tuning utilities to defaults before testing. Do not raise CPU, GPU or RAM voltage as a casual fix; incorrect voltage can damage components. Back up files because unstable CPU, memory or storage can corrupt data.
Use the workload to narrow the hardware path
| Crash pattern | Investigate first |
|---|---|
| CPU-heavy rendering or compilation | CPU stability, cooling, motherboard power, BIOS. |
| Gaming or GPU load | GPU, PCIe, power supply, thermals, graphics driver. |
| Memory test or mixed random codes | RAM, memory controller, XMP/EXPO. |
| File transfers or storage load | NVMe/SSD, PCIe link, controller, firmware. |
| Idle or sleep transitions | Firmware, power states, chipset, undervolting. |
1. Load stable default settings
Remove CPU and GPU overclocks, undervolting, curve optimisers and custom power limits. Disable XMP/EXPO temporarily. Use the motherboard or PC manufacturer’s documented method to load defaults, then retest the exact workload.
If defaults stop the crashes, reintroduce no tuning until the system proves stable for an extended period.
2. Read WHEA-Logger events
Open Event Viewer and inspect Windows Logs → System around the crash time for WHEA-Logger. Note whether the record mentions a processor core, cache hierarchy, memory, PCI Express root port or storage device.
One event does not always name the replaceable part, but repeated records with the same component or bus provide direction.
3. Check BIOS/UEFI and device firmware
Compare the installed BIOS version with the exact PC or motherboard support page. Read release notes for CPU microcode, memory compatibility, PCIe or stability fixes. Update only when appropriate, using reliable power and the manufacturer’s process.
Also check SSD and GPU firmware when the relevant manufacturer documents a correction.
4. Check cooling and temperatures
- Confirm CPU, GPU and case fans operate.
- Clear blocked vents and dust safely.
- Monitor temperatures during the workload that triggers the crash.
- Check that a cooler or recent hardware installation is seated according to its instructions.
Thermal spikes, throttling or crashes soon after load begins can indicate cooling or power problems.
5. Check power delivery
Use the correct laptop charger and remove questionable docks or adapters. On desktops, verify GPU power connectors and that the power supply is appropriate for the hardware. Sudden 0x124 crashes under combined CPU/GPU load can expose insufficient or unstable power.
Do not open a power supply; internal capacitors are dangerous even when unplugged.
6. Test RAM and the memory controller
Run Windows Memory Diagnostic followed by an extended supported memory test at default settings. If errors appear, isolate modules and slots only using manufacturer service guidance.
Errors that follow one module suggest the DIMM; errors tied to one slot or occurring with multiple known-good kits may involve the board, socket or CPU memory controller.
7. Test CPU stability without unsafe stress
Run the PC manufacturer’s CPU diagnostic first. Use controlled workloads while monitoring temperature and power rather than extreme stress settings. Repeated cache-hierarchy or processor-core WHEA records at defaults require CPU, motherboard, BIOS and power evaluation.
8. Isolate GPU and PCIe devices
Reseat or remove recently added PCIe hardware only if you are comfortable following anti-static and manufacturer instructions. Update stable chipset and graphics drivers. Test without non-essential capture, network or expansion cards.
A WHEA record naming a PCIe root port may identify the path, not necessarily the exact failing card; map the port using motherboard documentation.
9. Check NVMe and storage health
Use the SSD manufacturer’s diagnostic and firmware utility. Review whether WHEA records or Event Viewer errors identify the NVMe controller or PCIe path. Back up immediately when the drive disconnects, becomes read-only or reports media errors.
10. Update chipset and hardware drivers selectively
Install stable chipset, management engine, storage, graphics and network packages from Windows Update or the PC manufacturer. Roll back the specific driver that directly preceded the failures. Drivers can trigger hardware states, but repeated WHEA errors at default settings still require hardware investigation.
11. Know when professional hardware service is appropriate
Seek service when WHEA errors persist at defaults, firmware is current, temperatures are controlled and the same component path repeats. Provide the stop code, WHEA event details, workload, temperatures and diagnostics. This evidence is far more useful than simply reporting random restarts.
Avoid these common mistakes
- Do not raise voltage to suppress WHEA errors.
- Do not flash firmware for the wrong model or interrupt the update.
- Do not assume reinstalling Windows repairs unstable hardware.
- Do not replace several expensive components before isolating the failing path.
Frequently asked questions
Is WHEA_UNCORRECTABLE_ERROR always hardware failure?
It is a hardware error report, but firmware, drivers, power delivery, heat and unstable tuning can make otherwise functional hardware report errors.
Can a BIOS update fix WHEA errors?
Yes when the manufacturer documents stability or compatibility fixes, but BIOS updates carry risk and must match the exact model with reliable power.
How do I find which component caused WHEA 0x124?
Review Event Viewer WHEA-Logger records and crash dumps for processor, memory, PCIe or storage clues, then reproduce the failure with isolated component tests.
Technical steps align with Microsoft guidance for bug check 0x124 and WHEA hardware errors, plus standard manufacturer practices for firmware, memory, storage, thermal and power diagnostics.
Official references
For platform-specific behavior and recovery options, compare this guide with the current documentation from the relevant official source.