Fix 0x000002EC Demand Zero Fault on Windows

You Hit 0x000002EC? Let's Get This Fixed

Yeah, this error's a pain. Your machine blue-screened with ERROR_PAGE_FAULT_DEMAND_ZERO (0x000002EC). It usually pops up when you're booting up or after a sleep cycle. I've seen it on Windows 10 and 11, often after a driver update or a RAM upgrade that went sideways. Here's what to do.

The Fix (Start Here)

Skip the system restore nonsense. The culprit is almost always one of three things: bad RAM, a corrupt pagefile, or a driver that thinks it owns memory it doesn't. Let's hit them in order.

Run Windows Memory Diagnostic. Press Win + R, type mdsched.exe, hit Enter. Choose "Restart now and check for problems." Let it run through two passes. If it finds errors, your RAM is toast. Replace it.
Reset the pagefile. Had a client last month whose pagefile got corrupted after a sudden power loss. Go to System Properties > Advanced > Performance Settings > Advanced > Virtual Memory > Change. Uncheck "Automatically manage," set a custom size (say 4096 MB initial, 8192 MB max for a system with 8 GB RAM), click Set, reboot. Then come back, set it back to "System managed size," and reboot again. That rebuilds the file clean.
Update your chipset and storage drivers. Go to your motherboard or laptop manufacturer's site, download the latest chipset, SATA, and NVMe drivers. Don't use Windows Update for this—it's often behind. Install, reboot.

After each step, test. If the error's gone after resetting the pagefile, you're done. If not, move to the next.

Why This Works

A demand zero fault happens when the Windows memory manager needs a page full of zeros (for a new process, say) but can't find one. The page pool might be exhausted, or a hardware component is feeding bad data. RAM errors literally randomize bits—zeros become ones. A corrupt pagefile might have stale entries. Drivers that play fast and loose with memory allocation can leave the system in a state where it thinks a page is zeroed when it's not. By narrowing down to hardware or software, you cut the root cause.

Less Common Causes (Tried the Above? Dig Deeper)

If the standard fix didn't stick, you're looking at rarer scenarios:

Faulty RAM slot or timings. I've seen sticks that pass MemTest86 in slot 1 but crash in slot 2. Swap your RAM modules around. Also, if you overclocked or enabled XMP, try running at stock speeds (2133 MHz for DDR4, 4800 for DDR5).
Storage controller issues. A dying SSD or HDD can cause pagefile reads to return garbage. Download the manufacturer's diagnostic tool (like Samsung Magician or CrystalDiskInfo) and check for reallocated sectors or CRC errors.
Third-party antivirus or security software. Some AV hooks into memory management. Temporarily uninstall (not just disable) McAfee, Norton, or any low-tier AV. Reboot, see if the error returns. Had a client whose Trend Micro was intercepting page faults incorrectly—gone after uninstall.
Corrupt system files. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an admin command prompt. This fixes corrupted Windows components that might be mismanaging memory.

Prevention for Next Time

You don't want to see this again. Here's the short list:

Test new RAM thoroughly. Run MemTest86 for at least one full pass (a few hours) before trusting it.
Kill unnecessary startup programs. They grab memory pages at boot, increasing the chance of demand faults if something goes wrong.
Keep your pagefile on the fastest drive available (NVMe > SATA SSD > HDD). A slow or failing drive makes page fault issues worse.
Don't disable the pagefile entirely. Some "optimization" guides say to. They're wrong. Windows needs it for memory management. Set it to system-managed.
Update BIOS if you're on a recent CPU (like Intel 12th gen or AMD Ryzen 5000+). BIOS updates often fix memory controller bugs that cause these exact faults.

That's it. You should be back to normal within an hour. If you're still stuck after all this, you might be dealing with a failing motherboard or CPU—time to swap hardware. But 9 out of 10 times, it's the RAM or pagefile. Go get it.