Windows & BSOD · critical

How to fix FAULTY_HARDWARE_CORRUPTED_PAGE (0x12B)

Windows & BSOD troubleshooting guide

What this error means

Windows stopped because its memory manager found memory corruption caused by hardware or a driver writing to memory directly. Microsoft says such corruption can only come from access by physical address, not through normal Windows code. Microsoft lists three causes: defective RAM, a driver or device that wrote to the wrong memory during a direct memory access (DMA) transfer, or a hardware device or firmware corrupting memory, for example across sleep or another power transition. Faulty RAM is the first thing to rule out.

Updated

Applies to
Windows 11 and Windows 10
Difficulty
Intermediate
Before changes
Low; opening a desktop needs care

Reviewed by Matyáš Rada · Documentation checked: 2026-10-31 · Checked against Microsoft's bug check documentation; not tested on every configuration.

Before you begin

Back up important files if crashes are frequent; memory corruption can also damage files that are being saved. If Windows cannot start, see the startup guide.

Work through these checks

0 of 7 complete
01Run Windows Memory Diagnostic

Defective RAM is the first cause Microsoft lists, and its remediation is Windows Memory Diagnostic.

  1. Press Win + R, type mdsched.exe and choose Restart now and check for problems.
  2. After the restart, open Event Viewer > Windows Logs > System and find the MemoryDiagnostics-Results entry.
What to expect

No memory errors are found.

If it does not help

If errors are found, go to step 3 to find the faulty module. A pass does not fully rule out RAM; a longer test such as MemTest86 is more thorough.

Browse related errors
02Turn off memory overclocks

Memory running above its default speed can corrupt data even if each module is fine.

  1. In the BIOS, turn off XMP, EXPO or DOCP, or choose Load optimized defaults.
  2. Use the PC for a few days at default settings.
What to expect

The crashes stop.

If it does not help

If they stop, update the BIOS (step 4) and try the profile again.

Browse related errors
03Test each RAM module

Testing one module at a time shows which module or slot is faulty.

  1. Switch off and unplug the PC, and leave only one RAM module installed.
  2. Run the memory test or use the PC normally, then repeat with each module and in a different slot.

Touch a metal part of the case before handling RAM.

What to expect

You find the faulty module or slot.

If it does not help

See the memory test errors guide on this site for more detail.

Browse related errors
04Update the BIOS and device firmware

Microsoft lists firmware that corrupts memory as a cause; updates fix such bugs and improve memory stability.

  1. Install the latest BIOS/UEFI from your PC or motherboard maker.
  2. Update the SSD firmware with the drive maker's tool, and other device firmware the PC maker offers (for example Thunderbolt or docking station).

Do not switch off the PC during a firmware update.

What to expect

Firmware is current and the crashes stop.

If it does not help

Check BIOS settings after the update; they may be reset.

Browse related errors
05Check whether it happens after sleep

Microsoft mentions firmware modifying memory across a power transition.

  1. Note whether crashes happen shortly after waking from sleep, hibernation or a Fast Startup boot.
  2. If so, turn off Fast Startup (Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable) and use Shut down or Restart instead of Sleep for a few days as a test.
What to expect

You know whether power transitions trigger the crash.

If it does not help

If they do, update the BIOS and chipset drivers and report the problem to the PC maker.

Browse related errors
06Update or remove device drivers

A driver or device that sets up DMA transfers incorrectly can write to the wrong memory.

  1. Install the latest chipset, storage, network, Thunderbolt/USB4 and graphics drivers from the makers.
  2. Disconnect recently added expansion cards, docks and external devices, and test without them.
What to expect

The crashes stop with updated drivers or without a device.

If it does not help

If a device is responsible, contact its maker for a fixed driver or firmware.

Browse related errors
07Replace the faulty part

Physical memory corruption keeps happening until the faulty hardware is replaced.

  1. Replace a RAM module that failed testing, ideally with a kit from your motherboard's supported memory list.
  2. If memory is soldered (many laptops), or crashes continue with new RAM, contact the PC maker for repair.
What to expect

The PC runs without this stop code.

If it does not help

Keep the BIOS and drivers updated to avoid firmware-related corruption returning.

Browse related errors

Possible causes

  • Defective RAM
  • Unstable memory overclock or XMP/EXPO profile
  • A driver or device writing to the wrong memory during DMA
  • Firmware corrupting memory around sleep, hibernation or startup
  • Outdated BIOS

Useful Windows tools

These commands open Windows tools. Review changes before applying them.

mdsched.exe
eventvwr.msc

Sources & further reading