MACHINE_CHECK_EXCEPTION is one of the more hardware-focused Windows blue screens. It usually means the processor detected a low-level hardware problem and Windows stopped to avoid continuing with unreliable data.
This guide applies to Windows 10 and Windows 11 PCs showing the MACHINE_CHECK_EXCEPTION stop code.
Does This Affect You?
Unlike many blue screens that start with a bad driver, this one often points toward CPU stability, overclocking, overheating, memory instability, or power delivery. It can be serious, but many cases are fixed by returning performance settings to defaults and improving cooling.
Undo CPU or RAM Overclocking
Start here if the problem began after BIOS changes, a performance preset, XMP, DOCP, or EXPO was enabled.
- Restart the PC and enter BIOS or UEFI setup. Common keys are Del, F2, and F10, but the exact key depends on the motherboard or PC maker.
- Find the overclocking section. It may be named OC, Overclocking, AI Tweaker, Extreme Tweaker, or something similar.
- Disable manual CPU overclocks and return CPU settings to Auto or default.
- Disable XMP, DOCP, EXPO, or memory performance profiles and return RAM settings to default/Auto.
- If you are unsure what changed, use Load Optimized Defaults or Load Setup Defaults.
- Save changes, restart, and use the PC normally to see whether crashes stop.
Check Cooling and Update BIOS
If the PC still crashes at stock settings, look at temperature and firmware stability next.
- Open Task Manager to check CPU usage, but use a tool such as HWMonitor or Core Temp if you need CPU temperature because Windows does not show it by default.
- Watch CPU temperatures during normal use and under load. Sustained temperatures near the mid-to-high 90s Celsius can indicate cooling trouble on many modern CPUs.
- Check fans, vents, dust buildup, and cooler mounting if you are comfortable opening the PC. Otherwise, have a repair shop clean and inspect it.
- Visit the motherboard or PC manufacturer’s support page and check for a BIOS/UEFI update that mentions CPU stability or compatibility fixes.
- Follow the manufacturer’s BIOS update instructions exactly and keep the PC powered during the update.
If the Crash Continues
Check WHEA Events
Open Event Viewer, go to Windows Logs > System, and look for WHEA-Logger events around the crash time. Those entries can identify a CPU core, cache, bus, or memory channel involved.
Test Memory One Stick at a Time
Even with this stop code, unstable RAM can be involved. If the PC has multiple memory sticks and you are comfortable working inside it, test with one stick at a time to find a bad module or slot.
Consider the CPU Only After Basics
If crashes happen at default settings, cooling is good, BIOS is current, and the failures are random, a defective CPU is possible. Contact Intel, AMD, or the PC maker before replacing parts because warranties may apply.
Rule Out the Power Supply
A weak or aging PSU can create CPU-level instability, especially after adding a power-hungry graphics card. Rule out power delivery before assuming the processor itself is bad.
Sources
- Microsoft Learn: Bug Check Code Reference
- Microsoft Support: Troubleshoot blue screen errors
- Intel Support: Understanding Machine Check Exceptions