Fix 0x000002EF: Page Fault in Paging File Error

Quick answer: Add more RAM or increase your paging file size. The culprit here is almost always insufficient physical memory making Windows overwork the disk-based paging file.

What's Happening Here

0x000002EF means the Memory Manager tried to resolve a page fault — that's when a process needs data not currently in physical RAM — but it had to fetch it from the paging file on your hard drive or SSD. Normally, this happens all the time and it's harmless. The error triggers when the system's under severe memory pressure and disk I/O becomes the bottleneck. You'll see this most often on machines with 8GB or less RAM running multiple apps, or on servers with aggressive memory limits.

I've seen this on Windows Server 2016 hosts running SQL Server with default memory settings, and on Windows 10/11 laptops with 4GB RAM trying to run Teams, Chrome, and Visual Studio at the same time. The real fix is more RAM. Don't bother with registry tweaks or driver updates first — they rarely help here.

How to Fix It

Check your current RAM usage. Open Task Manager (Ctrl+Shift+Esc). Go to the Performance tab. If Memory usage is consistently above 90%, you're out of physical memory. wmic memorychip get capacity in Command Prompt shows installed RAM.
Increase the paging file size. Go to System Properties > Advanced > Performance Settings > Advanced > Virtual Memory. Uncheck "Automatically manage" and set a custom size. Start with 1.5x your RAM. For 8GB, set Initial and Maximum to 12288 MB.
```
# PowerShell command to set paging file to 12GB
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management' -Name PagingFiles -Value 'C:\pagefile.sys 12288 12288'
```
Reboot after.
Check disk health. Run wmic diskdrive get status in CMD. If it shows anything but "OK", replace the drive. Also check SSD wear level if it's an SSD — use CrystalDiskInfo or Get-PhysicalDisk in PowerShell.
Disable Superfetch and search indexing temporarily. Run services.msc, find SysMain (Superfetch) and Windows Search. Stop both, set to Disabled. Reboot. If the error stops, you can leave them off or investigate memory leaks in those services.
Test RAM with MemTest86. Bad RAM can cause erratic page fault behavior. Boot from a USB with MemTest86, let it run for at least one full pass. Any errors mean replace the stick.

Alternative Fixes If Main Steps Fail

If the error keeps happening after all that, try these:

Set paging file to System Managed but on a different drive — ideally a fast SSD separate from the OS drive. Avoid putting it on the same drive as heavy I/O apps.
Disable memory compression in PowerShell (admin): Disable-MMAgent -MemoryCompression. Reboot. This forces Windows to stop compressing in RAM, which can reduce page faults on some workloads.
Lower your maximum memory for running apps. Use System Configuration > Boot > Advanced Options > check Maximum memory and set it to 1024 MB below your total RAM (e.g., 7168 MB for 8GB). This reserves space for the kernel.
Update chipset drivers. Not the graphics driver — the motherboard chipset driver. A bad chipset driver can cause memory controller issues. Get it from your motherboard vendor, not Windows Update.

Prevention

The best prevention is to stop running out of RAM. If you're on a machine with less than 8GB, upgrade to 16GB — it's cheap and fixes 90% of page fault issues. For servers, monitor memory usage with PerfMon counters like Memory\Available MBytes and Paging File\% Usage. Set alerts at 10% free RAM. Also move the paging file to a dedicated SSD volume if you can — it won't fix low memory but it'll reduce I/O latency when page faults do happen.

One last thing: if you're using Windows 11 with a small SSD, disable hibernation (powercfg -h off). That freezes your RAM state to disk on sleep, which can trigger this error on wake if disk is slow. I've seen that one bite people more than once.