Back up important files: repeated hardware crashes can corrupt data. Photograph the blue screen and note what you were doing when it happened. If Windows cannot start, see the startup guide.
Work through these checks
0 of 7 complete01Read the WHEA record in Event Viewer
The stop code is the same for every hardware error. The record in Event Viewer says which component reported it and what kind of error it was, which decides the next step.
- Press Win + R, type eventvwr.msc and press Enter.
- Open Windows Logs > System, choose Filter Current Log and select WHEA-Logger under Event sources.
- Open the newest event with ID 18 (fatal error, the one that caused the blue screen). Note Reported by component, Error Source and Error Type.
- Also look for events with ID 17 or 19. These are corrected errors that Windows survived, and they often point to the same part.
You know the component. Processor Core with Error Source Machine Check Exception points to the CPU or its settings (Error Type: Cache Hierarchy, Internal or Bus/Interconnect). Memory Hierarchy points toward RAM. PCI Express Root Port or PCI Express Endpoint points to an expansion device or its slot.
If it does not helpFor a processor error, steps 3, 4 and 6 matter most; the separate Machine Check Exception guide on this site goes deeper. For a PCI Express error, go to step 5. If there is no event, continue in order.
02If the PC crashes at startup, reset the BIOS
When the error appears before Windows loads, a BIOS setting the hardware cannot handle is the most common reason, and you cannot reach Event Viewer anyway.
- Restart and enter the BIOS/UEFI (usually Del, F2 or F10) and choose Load Optimized Defaults, then save.
- If you cannot enter the BIOS, switch off and unplug the PC and clear the CMOS using the jumper or button described in the motherboard manual.
- Start the PC again with only the essential parts connected: one RAM module, the system drive and the graphics card.
Clear the CMOS only with the power cable unplugged.
Windows starts again.
If it does not helpIf it still crashes at startup with default settings and minimal hardware, swap the RAM module or test with a different power supply, then contact the manufacturer.
03Return all tuning to default settings
Overclocks, undervolts and memory profiles are the most common reason for WHEA errors on otherwise healthy hardware, and they can become unstable over time.
- Photograph your BIOS settings, then choose Load Optimized Defaults.
- Make sure XMP/EXPO, Precision Boost Overdrive, Curve Optimizer, manual voltages and multipliers are off.
- Also close or uninstall tuning tools in Windows, such as MSI Afterburner profiles or vendor overclocking utilities.
- Use the PC normally for a few days.
Do not raise voltages to stop the errors. Extra voltage can permanently damage the processor.
If the crashes stop, the hardware is probably fine and one setting was unstable.
If it does not helpRe-enable settings one at a time, starting with the memory profile, and keep the last stable combination. If the crashes continue at defaults, go on.
04Update the BIOS/UEFI
BIOS updates contain CPU microcode and stability fixes. Some processor families had WHEA errors that were fixed only through microcode.
- Find your motherboard or laptop model in System Information (Win + R, msinfo32, BaseBoard Product or System Model).
- Download the latest BIOS from the manufacturer's support page for that exact model and follow their instructions.
- Load default settings after the update.
Do not switch off the PC during the update. Connect a laptop to its charger.
The board runs the newest microcode and fixes.
If it does not helpWith an Intel 13th or 14th generation Core desktop processor, also read the Intel 13th/14th gen instability guide on this site.
05For PCI Express errors, check the reported device
When WHEA names a PCI Express component, the error comes from the link to an expansion device: usually the graphics card, an NVMe SSD or a riser cable.
- In the event details, find the device or bus numbers; Device Manager (View > Devices by connection) can help match them to a device.
- Shut down, unplug the PC and reseat the graphics card and its power cables, or the M.2 SSD.
- If you use a vertical-mount riser cable, connect the graphics card directly to the motherboard as a test.
- In the BIOS, set the affected slot to one PCIe generation lower (for example Gen4 instead of Gen5) as a test.
Touch a metal part of the case before handling components.
The PCI Express errors and crashes stop.
If it does not helpIf a lower PCIe generation or removing the riser fixes it, the riser or slot cannot run at full speed reliably; replace the riser or contact the motherboard maker. If the errors follow the device to another slot, the device is likely faulty.
06Check temperatures and test the memory
Overheating and faulty RAM both produce hardware errors that WHEA reports.
- Watch CPU and GPU temperatures with a monitoring tool such as HWiNFO while doing the task that usually crashes, and compare them with the manufacturers' limits.
- Clean dust from the cooler and fans and check that all fans spin.
- Run Windows Memory Diagnostic (Win + R, mdsched.exe) or MemTest86 for several passes.
Temperatures stay below the limits and the memory test finds no errors.
If it does not helpIf the memory test reports errors, follow the memory test errors guide on this site.
07Contact the manufacturer with the evidence
Hardware that keeps reporting uncorrectable errors at default settings, with current BIOS and normal temperatures, is likely faulty and may be covered by warranty.
- Collect the WHEA-Logger event details, the stop code, your BIOS version, temperatures and test results.
- Contact the maker of the part the WHEA record points to, or the PC or laptop manufacturer for a complete system.
Support can decide which part to replace without guessing.
If it does not helpUntil then, keep backups current and avoid heavy workloads that trigger the crash.
Possible causes
- Unstable overclock, undervolt or memory profile (XMP/EXPO)
- Outdated BIOS/UEFI or CPU microcode
- A PCI Express device (graphics card, NVMe SSD, riser cable) losing its connection
- Overheating processor or poor cooling
- Faulty or incompatible RAM
- Failing processor, motherboard or power supply
Useful Windows tools
These commands open Windows tools. Review changes before applying them.
eventvwr.mscmdsched.exemsinfo32Was this helpful?
Your progress is saved on this device.