What WHEA_UNCORRECTABLE_ERROR means
The Windows Hardware Error Architecture collects error reports from hardware. This stop means a hardware error was reported that the system could not correct. The CPU, memory, PCIe devices, storage, overclocking and power or cooling problems can all report through it, so the code does not itself say which part is at fault.
Common causes
- An unstable CPU, memory or GPU overclock or undervolt
- Overheating or inadequate power delivery
- A failing CPU, RAM, storage device or PCIe card
- Outdated BIOS or chipset firmware
How to fix WHEA_UNCORRECTABLE_ERROR
Work through these in order and test after each one. Stopping as soon as the crashes stop tells you which change mattered.
- Look for WHEA events in Event Viewer. Open Event Viewer, Windows Logs, System, and look for events from WHEA-Logger around the time of the crash. They often indicate the type of component that reported the error, which narrows the search.
- Return the PC to stock settings. Reset the BIOS to defaults, then leave XMP or EXPO, CPU or GPU overclocks and undervolts (including per-core offsets such as Curve Optimizer) switched off while you test. If the crashes stop, re-enable one setting at a time to find the unstable one.
- Watch temperatures under load. Use a monitoring tool to log CPU, GPU and drive temperatures while you reproduce the problem. Sustained high readings, loud fans or thermal throttling point to dust, failed fans or poor airflow rather than a software fault.
- Test the memory. Run Windows Memory Diagnostic (search for it in Start) for a quick check, then MemTest86 for several passes if the crashes continue. Any error points to a faulty stick or slot, or to memory settings the hardware cannot run reliably.
- Update firmware and remove extras. Install the latest BIOS and chipset drivers from the motherboard or laptop maker, and remove any non-essential PCIe cards to see whether the crashes stop.
If errors persist at stock settings with good temperatures, a hardware component is failing. Isolate it by swapping RAM, GPU or drive with known-good parts.
Not sure this is your code?
The stop code appears as text on the blue screen. If the PC restarted before you could read it, open Event Viewer, then Windows Logs, then System, and look for a BugCheck event with ID 1001. You can also search all stop codes.
Related guides
Other hardware and cpu errors
- CLOCK_WATCHDOG_TIMEOUT (0x101)
- UNEXPECTED_KERNEL_MODE_TRAP (0x7F)
