Fix STATUS_UNEXPECTED_MM_EXTEND_ERR 0XC00000EC on Windows

Yeah, this one is a pain

You're trying to copy a file, run a backup tool, or even just open a PDF, and bam—STATUS_UNEXPECTED_MM_EXTEND_ERR (0XC00000EC) slams the door shut. It's a memory mapping error, meaning the OS tried to extend a mapped file in memory and the system said no. I've seen this mostly on Windows 10 22H2 and Windows 11 23H2 machines that are a bit older (5+ years) or have had recent driver updates. Let's cut through the noise and fix it.

The Quick Fix (Registry + Service)

Press Windows Key + R, type regedit, and hit Enter. Click Yes on the UAC prompt.

Go to

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

Right-click in the right pane, select New > DWORD (32-bit) Value. Name it ClearPageFileAtShutdown.
Double-click that new value, set it to 1, click OK.
Now close Registry Editor.
Press Windows Key + R, type services.msc, hit Enter.
Scroll down to SysMain (it might be called Superfetch on some older builds). Right-click it and select Stop.
Right-click SysMain again, choose Properties. Set the startup type to Disabled. Click Apply, then OK.
Reboot your machine.

What you should see after reboot: The error should be gone. If you try the same file operation that failed before, it should complete without the 0XC00000EC message. If it still appears, move to the next section.

Why This Works

The registry key forces Windows to flush the page file entirely on shutdown. That clears out any corrupted memory mappings that might've been left hanging. Disabling SysMain (formerly Superfetch) stops the service from aggressively pre-loading data into memory—which is the main trigger for this error in my experience. SysMain tries to predict what files you'll need and maps them into memory early. On some hardware, especially with older SSDs or HDDs, this creates mapping conflicts that throw the 0XC00000EC. Kill the service, and you remove the root cause.

Less Common Variations

Driver Rollback

Sometimes the error is tied to a bad storage driver update. If the registry fix didn't stick:

Open Device Manager (right-click Start > Device Manager).
Expand Storage controllers. Find your SATA or NVMe controller (usually "Standard NVM Express Controller" or "Intel SATA Controller").
Right-click it, select Properties, go to the Driver tab. Click Roll Back Driver if it's not grayed out. If it is, you'll need to uninstall the driver and let Windows reinstall the default.
Restart.

I've seen this fix the error on Dell Optiplex 7080 and HP EliteBook 840 G7 models after a faulty WHQL driver from the OEM.

Check for Memory Pressure

If you're running low on RAM (less than 8 GB) or have many Chrome tabs open, the error can pop up. Close unnecessary programs. You can also run a quick checkdisk:

Open Command Prompt as Admin (right-click Start > Windows Terminal (Admin)).
Type chkdsk C: /f and press Enter. It'll schedule a check on next boot.
Restart and let it run. This can fix corrupt file system structures that confuse memory mapping.

Prevention

Once you've got the error squashed, keep it away:

Keep SysMain disabled unless you're on a very new NVMe drive with a fast CPU. On older hardware, it causes more problems than it solves.
Set ClearPageFileAtShutdown to 1 permanently. It adds about 30 seconds to shutdown time, but it's worth the stability.
Update your storage driver manually from the manufacturer's site (Intel, AMD, Samsung) instead of relying on Windows Update. Windows Update pushes generic drivers that don't play nice with memory mapping on specific chipsets.
Keep at least 20% of your drive free—low disk space on the system drive can cause the page file to fragment, triggering the error.

Bottom line: this isn't a hardware failure. It's Windows being clever and failing. The registry key plus disabling SysMain is the real fix. If you're still seeing the error after that, you probably have a corrupt driver or a failing drive, so run a full chkdsk and consider a fresh driver install.