STATUS_IN_PAGE_ERROR (0XC0000006) Fix Guide

1. Bad Memory (RAM) – The Number One Culprit

I've been doing this for 14 years. 80% of the time, 0XC0000006 comes from faulty RAM. The error shows up when Windows tries to read data from the page file stored on disk, and the memory controller chokes on it. You'll see it during heavy multitasking, gaming, or running a VM.

Real-world trigger: You're running Photoshop and Chrome with 20 tabs open, and bam — the app crashes with 0XC0000006. Or you get a BSOD while playing a game.

Fix: Run Windows Memory Diagnostic

1. Press Win + R, type mdsched.exe, press Enter.
2. Choose "Restart now and check for problems".
3. Let it run. It takes 15-30 minutes. Go get coffee.
4. After reboot, open Event Viewer (eventvwr.msc). Go to Windows Logs > System. Look for MemoryDiagnostics-Results with source "Windows Memory Diagnostic".

If it shows errors, you have bad RAM. No software fix will help. Replace the stick. If you have multiple sticks, test them one at a time. Pull all but one, run the test again. Swap sticks until you find the bad one.

Pro tip: Don't bother with third-party memory testers for quick checks. The built-in tool is reliable enough. If you want a deeper test, use MemTest86+ on a USB stick. Let it run overnight.

2. Dying Hard Drive or SSD

Second most common cause. The error means Windows can't read the page file from disk. If your drive has bad sectors, corrupt filesystem, or is failing, you'll get this. You'll also notice slow file access, weird noises from HDD, or apps freezing before the crash.

Real-world trigger: You try to open a large file from an external USB drive, and the system chokes. Or your system drive (usually C:) is an old mechanical drive with reallocated sectors.

Fix: Run CHKDSK and Check Drive Health

1. Open Command Prompt as Administrator.
2. Type chkdsk c: /f /r and press Enter. Say Y to schedule on next reboot.
3. Restart your PC. CHKDSK runs before Windows loads. Let it finish.
4. After reboot, check the drive's health. For SSDs, use the manufacturer's tool (Samsung Magician, Crucial Storage Executive, etc.). For HDDs, use CrystalDiskInfo. Look for "Caution" or "Bad" status.

What to do: If CHKDSK finds bad sectors (unreadable), replace the drive ASAP. If it's just filesystem corruption, CHKDSK might fix it. If the drive is fine, move to the next step.

3. Corrupt Page File

Less common but happens. The page file (virtual memory) gets corrupted. This often happens after a power loss, blue screen during a write operation, or if you've been messing with virtual memory settings.

Real-world trigger: Your PC lost power during a Windows update. Next boot, apps crash with 0XC0000006. Or you manually set a custom page file size and it went wrong.

Fix: Reset the Page File

1. Go to System Properties (right-click This PC > Properties > Advanced system settings).
2. Under Performance, click Settings.
3. Go to Advanced tab > Virtual memory > Change.
4. Uncheck "Automatically manage paging file size for all drives".
5. Select your system drive (C:). Select "No paging file". Click Set.
6. Reboot. Your PC runs without a page file for a bit. That's fine temporarily.
7. Go back to the same settings. Check "Automatically manage paging file size" again. Click Set. Reboot.

This forces Windows to recreate a fresh page file. Usually fixes corruption.

Quick-Reference Summary Table

That's it. Start with RAM, then disk, then page file. You'll fix 9 out of 10 cases. If none of these work, you might have a deeper issue like a corrupt Windows system file — but that's rare. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth just in case. But honestly, I've never seen that fix 0XC0000006. Start with the hardware.