FAULTY_HARDWARE_CORRUPTED_PAGE wears its diagnosis on its sleeve: Windows found a corrupted page of memory and, true to the name, hardware is usually at fault. Stop code 0x0000012B means a single-bit error — one bit flipped from 0 to 1 or vice versa — in memory that Windows was actively using. Sometimes that’s a dying RAM stick. Sometimes it’s a driver writing where it shouldn’t.

The tricky part is that this error sits right on the hardware/software boundary, so the fix could be a free driver rollback or a RAM replacement. The troubleshooting below is designed to tell you which one you’re dealing with before you spend money — because nothing’s worse than buying new RAM only to discover it was a storage driver all along.

Why this happens

  • Failing RAM. The most common true cause. Memory cells wear out, and a cell that intermittently flips bits produces exactly this single-bit-error signature. It often starts occasional and gets more frequent.
  • The Intel Rapid Storage driver bug. The iaStorAC.sys driver has a long, documented history of causing this exact stop code on laptops. If your machine uses Intel RST (most Intel-based laptops do), this is suspect number one on the software side.
  • Loose or poorly seated RAM. On laptops with removable SODIMM sticks, a stick that’s worked slightly loose — from drops, heat cycling, or just time — makes intermittent contact and produces intermittent corruption.
  • Unstable memory overclock/XMP. Aggressive memory timings or overclocking utilities can push RAM past what it handles reliably, causing bit errors under load that vanish at stock settings.
  • A failing SSD or storage controller. Less common, but corruption can originate in the storage path — especially on laptops where the page file lives on a drive with failing flash cells.
  • Overheating. Heat increases the error rate of memory cells. Laptops that crash with this error only under sustained heavy load, in hot rooms, are telling you something about thermals.

How to fix it

Work through these in order — start with Fix 1 and only move on if the problem is still there.

Fix 1: Check for the Intel RST driver problem

This is the famous software cause — rule it out before suspecting your RAM.

  1. Press Win + X, open Device Manager, and expand Storage controllers (or IDE ATA/ATAPI controllers on older systems).
  2. Look for Intel Chipset SATA/PCIe RST Premium Controller or anything with iaStorAC in the name. Right-click it and choose Properties > Driver — note the version and date.
  3. If crashes started after a driver update, click Roll Back Driver. If not, right-click the controller and choose Update driver > Browse my computer > Let me pick — try the Standard SATA AHCI Controller driver instead, which bypasses the Intel driver entirely.
  4. Alternatively, download the latest RST driver from Intel’s driver support page — newer versions fixed several corruption bugs. Restart and test for a few days.

Fix 2: Run the Windows Memory Diagnostic

Free, built in, and definitive enough to act on.

  1. Save your work, then press Win + R, type mdsched.exe, and press Enter.
  2. Choose Restart now and check for problems. The laptop reboots into the diagnostic.
  3. Press F1 and select Extended test mix for a thorough check, then let it run — 30 minutes to over an hour depending on your RAM size.
  4. When Windows boots back, check the results: press Win + R, type eventvwr.msc, go to Windows Logs > System, and filter for source MemoryDiagnostics-Results. Any reported error means bad RAM, full stop. Memory errors also produce the PFN List Corrupt blue screen — if your crashes vary between stop codes, compare notes there.

Fix 3: Reseat the RAM

If your laptop has accessible RAM slots, a reseat fixes a surprising number of intermittent errors.

  1. Power off completely, unplug the charger, and — if removable — take out the battery. Hold the power button for 15 seconds to drain residual charge.
  2. Remove the bottom panel (check your model’s service manual for the screw layout — some use captive screws, some hide screws under rubber feet).
  3. Release the clips on each SODIMM, lift the stick out, and reseat it firmly until the clips snap back. Do this for every stick.
  4. While you’re in there, blow out dust with compressed air. Reassemble, boot, and see if the crashes stop. If your RAM is soldered (most ultrabooks), skip this — there’s nothing to reseat.

Fix 4: Reset memory timings to stock

Undo any overclocking or aggressive timings.

  1. Enter the BIOS/UEFI (usually F2 or Del during the manufacturer’s logo) and load Optimized Defaults or Restore Defaults.
  2. If you use Intel XMP or any memory overclock profile, disable it — run at the motherboard’s default JEDEC timings.
  3. Also reset any CPU undervolt/overclock in utilities like ThrottleStop or the manufacturer’s gaming hub.
  4. Save, exit, and test under the same workload that used to crash. If the errors vanish at stock settings, your overclock was never truly stable.

Fix 5: Update the SSD firmware and check drive health

Cover the storage side of the corruption path.

  1. Identify your SSD: Device Manager > Disk drives, note the model, then check the manufacturer’s site for a firmware update utility.
  2. Check the drive’s SMART health: open Terminal (Admin) and run wmic diskdrive get status — you want OK for every drive.
  3. Run chkdsk C: /f /r from an admin terminal to catch file-system-level corruption (schedule it for next restart if prompted).
  4. If the SSD health is degrading or firmware updates don’t help, clone to a new drive sooner rather than later — storage-origin corruption only gets worse. Drive-related crashes overlap with the NTFS blue screen family , which is worth reading if chkdsk keeps finding errors.

Fix 6: Address thermals

If crashes cluster under heavy load, heat is amplifying the errors.

  1. Monitor temperatures during your typical crashing workload — anything with a sensor readout works; sustained memory-adjacent temps are what matter, but CPU/GPU above 95°C indicates a cooling problem.
  2. Clean the vents and fans with compressed air, and stop using the laptop on soft surfaces that block intakes.
  3. Replace dried-out thermal paste if the laptop is more than a couple of years old — a repair shop can do this cheaply if you’re not comfortable opening the machine.
  4. Retest the same workload. Fewer crashes after cooling improvements confirms thermals were a contributor, even if RAM is also marginal.

Fix 7: Replace the faulty RAM

When diagnostics point at memory and reseating didn’t help, replacement is the fix.

  1. Confirm which stick is bad if you have two: run the memory diagnostic with one stick installed at a time (Fix 2, repeated). The one that errors is the one to replace.
  2. Buy a matching SODIMM — same DDR generation (DDR4/DDR5), speed, and ideally the same capacity. Your laptop manual or the existing stick’s label has the specs.
  3. Install the new stick, boot, and rerun the memory diagnostic to confirm clean results.
  4. Keep the receipt — RAM has long warranties, and if the replacement also errors, the motherboard’s memory slots are suspect, which is a professional repair.

Closing

The name of this error sends people straight to buying RAM, but the smart money does Fix 1 first — the Intel RST driver has caused more of these blue screens than all the bad RAM sticks combined. Work the list in order, let the diagnostics tell you what’s actually broken, and back up your files early: single-bit errors are a data-corruption risk, not just a crash risk. Handle it this week, not next month, and you’ll likely fix it for the cost of a driver update rather than a hardware replacement.

Frequently asked questions

What does Faulty Hardware Corrupted Page mean?
Stop code 0x0000012B: Windows caught a single-bit error in a memory page — a bit flipped where it shouldn’t have. The name blames hardware, and it’s right more often than not, but buggy drivers (especially Intel’s Rapid Storage driver) are a known software cause too.
Does this error always mean my RAM is bad?
Not always, but RAM is the prime suspect. Failing memory cells, poorly seated RAM sticks, and unstable memory overclocks all produce single-bit errors. Run the Windows Memory Diagnostic first — it’s free, built in, and settles the question in under an hour.
Can a driver really cause a 'hardware' error?
Yes. The infamous iaStorAC.sys (Intel Rapid Storage Technology) bug caused exactly this stop code on countless laptops. If your crashes started after a storage driver update, roll that driver back before you buy new RAM.
Should I keep using my laptop if I get this error occasionally?
Back up your important files first, then troubleshoot promptly. Single-bit memory errors can corrupt data silently — a flipped bit in a document or photo is worse than a blue screen. Don’t ignore it for weeks.