Experiencing an abrupt Blue Screen of Death (BSOD) displaying Stop Code: FAULTY_HARDWARE_CORRUPTED_PAGE (bugcheck 0x0000012B) unexpectedly interrupts workflow in Windows 11. In the Windows NT memory architecture, the Memory Manager utilizes an internal diagnostic check called Memory Compression and Single-Bit Error Correction to ensure the integrity of virtual memory pages. Bugcheck 0x0000012B occurs when the memory manager decompresses a compressed memory page and discovers that the page has suffered physical data corruption—meaning the data retrieved from RAM differs from the checksum calculated when it was originally stored. This specific error is an explicit indicator of physical memory degradation, voltage instability across DRAM slots, or corrupted filesystem storage paging files. This guide outlines practical solutions to isolate and resolve error 0x0000012B in Windows 11.
What Causes FAULTY_HARDWARE_CORRUPTED_PAGE?
Bugcheck 0x0000012B is triggered primarily by physical memory faults and system paging corruption:
- Defective Physical RAM (Memory Sticks): Microscopic semiconductor degradation or failing capacitor cells within DRAM sticks causing bit flips.
- Unstable Memory Overclocking (XMP / DOCP / EXPO): Extreme memory profiles pushing memory bus clock frequencies or sub-timings beyond motherboard stability margins.
- Corrupted Windows Paging File (pagefile.sys): Bad sectors on the primary system solid-state drive (SSD) corrupting compressed memory chunks written to disk.
- Outdated Motherboard BIOS / UEFI Microcode: Outdated memory controller firmware failing to deliver stable voltages to DDR4 or DDR5 memory channels.
- Damaged Windows Component Store Files: Corrupted operating system libraries preventing the memory manager from executing compression routines.
Method 1: Test RAM Modules Using Windows Memory Diagnostic
Evaluating hardware RAM integrity identifies whether physical memory modules are generating data bit flips.
- Press Win + R to open the Run dialogue.
- Type
mdsched.exeand press Enter. - Select Restart now and check for problems (recommended).
- Windows will restart into the Blue Windows Memory Diagnostic tool and execute standard test passes.
- Observe the screen:
- If it states “Hardware problems were detected”, physical RAM is defective.
- Shut down the PC, unplug power, open the computer casing, and test each RAM stick individually to locate the faulty module.
Method 2: Disable XMP / DOCP / EXPO in BIOS/UEFI
Operating RAM at extreme factory overclock profiles is the primary non-defective cause of memory page corruption.
- Reboot your computer and tap Del or F2 repeatedly during startup to enter BIOS/UEFI settings.
- Navigate to the memory frequency configuration tab (often named OC, AI Tweaker, or Overclocking).
- Locate XMP (Intel), DOCP, or EXPO (AMD).
- Change the setting from Profile 1 to Disabled (running RAM at standard baseline JEDEC speeds).
- Press F10 to save changes and restart.
- Monitor your system. If blue screen crashes cease, the previous XMP profile was running with insufficient voltage or overly aggressive memory timings.
Method 3: Reset and Rebuild the Windows Paging File
Purging the virtual memory paging file eliminates corrupt memory structures cached on your storage drive.
- Press Win + R, type
sysdm.cpl, and press Enter. - Select the Advanced tab.
- Under Performance, click Settings… > click the Advanced tab > click Change… under Virtual memory.
- Uncheck Automatically manage paging file size for all drives.
- Select drive C:, choose No paging file, and click Set. Click Yes on the confirmation prompt.
- Click OK and restart your PC. Windows will boot without a paging file, purging old data.
- Upon reboot, return to Virtual Memory settings, re-check Automatically manage paging file size for all drives, and click OK. Windows will regenerate a pristine
pagefile.sys.
Method 4: Run SFC and DISM System File Repair Scans
Repairing corrupted Windows system files ensures the memory manager’s compression binaries operate without error.
- Press Win + S, type
cmd, right-click Command Prompt, and select Run as administrator. - Execute the DISM component repair tool:
DISM /Online /Cleanup-Image /RestoreHealth - Allow the scan to reach 100%.
- Execute the System File Checker scan:
sfc /scannow - Wait for confirmation: “Windows Resource Protection found corrupt files and successfully repaired them.”
- Restart Windows 11.
Method 5: Update Motherboard BIOS Firmware
Motherboard manufacturers frequently release BIOS updates that improve DDR4 and DDR5 memory compatibility and signal integrity.
- Press Win + R, type
msinfo32, and press Enter. - Check your BaseBoard Product and current BIOS Version/Date.
- Navigate to your motherboard manufacturer’s official support website (ASUS, MSI, Gigabyte, ASRock).
- Download the newest stable BIOS firmware release.
- Flash the update according to the manufacturer’s documented procedure (typically using a USB flash drive inside the BIOS interface).
FAULTY_HARDWARE_CORRUPTED_PAGE Diagnostic Matrix
| Observed Trigger | Underlying Root Cause | Primary Resolution |
|---|---|---|
| Crash occurs during intense gaming or compiling | Memory timing instability under load (XMP/EXPO) | Disable XMP in BIOS; run RAM at baseline JEDEC frequency |
| mdsched.exe reports hardware problems | Failing physical DRAM memory stick | Test RAM sticks individually; replace defective module |
| Crash occurs randomly while idle on desktop | Corrupted paging file on storage drive | Rebuild pagefile.sys via System Properties > Virtual Memory |
| Error repeats on brand-new custom PC build | RAM installed in incorrect motherboard DIMM slots | Ensure RAM is installed in primary channels (usually slots A2 and B2) |
Frequently Asked Questions
Does FAULTY_HARDWARE_CORRUPTED_PAGE always mean my RAM is broken?
Not necessarily. While the word “FAULTY_HARDWARE” specifically denotes physical data corruption, this frequently occurs due to aggressive XMP/DOCP memory overclocking profiles or an outdated BIOS running with incorrect DRAM voltage settings. Disabling XMP in the BIOS resolves the crash in over 50% of cases without purchasing new hardware.
Can a damaged solid-state drive (SSD) cause this error?
Yes. If the compressed memory manager writes memory pages to an SSD containing bad NAND flash blocks or failing controller firmware, reading the pages back into RAM will produce corrupted data, triggering bugcheck 0x0000012B.