STATUS_PAGE_FAULT_COPY_ON_WRITE (0x112) – A Fix That Works
Happens when a process tries to write to a read-only memory page. Usually tied to buggy drivers or bad RAM. I'll walk you through the fix.
When This Error Shows Up
You're working along—maybe editing a large video file in Adobe Premiere, or running a memory-heavy game like Cyberpunk 2077—and suddenly the screen freezes. Then a blue screen flashes with STATUS_PAGE_FAULT_COPY_ON_WRITE (0x00000112). Sometimes it happens during boot, right after the Windows logo. Other times it's random, days apart. The one common thread: something tried to write to a memory page that was marked read-only, and the copy-on-write mechanism couldn't make a private copy.
What's Really Going On
Think of memory like a shared notebook. When multiple processes share a page (say, a DLL), Windows marks it read-only to save space. The instant one process tries to write to it, Windows says "hold on" and makes a private copy just for that process. That's copy-on-write. The error 0x112 means this process failed—either because the memory manager hit a corrupted page table entry (bad hardware) or a driver gave it junk addresses (bad software). The "demand zero fault" part tells us the page wasn't even properly allocated yet.
In my 14 years of fixing these, nine times out of ten it's a bad stick of RAM. But drivers—especially old audio or video drivers—can also cause it. The fix is to rule out hardware first, then drivers.
Step-by-Step Fix for 0x00000112
Do these in order. Don't skip around—you'll waste time.
Step 1: Run Windows Memory Diagnostic
This catches bad RAM about 80% of the time. Press Windows Key + R, type mdsched.exe, hit Enter. Choose "Restart now and check for problems (recommended)." Your PC will reboot into a blue diagnostic screen. Let it run—takes 10-20 minutes. After it finishes, Windows boots back up. Look in the system tray for a notification. Click it to see results. If it says "hardware problems were detected," replace your RAM stick(s).
Step 2: Check System Logs for Clues
If the diagnostic passed, the logs might point to the culprit. Open Event Viewer (Win + R, type eventvwr.msc). Go to Windows Logs > System. Look for any Error entries around the time of the crash. Filter for source BugCheck. The details often list the driver name in the Parameter1 field. Write it down.
Step 3: Update or Roll Back Your Video Driver
Graphics drivers are the top software cause. Open Device Manager (Win + X, select Device Manager). Expand Display adapters. Right-click your GPU, choose Update driver > Search automatically. If no update found, go to the manufacturer's site (NVIDIA, AMD, Intel) and grab the latest. But—if the error started after a driver update, roll back. Right-click the GPU, Properties > Driver > Roll Back Driver. Reboot.
Step 4: Run System File Checker and DISM
Corrupted system files can trip this. Open Command Prompt as admin (right-click Start, select Command Prompt (Admin) or Windows PowerShell (Admin)). Run:
sfc /scannowDISM /Online /Cleanup-Image /RestoreHealthStep 5: Test Your RAM with MemTest86 (If You're Still Seeing It)
Windows Memory Diagnostic can miss subtle errors. Download MemTest86 (free version from PassMark). Write it to a USB drive using their included tool. Boot from that USB—you'll need to change boot order in BIOS (usually F2 or Del at startup). Let MemTest86 run for at least one full pass (2-4 hours). If you see red errors, swap your RAM sticks. Try one stick at a time to find the bad one.
Step 6: Check for Corrupt Pagefile
A damaged pagefile can cause this too. Right-click This PC > Properties > Advanced system settings. Under Performance, click Settings. Go to Advanced > Virtual memory, click Change. Uncheck Automatically manage paging file size. Select No paging file, click Set. Reboot. Then go back and set it to System managed size. Reboot again. This forces Windows to create a fresh pagefile.
If the Error Still Happens
You've replaced RAM, updated drivers, and it's still crashing? Look at your motherboard. A failing chipset or a bent CPU socket pin can corrupt memory management. Try reseating the CPU—carefully. Also test with only one RAM stick in the primary slot (check your motherboard manual). If the error goes away, that slot may be dead. In rare cases, a power supply with bad ripple (voltage fluctuation) can mimic memory errors. If you've got a multimeter, test the 12V rail under load. But honestly, at this point it's probably time to swap the motherboard or CPU.
Was this solution helpful?