STATUS_NO_MEMORY 0XC0000017 — Fast Fix

Yeah, this error is a pain. You're trying to launch an app or boot a VM and Windows just gives you that blank stare. “STATUS_NO_MEMORY.” Like the system's saying “Nope, I'm broke.” I've seen this in Windows 10, Server 2016, and Server 2019. The culprit here is almost always a corrupted or misconfigured pagefile, or a process that's gobbled up all available virtual address space. Let's fix it.

The Fast Fix — Rebuild the Pagefile

Don't bother tweaking RAM timings or reinstalling Windows yet. Do this first:

Open System Properties (Win + R, type sysdm.cpl, hit Enter).
Go to the Advanced tab, then under Performance, click Settings.
In the Performance Options window, go to the Advanced tab. Under Virtual memory, click Change.
Uncheck Automatically manage paging file size for all drives.
Select your system drive (usually C:), select No paging file, click Set. You'll get a warning — click Yes.
Reboot. Yes, your system will run with zero pagefile for a moment. That's fine.
After reboot, go back to the same settings. Select System managed size and click Set. Reboot again.

This resets the pagefile completely — clears any corruption or fragmentation that causes the 0XC0000017 error.

Why That Fix Works

The pagefile is Windows' second-chance RAM. When an app requests memory and physical RAM is full, the system swaps out less-used data to disk. If the pagefile is corrupt or its size is locked incorrectly, the OS can't allocate new memory. The error 0XC0000017 specifically means the memory manager ran out of virtual address space — not physical RAM. That's why adding more RAM sticks often doesn't fix it. The issue is the mapping of memory, not the chips.

I've seen this happen after a failed Windows Update that reset pagefile settings, or when a third-party tool like a RAM cleaner or game optimizer messes with memory management. The reset clears all that garbage.

When the Pagefile Fix Doesn't Work

Sometimes the culprit is a memory leak in a specific process. Here's the variation I see in enterprise environments:

SQL Server consuming all AWE memory. Run DBCC MEMORYSTATUS and check for locked pages.
Java apps with heap set too high, starving the OS. Check java -XX:+PrintFlagsFinal.
Chrome (yes, really) spawning hundreds of processes. Open Task Manager, sort by memory, kill any runaway browser tab.

To find the leak, use Sysinternals Process Explorer (free from Microsoft). Sort by “Virtual Size” (not private bytes). If one process is using 2GB+ of virtual address space, that's your suspect. Kill it, then see if the error stops.

Advanced Variation — BCD Memory Limit

Another less-common cause: a boot configuration setting that caps physical memory. I've seen this after someone misconfigured a server for a VM. Run this in an elevated command prompt:

bcdedit /deletevalue truncatememory

Then reboot. You can also check with bcdedit /enum — look for a “truncatememory” or “maxmem” entry. If it's there, delete it. This forces Windows to see all installed RAM.

Prevention — Keep It Simple

You don't need a RAM cleaner or a pagefile optimizer. Those cause more problems than they solve. Here's what actually works:

Set your pagefile to system-managed on a single drive. Don't spread it across multiple drives unless you really know what you're doing.
Don't run memory-intensive apps on systems with less than 8GB of RAM. That's a recipe for this error.
After a Windows Update, check your pagefile settings — updates sometimes reset them to zero.
Monitor virtual memory usage in Performance Monitor. If the “Committed Bytes” counter is consistently above 90% of your total RAM + pagefile, you're hitting a wall.

That's it. If you've followed these steps and still see 0XC0000017, you've got a hardware issue — bad RAM slot or failing memory module. Run MemTest86 overnight to confirm. But nine times out of ten, it's the pagefile. Fix that first.