0X00000237

Fix ERROR_PAGEFILE_QUOTA_EXCEEDED (0x237) on Windows

Page file quota exceeded? Here's what triggers it and how to fix it in Windows 10/11 with step-by-step instructions.

You're minding your own business, maybe running a big Excel macro or a video edit, and Windows throws up a dialog: "ERROR_PAGEFILE_QUOTA_EXCEEDED" with the code 0x00000237. It's not a crash, but programs start failing or won't open. This happens most often when you've got many apps running at once — like 30 browser tabs, Outlook, and a virtual machine — and your system's page file can't keep up.

The root cause is simple: Windows uses a hidden file called pagefile.sys as virtual memory when your RAM fills up. Each process has a quota—a cap on how much of that page file it can use. When a program hits that cap, you get error 0x237. It's not that your disk is full or your RAM is dead. It's that the page file is either too small or the quota is too tight.

Here's the fix. I'll walk you through it step by step. Don't skip ahead—each step builds on the last.

Step 1: Check your current page file settings

First, let's see what you're working with. Right-click the Start button and select System. Then click Advanced system settings on the right side. You'll see a window called System Properties. Under the Advanced tab, click the Settings button in the Performance section. Then go to the Advanced tab in that new window and click Change under Virtual memory.

You should see a checkbox that says Automatically manage paging file size for all drives. If it's checked, that's often the culprit—Windows usually handles it fine, but when you have special workloads, the auto size just isn't enough. Write down what you see here: which drives have a page file, and what the current size is. You'll need that later.

Step 2: Set a custom page file size

Uncheck the automatic management box. Now select your C: drive (or whichever drive has Windows installed). Choose Custom size. Here's the part that trips up most people: the initial size should be 1.5 times your RAM, and the maximum size should be 3 times your RAM. If you have 16 GB of RAM, that's 24576 MB for initial and 49152 MB for maximum.

Don't be shy with the maximum. The page file won't actually grow to that size unless it has to, but if it does need to grow, you don't want it to fail. Set it and click Set, then OK.

After clicking OK, Windows will ask if you want to restart. Don't do it yet—we've got more to do.

Step 3: Increase the process quota limit

This is the part most guides miss. Even with a bigger page file, the per-process quota might still be too low. You need to tweak a registry value. Here's how:

  1. Press Win + R, type regedit, and hit Enter.
  2. Navigate to this key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
  3. Look for a DWORD called PagedPoolQuota. If it's not there, right-click in the right pane, select New > DWORD (32-bit) Value, and name it PagedPoolQuota.
  4. Double-click it, select Decimal, and set the value to 100000000 (that's 100 MB). This raises the quota per process.
  5. Click OK and close regedit.

Now you can restart your computer. After it boots, the error should be gone. Test it by reopening the app that gave you trouble.

What if it still fails?

If you still see error 0x237, check a few things:

  • Is your disk full? The page file needs free space to grow. Open File Explorer and see how much free space is on C:. If it's less than 10% of the drive, that's your problem. Free up space or move the page file to another drive with more room.
  • Are you running 32-bit software? A 32-bit program can only use up to 2 GB of page file, no matter what you set. If you're running old apps, check if they have a 64-bit version.
  • Do you have antivirus that's overzealous? Some security suites monitor pagefile.sys and can interfere. Temporarily disable yours and see if the error disappears. If it does, add an exclusion for pagefile.sys.

If none of that helps, you might have a corrupt page file. You can reset it completely: disable the page file entirely, restart, then re-enable it with the settings from Step 2. That's a nuclear option, but it's solved a bunch of weird quota errors for my users.

Last thing: if you're on an SSD, make sure TRIM is enabled (it usually is). A trimmed SSD gives you better page file performance. But honestly, the steps above will fix the quota error in 9 out of 10 cases.

Related Errors in Windows Errors
0X00003627 ERROR_IPSEC_IKE_INVALID_SITUATION (0X00003627) Fix 0X801F0005 Fixing ERROR_FLT_INVALID_NAME_REQUEST (0X801F0005) on Windows 10/11 0X000020C3 Fix ERROR_DS_NONEXISTENT_MAY_HAVE (0X000020C3) in AD Schema 0xc000021a BSOD 0xc000021a: Critical System Process Failure Fix

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.