FAULTY_HARDWARE_CORRUPTED_PAGE is Windows catching memory corruption red-handed. Programs store data in “pages” of memory, and Windows checksums some of them. When a checksum fails — the page’s contents changed when nothing should have changed them — you get this blue screen. The name blames hardware, and hardware is indeed the usual culprit, but drivers can corrupt pages too. The trick is figuring out which story fits your laptop before spending money on parts.

Start with the timing: did the crashes begin after a driver or Windows update? Suspect software. Did they start out of nowhere on an older laptop, or get slowly worse over weeks? Suspect the RAM. Either way, the fixes below are ordered to rule out the free causes first. This error shares DNA with other memory-related crashes like the MEMORY_MANAGEMENT blue screen , and the diagnostic approach overlaps — but the fixes here are specific to corrupted pages.

Why this happens

  • Failing RAM: The top cause by a wide margin. Memory cells degrade, flip bits, and corrupt the pages Windows is checksumming. Often starts intermittent and gets worse.
  • Buggy graphics or storage drivers: A driver writing past its own buffer corrupts neighboring pages. Despite the error’s name, this is a software problem with a software fix.
  • Unstable memory overclocks or XMP profiles: RAM pushed past its stable limits corrupts pages under load. “It was stable for months” doesn’t mean the overclock is still good — components age.
  • Overheating: High temperatures cause memory errors. Thin laptops with clogged vents can produce this error specifically during gaming or heavy workloads.
  • Corrupted page file or failing drive: If the page file lives on bad sectors, pages swapped to disk come back corrupted. A dying SSD produces the same symptom as dying RAM.
  • Corrupted system files: Less common, but damaged memory-management components can mis-handle pages.
  • Faulty motherboard memory slots: Rare, but a bad slot corrupts data the same way a bad stick does — which is why you test sticks in different slots.

How to fix it

Work through these in order — software and settings first, hardware tests to confirm.

Fix 1: Update graphics and chipset drivers

Rule out the driver story before testing hardware.

  1. Press Windows + X and open Device Manager.
  2. Download the latest graphics driver from your GPU vendor — NVIDIA , AMD , or Intel — and choose clean installation in the installer.
  3. Update the chipset driver from your laptop manufacturer’s support site.
  4. Restart and stress the laptop the way that usually triggers the crash. If it was a driver, you’re done.

Fix 2: Reset BIOS to stock and disable XMP

Unstable memory settings are a free fix — check them before buying RAM.

  1. Restart, tap F2 (or Del) to enter BIOS/UEFI setup.
  2. Load Setup Defaults / Load Optimized Defaults.
  3. Explicitly disable any XMP, EXPO, or memory overclock profile.
  4. Save and Exit, then use the laptop for a day or two. If the crashes stop, the memory tuning was the problem — leave it stock.

Fix 3: Run Windows Memory Diagnostic

The quick built-in test. It catches obvious failures; subtle ones need Fix 4.

  1. Press Windows + R, type mdsched.exe, press Enter.
  2. Choose Restart now and check for problems.
  3. After reboot, check the result in Event Viewer > Windows Logs > System, source MemoryDiagnostics-Results.

A failure here is conclusive — the RAM is bad. A pass is not conclusive; keep going.

Fix 4: Run MemTest86 for a definitive answer

This is the gold standard for memory testing, and for this specific error it’s worth the time.

  1. Download MemTest86 (free edition) and create a bootable USB with its included tool.
  2. Boot from the USB (tap F12 during startup for the boot menu on most laptops).
  3. Let it run at least two full passes — four is better. This takes 1-4 hours depending on RAM size.
  4. Any error, even one, means bad RAM. Test sticks individually (one at a time) to identify which one fails.

If MemTest86 passes four clean passes, your RAM is almost certainly fine — the corruption is coming from software or the drive.

Fix 5: Check the drive and page file

If RAM tests clean, look at storage — the other hardware that corrupts pages.

  1. Open Terminal (Admin) and run chkdsk C: /f /r, scheduling it for restart.
  2. Check SMART health with your drive maker’s tool (Samsung Magician, WD Dashboard, Crucial Storage Executive). Reallocated sectors = dying drive.
  3. As a diagnostic step, try disabling the page file temporarily: Settings > System > About > Advanced system settings > Performance Settings > Advanced tab > Change under Virtual memory, untick Automatically manage, set No paging file, restart, and test. If crashes stop with no page file, the drive’s page-file area is suspect. (Re-enable it afterward — running without a page file isn’t a long-term solution.)

Fix 6: Run SFC and DISM

Repair Windows’ own memory-management files.

  1. Open Terminal (Admin).
  2. Run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow again.
  3. Restart.

Fix 7: Test RAM slots and reseat the memory

If a stick fails, make sure it’s the stick and not the slot.

  1. Power off, unplug, and remove the battery if it’s removable. Ground yourself.
  2. Remove the RAM, blow out the slots with compressed air, and reseat the stick firmly until the clips snap.
  3. If you have two sticks and one failed MemTest86, test the “bad” stick in the other slot. Fails in both slots = bad stick. Passes in the other slot = bad slot (motherboard issue — a warranty matter).
  4. Check your warranty status before opening the chassis — on some laptops, opening it yourself voids coverage.

Fix 8: Clean the cooling system

If crashes happen only under load and temperatures are high, heat may be corrupting memory.

  1. Install HWiNFO and monitor temperatures during the crash-triggering workload.
  2. Blow compressed air through the vents (short bursts, with the laptop off).
  3. Keep the laptop on a hard, flat surface. If CPU temps stay above ~95°C under load after cleaning, the thermal paste or fans may need professional service.

Closing

FAULTY_HARDWARE_CORRUPTED_PAGE earns its name most of the time — bad RAM is the cause in the majority of cases that survive driver updates. But “most of the time” isn’t “always,” which is why the order matters: update drivers, reset the overclock, then let MemTest86 give you the definitive answer before you spend a cent. And back up your files early in the process — whatever is corrupting memory pages can corrupt your data too, and that’s the one outcome worth preventing regardless of the cause. If you’ve seen this error discussed with community fixes, our companion piece on Reddit’s most-cited fixes rounds out the picture.

Frequently asked questions

Does FAULTY_HARDWARE_CORRUPTED_PAGE always mean my RAM is dead?
Not always, but usually. The error means a memory page was corrupted — failing RAM is the top cause, followed by driver bugs corrupting memory, unstable overclocks, and occasionally a failing drive. Always test the RAM, but don’t buy replacements until you’ve ruled out drivers.
Can a driver cause FAULTY_HARDWARE_CORRUPTED_PAGE?
Yes. Despite the name, buggy drivers — especially graphics and storage drivers — can corrupt memory pages and trigger this exact error. Update drivers before concluding the hardware is at fault.
How do I test my RAM properly?
Use MemTest86 from a bootable USB and run at least two full passes — Windows Memory Diagnostic is a decent quick check but misses subtle faults. Any single error means the stick is bad. Test sticks individually to find the faulty one.
Will this error damage my files?
The error itself doesn’t delete files, but the underlying cause can: corrupted memory can garble data being written to disk, and a failing drive causes the same error. Back up important files before troubleshooting.