How to Fix 0x0000012B FAULTY_HARDWARE_CORRUPTED_PAGE Blue Screen Error in Windows

Quick Answer

The 0x0000012B FAULTY_HARDWARE_CORRUPTED_PAGE is a Windows Blue Screen of Death (BSOD) error indicating that the Windows memory manager detected corruption in physical memory. This corruption can result from defective RAM, a device driver or hardware component incorrectly accessing physical memory through Direct Memory Access (DMA), or firmware that modifies memory incorrectly.

The first recommended diagnostic step is to run Windows Memory Diagnostic to check for memory-related errors. If the memory test does not identify a problem, investigate recently installed hardware, device drivers, BIOS/UEFI firmware and memory configuration settings.

Importantly, this stop code does not automatically prove that a RAM module is defective. The underlying cause must be established through appropriate hardware and software diagnostics before replacing components.

What Is FAULTY_HARDWARE_CORRUPTED_PAGE (0x0000012B)?

FAULTY_HARDWARE_CORRUPTED_PAGE is a Windows bug check, commonly called a stop code or Blue Screen of Death error. Its hexadecimal bug check value is 0x0000012B.

Windows uses physical memory (RAM) to store operating system data, application information, kernel structures and other information required while the computer is running.

The Windows memory manager monitors and manages memory pages. A memory page is a fixed-size block of virtual memory mapped to physical memory. When Windows detects certain types of corruption in physical memory, it may stop the operating system to prevent further damage or unreliable operation.

Microsoft documents this bug check as a memory corruption condition caused by a component accessing memory through physical addressing.

The error can occur in Windows 10 and Windows 11 environments, although the precise hardware, driver and firmware circumstances depend on the computer.

Common Symptoms of Error 0x0000012B

When this bug check occurs, the computer may display a blue screen containing information similar to the following:

:( Your device ran into a problem and needs to restart.

Stop code: FAULTY_HARDWARE_CORRUPTED_PAGE

0x0000012B

Depending on the circumstances, users may experience the following symptoms:

• The computer suddenly displays a Blue Screen of Death and restarts.
• Windows crashes during normal operation or while running demanding applications.
• The system becomes unstable after installing new hardware.
• Blue screen errors occur during gaming, video editing or other memory-intensive activities.
• The computer crashes after changing RAM speed, memory timings or firmware settings.
• Unexpected restarts occur without an obvious application-related cause.
• Repeated BSOD events appear in Windows Reliability Monitor or Event Viewer.

These symptoms are not exclusive to error 0x0000012B. The actual stop code and crash dump should be examined before associating a system failure with this particular bug check.

What Causes FAULTY_HARDWARE_CORRUPTED_PAGE?

According to Microsoft's bug check documentation, this error occurs when physical memory corruption is detected. Microsoft identifies three important categories of causes.

1. Defective RAM (Physical Memory)

Faulty Random Access Memory (RAM) is one of the documented causes of this bug check.

RAM stores the data and instructions that the processor and operating system need during operation. If a memory module or its associated memory subsystem produces incorrect data, Windows may detect corruption and trigger a bug check.

Potential memory-related problems include:

• Defective RAM modules.
• Intermittent memory errors.
• Unstable memory operation at configured speeds or timings.
• Problems with memory slots or motherboard memory circuits.
• Memory instability associated with overclocking or aggressive memory profiles.

A failed memory diagnostic test is important evidence of a memory problem. However, a successful test does not completely rule out intermittent hardware faults.

2. Faulty Device Drivers or Incorrect DMA Operations

Direct Memory Access (DMA) allows certain hardware devices to transfer data directly to or from system memory without requiring the processor to manage every individual transfer.

Device drivers coordinate these operations. A driver or device that incorrectly accesses or modifies physical memory can corrupt memory pages and cause Windows to report this bug check.

Hardware and drivers that may deserve investigation include:

• Graphics cards and their drivers.
• Storage controllers and NVMe devices.
• Network adapters.
• High-speed expansion cards.
• Other PCI Express devices that perform DMA operations.

These devices are investigation targets, not confirmed causes. The stop code alone does not identify which device or driver is responsible.

3. BIOS, UEFI or Firmware Problems

Firmware controls important hardware initialization and low-level system operations. Certain firmware defects can cause physical memory corruption.

Microsoft specifically documents situations where hardware or firmware incorrectly modifies physical memory, including firmware that illegally modifies physical pages across a power transition.

Investigate firmware-related problems when:

• The crashes started after a BIOS or UEFI update.
• The computer experiences crashes after sleep, hibernation or resume.
• Memory settings were recently changed.
• The motherboard manufacturer has released a relevant firmware stability update.
• The system uses unsupported or unstable memory configurations.

Do not assume that updating the BIOS will resolve every 0x12B error. Firmware updates should be performed only when relevant to the suspected problem and with the manufacturer's instructions.

How to Troubleshoot FAULTY_HARDWARE_CORRUPTED_PAGE (0x0000012B)

Follow the troubleshooting procedures below in order. Start with non-destructive diagnostic checks before changing hardware or firmware settings.

Step 1: Record the Blue Screen Error Details

Before changing anything, record the error information displayed on the blue screen.

1. Note the complete stop code: FAULTY_HARDWARE_CORRUPTED_PAGE.
2. Record the bug check value: 0x0000012B.
3. Note any additional error information displayed on the screen.
4. Record when the crash occurs, such as during startup, gaming, normal operation or after waking from sleep.
5. Identify any recently installed hardware, drivers or firmware updates.

This information helps establish whether the problem is associated with a recent configuration change or an intermittent hardware failure.

If Windows creates a crash dump, preserve it for further investigation.

Step 2: Run Windows Memory Diagnostic

Windows Memory Diagnostic is Microsoft's recommended initial investigation for determining whether defective RAM hardware may be responsible for this bug check.

The utility checks system memory for errors and runs outside the normal Windows operating environment during the diagnostic restart.

Procedure:

1. Save all open files and close running applications.
2. Press Windows + R to open the Run dialog box.
3. Type mdsched.exe and press Enter.
4. Select Restart now and check for problems (recommended).
5. Allow the computer to restart and complete the memory test.
6. Wait for Windows to restart and return to the desktop.

Important: Save your work before starting the test because the computer will restart automatically.

Step 3: Check Windows Memory Diagnostic Results

Sometimes the diagnostic results are not displayed clearly after Windows restarts. You can check the recorded results in Event Viewer.

1. Press Windows + R.
2. Type eventvwr.msc and press Enter.
3. Expand Windows Logs.
4. Select System.
5. Look for an event with the source MemoryDiagnostics-Results.
6. Open the event and review its details.

The results help determine whether Windows Memory Diagnostic detected memory problems.

Interpreting the results:

• Memory errors detected: Investigate the RAM modules, memory slots and motherboard memory subsystem. Do not rely on software repairs to correct defective physical memory.
• No memory errors detected: Continue investigating drivers, DMA-capable devices, firmware and memory configuration. A passed test does not guarantee that RAM is fault-free.
• No diagnostic result found: Confirm that the memory test actually completed and inspect the System log again. The absence of a result is not proof that the memory is healthy.

Step 4: Check RAM Modules and Memory Slots

If the memory diagnostic detects errors or the computer continues to crash, inspect the installed memory hardware.

Before handling RAM:

• Shut down Windows completely.
• Disconnect the power supply from the computer.
• For laptops, follow the manufacturer's service instructions and disconnect the internal battery where required.
• Use appropriate electrostatic discharge (ESD) precautions.
• Do not open a device if doing so could create a safety risk or violate warranty conditions.

Inspection procedure:

1. Check whether the RAM modules are correctly seated in their slots.
2. Look for visible damage, contamination or signs of overheating.
3. Check the motherboard manual for the recommended memory-slot arrangement.
4. If multiple removable RAM modules are installed, test them individually where the motherboard manufacturer's instructions permit.
5. If possible, test a suspected module in another known-good compatible slot.
6. Record which module and slot combinations produce errors.

Understanding the results:

• If one module repeatedly produces errors across compatible slots, that module may be defective.
• If multiple known-good modules fail in the same slot, the motherboard or memory channel may require investigation.
• If errors occur only when a particular memory profile is enabled, investigate memory speed, timings and voltage compatibility.

Testing should follow the motherboard manufacturer's recommended procedure. Avoid removing or installing memory while the computer is powered on.

Step 5: Disable Memory Overclocking and XMP or EXPO Profiles for Testing

Memory modules may operate using standard memory settings or optional performance profiles.

Depending on the platform, these settings may be identified as:

• Intel Extreme Memory Profile (XMP).
• AMD Extended Profiles for Overclocking (EXPO).
• Other motherboard-specific memory performance or overclocking settings.

These profiles can configure memory speeds and timings beyond the platform's default memory operating settings. A configuration that is unstable with a particular CPU, motherboard and memory combination may contribute to memory errors.

Procedure:

1. Restart the computer and enter BIOS/UEFI setup using the manufacturer's designated key.
2. Locate the memory configuration or overclocking section.
3. Record the existing memory settings.
4. Temporarily disable XMP, EXPO or other manual memory overclocking settings.
5. Save the changes and restart Windows.
6. Observe whether the system remains stable under the same workload that previously caused the crash.

Important: BIOS menu names and available settings differ between manufacturers. Do not change memory voltage, timings or unrelated firmware settings without appropriate technical knowledge.

If disabling the memory profile resolves the crashes, the system may have been unstable at the selected memory configuration. This does not necessarily mean that the RAM modules are physically defective.

Step 6: Update or Roll Back Device Drivers

Because incorrect DMA operations by a driver or hardware device are among Microsoft's documented causes, investigating device drivers is important when memory testing does not identify a fault.

Start with devices that were recently installed, updated or connected before the crashes began.

To inspect installed drivers:

1. Right-click the Start button.
2. Select Device Manager.
3. Expand the relevant hardware categories.
4. Look for devices displaying warning symbols or unexpected behavior.
5. Open the properties of a suspected device.
6. Select the Driver tab to review driver information.

Consider the following driver categories during investigation:

• Graphics drivers.
• Motherboard chipset drivers.
• Storage controller drivers.
• Network adapter drivers.
• Drivers for recently installed PCIe or USB hardware.

Obtain driver updates from Windows Update or the official computer, motherboard or hardware manufacturer's support website.

If the problem started after a driver update:

1. Open Device Manager.
2. Right-click the affected device and select Properties.
3. Open the Driver tab.
4. Select Roll Back Driver if the option is available.
5. Follow the instructions and restart the computer.

Do not install unrelated drivers or use unknown third-party driver updater utilities. A driver update is useful only when it is appropriate for the exact hardware and operating system.

Step 7: Disconnect Recently Installed Hardware

A newly installed or malfunctioning hardware device may contribute to physical memory corruption through incorrect DMA operations or device-related firmware problems.

If the error started after adding hardware, perform a controlled isolation test.

1. Shut down the computer.
2. Disconnect recently added external USB devices that are not required for startup.
3. If appropriate, remove recently installed expansion cards after following safe hardware-handling procedures.
4. Restart the computer.
5. Use the system under the same conditions that previously caused the crash.
6. Reconnect devices individually to identify whether a particular device is associated with the failure.

Do not disconnect essential boot devices or remove internal hardware unless you understand the system configuration and can safely restore it.

Step 8: Check for BIOS or UEFI Firmware Updates

Outdated or defective firmware may contribute to hardware instability and physical memory corruption.

Check the motherboard or computer manufacturer's support website for firmware updates applicable to the exact model and hardware revision.

Before updating BIOS or UEFI:

• Identify the exact motherboard or computer model.
• Read the manufacturer's release notes.
• Check whether the update addresses memory compatibility, hardware stability or relevant firmware issues.
• Back up important data.
• Use the manufacturer's official update procedure.
• Ensure stable power throughout the update.

Warning: An interrupted or incorrect BIOS update can make a computer unable to boot. Never install firmware intended for a different motherboard model or hardware revision.

If the crashes began immediately after a firmware update, consult the manufacturer before attempting a downgrade. Firmware rollback is not supported on every system.

Step 9: Analyze the Windows Crash Dump

If the error continues, analyzing the crash dump may provide additional information about the memory corruption event.

Windows can create crash dump files when a bug check occurs. Depending on system configuration, these files may be stored in locations such as:

• C:\Windows\Minidump - Small memory dump files.
• C:\Windows\MEMORY.DMP - A configured kernel, automatic or complete memory dump.

The actual location depends on the configured dump type and system settings.

Using WinDbg for Crash Dump Analysis

Windows Debugger (WinDbg) is a Microsoft debugging tool that can be used to inspect Windows crash dump files.

For advanced diagnosis:

1. Obtain WinDbg from the official Microsoft source.
2. Open the crash dump file in WinDbg.
3. Allow the debugger to load the appropriate symbols.
4. Run the following command in the debugger command window:

!analyze -v

This command performs a detailed analysis of the bug check and displays available diagnostic information.

For bug check 0x12B, Microsoft's documentation describes two different parameter scenarios.

Scenario A: Parameters 3 and 4 are both zero

This indicates that the memory manager detected a single-bit error on a memory page that was expected to be zeroed.

Parameter	Description
Parameter 1	Virtual address mapping to the corrupted page.
Parameter 2	Physical page number.
Parameter 3	Zero.
Parameter 4	Zero.

Microsoft identifies this scenario as a hardware memory error.

Scenario B: Parameters 3 and 4 are non-zero

This indicates that the Compressed Store Manager detected a failure while decompressing a memory page because of physical memory corruption. The failure may involve authentication, cyclic redundancy check (CRC) verification or decompression.

Parameter	Description
Parameter 1	FailStatus, indicating the type of failure.
Parameter 2	Compressed size of the page being read.
Parameter 3	Source buffer.
Parameter 4	Target buffer.

Important: These parameters provide diagnostic context, not an automatic identification of the defective hardware component. A debugger report must be interpreted alongside memory test results, device configuration and other system evidence.

Preserve the original dump file when seeking assistance from a qualified Windows debugging or hardware specialist. Crash dumps may contain sensitive information from system memory and should be shared only with trusted recipients.

Step 10: Check Windows System File Integrity

System file corruption can cause other Windows stability problems. Although repairing Windows files does not directly correct defective RAM or an incorrectly operating DMA device, checking system file integrity can help eliminate separate operating system corruption.

Open Command Prompt or Windows Terminal as an administrator.

First run the Deployment Image Servicing and Management (DISM) command:

DISM.exe /Online /Cleanup-Image /RestoreHealth

This command checks and repairs the Windows component store using available repair sources, normally Windows Update unless another source is configured.

After DISM completes, run System File Checker:

sfc /scannow

This command scans protected Windows system files and attempts to repair corrupted files using the component store.

Restart the computer after the operations complete and check whether the system remains stable.

Note: DISM and SFC are general Windows integrity checks, not dedicated repairs for the 0x0000012B bug check. They cannot repair defective physical RAM, faulty motherboard circuitry or firmware-related DMA corruption.

Advanced Troubleshooting for IT Technicians

If the error persists after basic diagnostic procedures, IT technicians should investigate the hardware and memory-access path systematically.

1. Correlate Crash Dumps with System Events

Review the crash dump, Windows System event log and Reliability Monitor together.

Look for a recurring pattern involving:

• Repeated 0x12B bug checks.
• Hardware installation or configuration changes.
• Power-state transitions.
• Recent driver or firmware updates.
• Other hardware-related errors recorded near the crash time.

Do not treat an event that happens near a crash as proof of causation without additional evidence.

2. Investigate DMA-Capable Devices

Since Microsoft identifies incorrect DMA operations and associated Memory Descriptor Lists (MDLs) as possible causes, advanced investigation may require examining device drivers and their interaction with physical memory.

Technicians should:

• Identify recently installed or updated DMA-capable devices.
• Review manufacturer-specific driver release notes.
• Inspect relevant crash dump information.
• Use appropriate Windows debugging tools where driver-level investigation is required.
• Escalate suspected hardware or driver defects to the device manufacturer.

Driver Verifier may be useful in certain driver troubleshooting scenarios, but it is not a routine first-line test for this bug check. Incorrect use can deliberately trigger additional system crashes and make Windows difficult to start. Use it only when a specific driver investigation is justified, with recovery arrangements in place.

3. Investigate Memory Controller and Motherboard Stability

When multiple memory modules or memory configurations produce errors, the investigation should extend beyond the RAM itself.

Potential areas include:

• Motherboard memory slots.
• CPU-integrated memory controller.
• Motherboard power delivery.
• Memory compatibility and supported configurations.
• Firmware configuration and hardware revision.

Use manufacturer-provided diagnostics and known-good compatible components to isolate the problem.

How to Prevent FAULTY_HARDWARE_CORRUPTED_PAGE Errors

Although hardware-related memory corruption cannot always be prevented, the following practices can reduce the likelihood of instability and help identify problems earlier.

• Use compatible RAM: Select memory supported by the motherboard and processor platform.
• Avoid unstable overclocking: Use manufacturer-supported memory settings and validate performance profiles.
• Maintain firmware: Install relevant BIOS and UEFI updates after reviewing compatibility and release information.
• Keep drivers updated: Use official and compatible drivers for hardware components.
• Check new hardware: Investigate system instability immediately after installing expansion cards or peripherals.
• Maintain proper cooling: Ensure that cooling systems and airflow operate according to the manufacturer's specifications.
• Protect the system from power interruptions: Use an appropriate power supply and suitable power protection for the computer.
• Monitor recurring crashes: Retain relevant error codes, event logs and crash dumps for technical investigation.
• Back up important data: Maintain regular backups to reduce the impact of unexpected system failures.

Frequently Asked Questions

1. What does FAULTY_HARDWARE_CORRUPTED_PAGE mean?

FAULTY_HARDWARE_CORRUPTED_PAGE is Windows bug check 0x0000012B. It indicates that the Windows memory manager detected physical memory corruption. Microsoft identifies defective RAM, incorrect DMA operations by a driver or device, and firmware-related memory corruption as possible causes.

2. Is 0x0000012B always caused by faulty RAM?

No. Defective RAM is one documented cause, but a driver or hardware device performing incorrect DMA operations and firmware-related memory corruption can also trigger this bug check. Memory testing and further hardware investigation are necessary before replacing RAM.

3. Can a faulty graphics card cause FAULTY_HARDWARE_CORRUPTED_PAGE?

A graphics card or its driver may deserve investigation because graphics hardware can use DMA to access system memory. However, the 0x12B stop code does not specifically identify the graphics card as the cause. Check the crash dump, driver history and hardware diagnostics before concluding that the graphics card is defective.

4. Can a Windows driver cause error 0x0000012B?

Yes. Microsoft documents that a driver or device can incorrectly modify physical memory through an incorrect DMA operation or associated MDL. Investigate recently installed or updated device drivers, especially those associated with hardware that performs direct memory access.

5. How do I check RAM for the 0x12B error?

Run Windows Memory Diagnostic by pressing Windows + R, entering mdsched.exe and selecting the restart-and-test option. After the test, inspect the MemoryDiagnostics-Results entry in Event Viewer under Windows Logs > System.

6. Can disabling XMP or EXPO fix this blue screen?

It may help if the memory configuration is unstable. Temporarily disabling XMP, EXPO or manual memory overclocking settings allows the computer to operate using its default supported memory configuration. If the crashes stop, investigate memory compatibility and stability rather than automatically assuming that a module is defective.

7. Can corrupted Windows system files cause 0x0000012B?

Windows system file corruption can cause other operating system problems, but Microsoft specifically describes 0x12B as physical memory corruption. DISM and SFC can check Windows component and protected system file integrity, but they do not repair defective RAM or incorrect DMA operations.

8. Does reinstalling Windows fix FAULTY_HARDWARE_CORRUPTED_PAGE?

Not necessarily. Reinstalling Windows cannot repair defective RAM, motherboard faults, a malfunctioning hardware device or firmware-related memory corruption. Hardware and driver diagnostics should be performed before considering an operating system reinstall.

9. Is FAULTY_HARDWARE_CORRUPTED_PAGE related to the PAGE_FAULT_IN_NONPAGED_AREA error?

Both are Windows memory-related bug checks, but they represent different detected conditions. FAULTY_HARDWARE_CORRUPTED_PAGE (0x12B) indicates physical memory corruption detected by the memory manager. PAGE_FAULT_IN_NONPAGED_AREA (0x00000050) indicates an invalid memory reference involving a nonpaged memory area. Their diagnostic procedures should not be treated as interchangeable.

10. When should I replace the RAM?

Consider replacing a RAM module when repeatable diagnostic errors follow that module across compatible slots, or when manufacturer testing confirms that it is defective. If errors occur only in one slot or across multiple known-good modules, investigate the motherboard, CPU memory controller and configuration before replacing RAM.

When to Contact Hardware or Technical Support

Professional hardware or Windows debugging assistance is recommended when:

• Windows Memory Diagnostic repeatedly reports memory errors.
• The computer continues to crash after returning memory settings to their defaults.
• Multiple known-good RAM modules produce errors.
• The system crashes after sleep or power-state transitions.
• Crash dump analysis suggests a possible device driver or DMA-related problem.
• The computer cannot remain stable long enough to complete diagnostic tests.
• BIOS or firmware-related problems are suspected.

Provide the technician with the exact stop code, crash dump where available, memory diagnostic results, recent hardware changes and relevant event logs. This evidence can reduce unnecessary component replacement and help isolate the actual fault.

Key Takeaways

The 0x0000012B FAULTY_HARDWARE_CORRUPTED_PAGE error is a Windows bug check associated with physical memory corruption. Although defective RAM is an important possibility, incorrect DMA operations by a driver or device and firmware-related memory corruption are also documented causes.

The recommended approach is to run Windows Memory Diagnostic, examine its results, investigate RAM and memory configuration, review relevant device drivers and hardware, and examine BIOS/UEFI firmware where appropriate.

For persistent failures, crash dump analysis with WinDbg can provide additional diagnostic information. Avoid replacing components or reinstalling Windows without first collecting sufficient evidence to identify the underlying problem.

Official References

• Microsoft Learn - Bug Check 0x12B: FAULTY_HARDWARE_CORRUPTED_PAGE - Official documentation covering the bug check parameters, causes and recommended initial investigation.
• Microsoft Support - Troubleshoot blue screen errors - General guidance for investigating Windows stop errors.
• Microsoft Learn - Windows Debugging - Documentation for Windows debugging tools and crash dump analysis.
• Microsoft Learn - Analyzing a Kernel-Mode Dump File with WinDbg - Guidance for opening and analyzing Windows kernel-mode crash dumps.
• Microsoft Learn - Repair a Windows Image - DISM documentation for checking and repairing Windows images.