Key takeaways
- Blaming Windows or a game. WHEA reports hardware-level faults, so reinstalling Windows seldom helps by itself.
- Changing many settings at once. You will not know which change worked.
- Ignoring corrected errors. They may foreshadow fatal ones.
- Running a Curve Optimizer undervolt that passes load tests but fails at idle. Stability needs light-load checks too.
- Skipping the BIOS update notes. Release notes often mention stability and memory compatibility changes.
An AMD WHEA error means Windows received a hardware error report from the processor, memory or a PCIe device, and the fastest fix is usually to return the system to stock settings: disable EXPO or manual memory tuning, remove Curve Optimizer or Precision Boost Overdrive undervolts, update the BIOS and chipset driver, and confirm cooling. If the error persists at stock settings, suspect failing hardware such as memory, the CPU or a PCIe device.
What a WHEA Error Is
WHEA stands for Windows Hardware Error Architecture. Microsoft documents it as the system that collects hardware error data and records it in the event log. The bug check WHEA_UNCORRECTABLE_ERROR (0x124) indicates that a fatal hardware error occurred. Microsoft’s reference says it is typically related to physical hardware failure, and lists heat, defective hardware, memory, a processor beginning to fail, or overclocking as possible causes. It adds that a driver causing it is less likely but possible.
The word AMD in the search term usually reflects that many reports come from Ryzen systems with tuned memory or undervolting, not that AMD hardware is uniquely faulty. The same error appears on Intel systems.
Two Kinds of WHEA Events
| Type | What you see | Meaning |
|---|---|---|
| Fatal (bug check 0x124) | Blue screen or sudden restart, then an event log entry | The error was uncorrectable and the system halted |
| Corrected (WHEA-Logger events) | Warnings in Event Viewer, often with no visible symptom | The hardware fixed the error itself, but it signals a marginal component or setting |
Corrected errors, which tools such as HWiNFO can count, are an early warning. A steady growth in the count under load suggests the system is operating at the edge of stability.
Common Causes on Ryzen Systems
| Symptom or pattern | Likely cause | First fix to try |
|---|---|---|
| Crashes started after enabling EXPO or a memory speed change | Memory or memory controller instability | Disable EXPO, run memory at the default speed, then step up |
| Crashes at idle or light load after a Curve Optimizer undervolt | Undervolt too aggressive for one core | Reset Curve Optimizer and Precision Boost Overdrive settings |
| Crashes only under heavy CPU load | Heat, power delivery or a CPU limit | Check temperatures, cooler mounting and case airflow |
| PCIe-related events (corrected errors about a bus device) | Gen 4 or Gen 5 link instability, a riser, or an NVMe drive | Reseat devices, set the slot to a lower PCIe generation |
| Began after a BIOS or driver change | Firmware or chipset driver mismatch | Install the board maker’s latest stable BIOS and AMD chipset driver |
| Persists with everything at defaults | Defective memory, CPU or motherboard | Test components separately and contact the maker |
Step-by-Step Fix Order
1. Read the Event Viewer Entry
Open Event Viewer, go to Windows Logs, System, and filter for the source WHEA-Logger. The entry text names the error source, such as a processor core, a PCI Express device or the memory controller. Note the details view, because it can point to a particular core or device. This tells you where to look instead of guessing.
2. Remove All Overclocks and Undervolts
Load the optimised or default settings in the BIOS. BIOS changes and overclocking can void warranties and cause instability, so use conservative values and change one thing at a time. The menu names differ between motherboard makers, so follow the board manual. After loading defaults, use the PC normally. If the errors vanish, reintroduce tuning step by step and stop at the last stable point.
3. Treat Memory Profiles Carefully
Memory profiles such as EXPO are factory overclocks. Not every CPU and board combination holds them with every kit. Many boards publish a qualified memory list, and the memory maker lists the platforms its kits support. If a profile causes errors, a lower speed or a different kit on that list is the common remedy. Avoid mixing different kits in four slots, since that raises the load on the memory controller.
4. Update Firmware and Chipset Drivers
Download the latest stable BIOS from the motherboard maker’s support page and the chipset package from AMD’s driver page. Follow the maker’s instructions for flashing, and do not interrupt the process or power off during it. Back up important data first. If a recent BIOS introduced the problem, check the maker’s release notes before rolling back, as some boards do not allow downgrades.
5. Check Cooling and Power
Confirm the cooler is seated and its fans work. Monitor CPU and VRM temperatures under load. Microsoft’s own reference names heat as a possible cause. Make sure the power supply is adequate for the system and that cables are fully seated. Never open a power supply; if you suspect it, contact the maker or a technician. Unplug the PC from the wall before touching internals.
6. Test Memory and Storage
Run the Windows Memory Diagnostic or a bootable tool such as MemTest86 for several passes. Any error is a sign of a faulty module or unstable settings. If you have more than one stick, test them one at a time in the slot the manual recommends. Check the NVMe drive’s health with the maker’s utility and update its firmware if the maker provides one.
7. Isolate PCIe Devices
If the log points to PCI Express, try the graphics card in a different slot if one is available, remove extra add-in cards, and set the slot link speed to a lower generation in the BIOS. A riser cable or a loosely seated card is a common culprit. For GPUs with a 12V-2×6 or 12VHPWR connector, follow the GPU and power supply maker’s guidance and stop using the card if you find any heat damage.
8. Run a Stress Test at Stock Settings
After the changes, run a CPU and memory stress test while watching temperature. If the machine is stable at stock but not tuned, the tuning was the cause. If it fails at stock, hardware replacement or warranty service is the next step.
When to Stop and Get Help
If the error occurs at default settings with a clean system, the cause may be a failing CPU, memory module or motherboard. Contact the maker or a qualified technician rather than continuing to run the machine, since repeated hardware errors can cause data corruption. Back up important files promptly.
Common Mistakes
- Blaming Windows or a game. WHEA reports hardware-level faults, so reinstalling Windows seldom helps by itself.
- Changing many settings at once. You will not know which change worked.
- Ignoring corrected errors. They may foreshadow fatal ones.
- Running a Curve Optimizer undervolt that passes load tests but fails at idle. Stability needs light-load checks too.
- Skipping the BIOS update notes. Release notes often mention stability and memory compatibility changes.
Frequently Asked Questions
Is a WHEA error always a dying CPU?
No. Microsoft lists heat, memory, overclocking and failing hardware as causes, and on Ryzen systems memory profiles and undervolts are frequent triggers. Rule out settings and cooling before assuming the processor is faulty.
What is WHEA Logger Event ID 17?
It is an entry recording a corrected hardware error, often tied to a PCI Express device. It is a warning rather than a crash, but repeated entries suggest a marginal slot, device or setting worth investigating.
Can a Curve Optimizer undervolt cause WHEA errors?
Yes, an undervolt that is too aggressive on one core can cause instability that surfaces as WHEA errors, often at idle or light load. Resetting it to default is a quick test.
Will updating the BIOS fix WHEA errors?
Sometimes. Updates can improve memory compatibility and stability, but a BIOS update will not repair defective hardware. Read the maker’s notes and follow its flashing instructions exactly.
Should I replace my RAM if MemTest86 shows errors?
Errors at default speeds point to a faulty module, and the memory maker’s warranty may cover it. Errors only with EXPO suggest the profile is too demanding for your platform, so try a lower speed first.
Is it safe to keep gaming with WHEA warnings?
Occasional corrected warnings are less serious than crashes, but they indicate something is marginal. Back up your data and work through the fixes rather than ignoring them.
FAQ
Is a WHEA error always a dying CPU?
What is WHEA Logger Event ID 17?
Can a Curve Optimizer undervolt cause WHEA errors?
Will updating the BIOS fix WHEA errors?
Should I replace my RAM if MemTest86 shows errors?
Is it safe to keep gaming with WHEA warnings?
More from Amazon
Programs that pair well with the guide above. Offers and eligibility are set by Amazon and may change.
Free shipping on eligible items, Prime Video and more. Eligible new members can start with a free trial.
Start a Prime free trialAd-free music streaming. Eligible new subscribers can start with a free trial.
Try Music Unlimited freeA Prime membership for ages 18-24 with a trial period. Eligibility is set by Amazon.
See Prime for Young AdultsAudiobooks and podcasts to listen to on the go. Eligible new members can start with a free trial.
Try Audible freeAs an Amazon Associate we earn from qualifying purchases.