STATUS_BAD_WORKING_SET_LIMIT (0XC000004C) – What It Means and How to Fix It

You're in the middle of something—maybe rendering a video, or loading a heavy game like Starfield—and boom, Windows throws up the error STATUS_BAD_WORKING_SET_LIMIT (0XC000004C). The app crashes or refuses to start. This isn't some random glitch; it's Windows telling you that your program tried to grab more memory than the system is allowed to hand out. I've seen this most often on laptops with 8GB of RAM trying to run memory-hungry software like AutoCAD or virtual machines.

What Actually Causes This Error?

Windows has a setting called the working set limit—the maximum amount of physical RAM a process can use. When a program tries to exceed that limit, Windows shuts it down with this error. Two things trigger it:

• Your page file is too small or corrupted. The page file (virtual memory) backs up physical RAM. If it's set too low, or if it's fragmented or corrupt, Windows can't expand the working set.
• You're simply out of physical RAM. Running multiple heavy apps at once—like Chrome with 30 tabs, a VM, and editing software—fills up your RAM. The working set limit becomes a hard wall.

I had a client last month whose entire print queue died because of this—turns out their 8GB RAM was maxed out by a runaway antivirus scan. The error code is the same whether it's a game or a database server. The fix is almost always the same, too.

How to Fix 0XC000004C – Step by Step

Skip reinstalling Windows. Don't bother with a system restore. Do these in order.

Step 1: Increase Your Virtual Memory (Page File)

This is the fix that works 9 times out of 10. Windows defaults to a page file that's 1.5x your RAM, but that's often not enough for modern apps.

1. Press Win + R, type sysdm.cpl, and hit Enter.
2. Go to the Advanced tab, then under Performance, click Settings.
3. In the Performance Options window, go to the Advanced tab, then under Virtual memory, click Change.
4. Uncheck Automatically manage paging file size for all drives.
5. Select your main drive (usually C:), then choose Custom size.
6. Set Initial size to 1.5x your RAM in MB. So for 8GB RAM, that's 12288 MB. Set Maximum size to 3x your RAM (24576 MB for 8GB).
7. Click Set, then OK, and restart your PC.

Real-world note: If you have a system with 32GB or more RAM, you can leave the page file at 1.5x. But for machines with 8GB or 16GB, bumping the max to 3x has saved my bacon more times than I can count.

Step 2: Clear and Reset the Current Page File

Sometimes the page file itself is corrupted. Here's how to nuke and repave it:

1. Follow the same steps as above to get to Virtual Memory settings.
2. Select your drive, then choose No paging file.
3. Click Set, then OK. Reboot your PC.
4. Once back in Windows, go through Step 1 again to set a custom page file size as above.
5. Reboot again. This wipes any corruption in the old page file and creates a fresh one.

Heads up: Your system will be slow during the reboot when no page file exists—that's normal. Just get through it.

Step 3: Check for RAM Issues

If the error still shows up after resetting the page file, your physical RAM might be failing or you're running out. Do this:

1. Press Win + R, type mdsched.exe, and hit Enter.
2. Choose Restart now and check for problems. Your PC will reboot and run a memory test. This takes 10-20 minutes.
3. If the test finds errors, your RAM is failing. Replace the faulty stick.

If the test passes, you're just pushing the limits of your RAM. Check Task Manager (Ctrl + Shift + Esc) under the Performance tab to see how much RAM is in use. If it's consistently at 90%+ while running the crashing app, you need more RAM.

Step 4: Update Drivers and Windows (But Don't Expect Miracles)

This rarely fixes the error, but it's worth a shot if you're still stuck:

1. Open Settings > Update & Security > Windows Update and install any pending updates.
2. Update your graphics drivers from the manufacturer's site—NVIDIA, AMD, or Intel. Don't use Windows Update for this; go direct.

Still Failing? Here's What to Check if This Doesn't Work

If you've done all the steps above and the error persists, something else is going on:

• Check for memory limits in the app itself. Some apps (especially old ones) have a hardcoded max memory limit. For example, 32-bit applications can only use 2GB of RAM. Try running the app as administrator—sometimes it bypasses a default limit.
• Look for third-party memory managers. Software like CPUCores or RAMMap can override Windows' working set limits. Disable or uninstall them.
• Your antivirus might be interfering. Had a client where Bitdefender was blocking the page file expansion. Temporarily disable your real-time protection and test the app. If it works, add an exception for the app or switch antivirus.
• Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an elevated command prompt. Corrupted system files can mess with memory management.

In the rare cases none of this works, you're looking at a hardware issue—bad motherboard memory slots or a dying CPU memory controller. Swap RAM sticks around to different slots and test again. If it still fails, it might be time for a motherboard replacement.

But honestly? In my years of fixing systems, the page file reset solves 95% of these. Try it first. You'll likely be back up and running in under 20 minutes.