How to Read WHEA-Logger Errors in Windows
WHEA stands for Windows Hardware Error Architecture.
When Windows detects certain hardware-level errors, it may create a WHEA event in Event Viewer.
Where to Find WHEA Events
Open:
Event Viewer → Windows Logs → System
Filter or search for:
WHEA-Logger
Corrected vs Fatal Errors
Some WHEA events describe corrected hardware errors.
This means the hardware or platform detected a problem but recovered from it.
A corrected error is not automatically a catastrophic failure, but repeated events deserve investigation.
Common Components
WHEA errors may reference:
- CPU cores
- memory
- PCI Express
- graphics hardware
- NVMe storage
- motherboard links
PCI Express Errors
A PCIe-related WHEA event may point to a root port or connected device.
Possible causes can include:
- GPU
- NVMe SSD
- Wi-Fi card
- PCIe power management
- motherboard firmware
- unstable hardware
The bus/device/function information can help identify the path involved.
CPU WHEA Errors
Processor-related WHEA events may occur because of:
- unstable overclocking
- aggressive undervolting
- RAM instability
- power delivery
- firmware issues
- hardware failure
Do Not Ignore Patterns
One corrected error months apart may be less concerning than hundreds every day.
Look at:
- frequency
- timing
- workload
- accompanying crashes
References
Questions about How to Read WHEA-Logger Errors in Windows
Does a corrected WHEA-Logger event mean a component has failed?
Not necessarily. A corrected error means the platform recovered from a reported hardware error. Repeated events or crashes warrant investigation, but one event alone does not identify a failed part.
Does a PCI Express Root Port event prove the GPU is broken?
No. A root port may have several connected devices or links. Use bus, device and function details and the actual hardware path before narrowing the investigation.
What details should I keep for support?
Save the event ID and full message, frequency, timestamps, workload and accompanying symptoms. Those patterns are more useful than the red error icon alone.