BSOD 299 (FAULTY_HARDWARE_CORRUPTED_PAGE): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: Windows found a corrupted physical memory page and attributes it to hardware corruption.

Could be also:
Constant	Type	OS
ERROR_PARTIAL_COPY	Win32 error	Windows
STATUS_FILE_LOCKED_WITH_WRITERS	NTSTATUS	Windows

Previous	Next
MUI_NO_VALID_SYSTEM_LANGUAGE	EXFAT_FILE_SYSTEM

FAULTY_HARDWARE_CORRUPTED_PAGE

Corrupted physical page

FAULTY_HARDWARE_CORRUPTED_PAGE is bug check code 0x0000012B. The built-in table identifies it as FAULTY_HARDWARE_CORRUPTED_PAGE; the useful diagnostic question is what Windows component raised the stop and which invariant failed.

This bug check is raised when Windows detects a physical page whose contents are corrupt in a way that points toward hardware or low-level memory corruption rather than a normal page fault.

How to read the parameters

The exact arguments identify the page frame and corruption context in the debugger output.
The important distinction is physical-page corruption, not virtual address access rights.
The source may still be a driver using DMA incorrectly, not only defective DRAM.

What to check in the dump

Run memory diagnostics, check ECC/WHEA logs, and inspect recent machine-check or PCIe errors.
Check DMA-capable drivers and devices, especially storage, network, and GPU devices.
If crashes are repeatable under load, capture temperature, firmware version, memory configuration, and whether memory overclocking or XMP/EXPO is enabled.

References

Looking for a different code? Search another status or error code.