0x0000028B Machine Check Error: Real Fix
That 0x0000028B error means a hardware fault triggered a machine check exception. Here's how to track down the culprit and stop it from crashing your system.
Yeah, the 0x0000028B error is a nasty one. It usually means your system detected an internal hardware fault and shut down to prevent data corruption. It's not a software bug — your actual hardware is crying for help.
First thing: Run the Windows Memory Diagnostic
The most common source of this error is bad RAM. Don't bother reinstalling Windows or updating drivers yet. Run the built-in memory test first.
- Press Windows Key + R, type mdsched.exe, hit Enter.
- Choose "Restart now and check for problems."
- Let it run. This takes 20-30 minutes. Go make coffee.
If it finds errors, you need new RAM. Pull all sticks but one and test each individually in slot 0. That's how you find the bad stick.
Check WHEA-Logger event 47
Open Event Viewer (eventvwr.msc). Go to Windows Logs > System. Filter by source WHEA-Logger. Look for Event ID 47. That log tells you exactly which hardware component caused the machine check.
Double-click the event. In the description, look for Error Source and Bus Type or Memory Error Type. Common culprits:
- CPU Internal Error — your processor itself. Try reseating it, check for bent pins, or update BIOS.
- Memory Error — RAM as mentioned. Run MemTest86 for a deeper scan.
- PCI Express Error — GPU or NVMe SSD. Reseat the card, try a different slot if possible.
Reset BIOS to defaults
Sometimes the BIOS applies aggressive memory timings or overclocks that the hardware can't handle. Go into BIOS (usually F2 or Del during boot) and load optimized defaults. Disable XMP/DOCP for now. Save and reboot. If the error stops, you can try enabling XMP again later, but you might need slightly looser timings.
Check for overheating
Machine check errors can happen when the CPU or VRMs overheat. Use HWMonitor to check your temps under load. If your CPU hits 95°C+ or your VRMs go past 110°C, that's your problem. Clean dust, reapply thermal paste, and check your cooler is mounted correctly.
Less common variations
- Error appears only during sleep/wake: This is often a CPU microcode issue. Update your BIOS — motherboard manufacturers release microcode patches for this.
- Error appears only with specific software: If it only crashes in a particular game or stress test like Prime95 or FurMark, that component is failing under load. Use OCCT to isolate which part fails.
- Error on AMD Ryzen 3000/5000 systems: Known issue with fTPM causing stutter and MCA errors. Disable fTPM in BIOS if you don't need it, or update to AGESA 1.2.0.7 or newer.
- Error on Intel 12th/13th gen: Check for CPU voltage instability. Raptor Lake had a known issue with high VID requests. Update BIOS and set IA AC Load Line to 1.1 mOhm if you're crashing.
Prevention
Keep your BIOS and chipset drivers current. Bad microcode can trigger false MCA errors. Don't overclock beyond what your cooling can handle. If you run a server or workstation, use ECC RAM — it catches and corrects these errors before they crash the system.
One last thing: if you've replaced the CPU, motherboard, RAM, and PSU and the error still shows, it's probably the PSU. A failing power supply can send dirty voltage that causes random hardware faults. Swap it out.
0x0000028B is your machine telling you something broke. Listen to it. Fix the hardware, not the software.
Was this solution helpful?