Fix 0X000005AF: Paging File Too Small Error on Windows

1. Memory leak in a running application (most common cause)

I've seen this error more times than I can count. Nine times out of ten, it's not that your paging file is genuinely too small — it's that some app is eating RAM and not letting go. Had a client last month whose QuickBooks kept crashing with this error. Turned out a plugin had a memory leak, chewing through 12GB of RAM over a few hours.

Here's how to check and fix it:

1. Open Task Manager (Ctrl+Shift+Esc) and go to the Processes tab.
2. Sort by Memory usage. Look for any process using more than 2-3GB that you don't expect. Common culprits: Chrome with too many tabs, Microsoft Teams, antivirus scans, or custom business software.
3. If you see a suspicious process, right-click it and select End task. See if the error clears up.
4. If you can't kill it (like a system process), restart the machine. That frees all committed memory.

The real fix is to identify what app has the leak. Use Resource Monitor (run resmon in the Start menu) and watch the Memory tab over 15 minutes. If committed memory keeps climbing without dropping, you've found your leak. Update or reinstall that app.

2. Paging file size set too small or on a nearly full drive

If no memory leak, the next suspect is your paging file itself. Windows usually manages this automatically, but sometimes it guesses wrong — especially on systems with lots of RAM (16GB+). The error can pop up when virtual memory runs out, even if physical RAM is fine.

I had a small law firm where this error kept hitting after they upgraded to 32GB RAM. Windows set the paging file to only 2GB — figured they didn't need more. But their document management software was a memory hog that still wanted virtual memory.

Here's the fix:

1. Open System Properties (search for "Advanced system settings" in Start).
2. Under Performance, click Settings, then the Advanced tab.
3. Under Virtual memory, click Change.
4. Uncheck "Automatically manage paging file size for all drives."
5. Select your C: drive (or whatever drive has space).
6. Select Custom size. Set Initial size to 1.5x your physical RAM (in MB: multiply GB by 1024, then by 1.5). For 16GB RAM, that's 24576 MB. Set Maximum size to 3x your RAM (49152 MB for 16GB).
7. Click Set, then OK, then restart.

Warning: Don't set it too large — if your drive is almost full, you'll get other errors. Make sure the drive has at least 10GB free after setting the paging file. If your drive is tight, move the paging file to another drive with more room. You can set it on a secondary drive under the same settings.

3. System-wide commit limit hit due to too many concurrent processes

Less common, but I've seen it in development shops running Docker, multiple VMs, and SQL Server on the same box. The commit limit is the total amount of virtual memory available — RAM plus paging file. Some apps (like Docker or SQL) can reserve huge chunks upfront, even if they don't use them.

Check the commit limit: Open Task Manager, go to the Performance tab, then Memory. Look at "Committed" (in GB) — if it's close to your RAM + paging file size, you're hitting the ceiling.

Fix options:

• Reduce max memory for VMs: In Hyper-V or VMware, set each VM's memory to no more than 50% of your physical RAM unless you really need it.
• Limit Docker resources: In Docker Desktop, go to Settings > Resources, and drop the memory limit from default 4GB to 2GB or whatever fits.
• Increase paging file further: If you can't reduce the load, go back to the paging file settings and bump the Maximum size to 4x RAM (65536 MB for 16GB). This gives more headroom.
• Add more RAM: If you're regularly running multiple heavy apps, 16GB might not cut it. Upgrade to 32GB or 64GB. I tell clients: if you see this error more than once a month, it's time for more hardware.

Quick-reference summary table