Fix ERROR_UNEXPECTED_MM_CREATE_ERR 0X0000022C on Windows
This error pops up when Windows can't create a memory mapping for a process. Usually a driver conflict or corrupted system file.
When you see this error
You're working on a Windows 10 or 11 machine, maybe after a recent update or driver install. You try to open an app — could be anything from a game to Visual Studio — and boom, you get ERROR_UNEXPECTED_MM_CREATE_ERR (0X0000022C). The app crashes immediately. Sometimes the whole system locks up for a second. I've seen this a lot on Dell and HP business laptops after Windows Update pushed a bad driver.
What's actually going on
The error code 0X0000022C means the Windows memory manager failed to create a memory mapping for a process. Think of a memory mapping as a way for an app to access a chunk of memory quickly. If something blocks that — like a buggy driver, a corrupted system file, or a failing disk — the OS throws this error.
The culprit here is almost always one of three things:
- Driver conflict — usually a graphics or storage driver that's not playing nice.
- Corrupted system files — a bad update or disk error messed up a critical file.
- Disk corruption — bad sectors or NTFS errors prevent the mapping.
Don't bother with registry cleaners or third-party RAM optimizers. They rarely help and often make things worse.
Step-by-step fix
I'll walk you through the fix in order. Each step builds on the last. If you skip one, the fix might not stick.
Step 1: Run SFC and DISM
Open Command Prompt as administrator. Click Start, type cmd, right-click it, choose "Run as administrator". Then run these commands one at a time:
sfc /scannowWait for it to finish. If it finds corrupt files, let it repair them. Then run:
DISM /Online /Cleanup-Image /RestoreHealthThis fixes the system image itself. Reboot after both finish.
Step 2: Check disk for errors
Open Command Prompt as admin again. Run:
chkdsk C: /f /rIt'll say it can't lock the drive and ask if you want to schedule it on next reboot. Type Y and reboot. Let it run — might take an hour on a big drive. Don't interrupt it.
Step 3: Roll back recent drivers
If the error started after a driver update, roll it back. Go to Device Manager (right-click Start > Device Manager). Find devices that updated recently — look under Display adapters, Storage controllers, and System devices. Right-click the device, choose Properties > Driver tab > Roll Back Driver. If the button is greyed out, you can't roll back. Then uninstall the driver completely and reboot. Windows will install the default driver.
Step 4: Uninstall recent Windows updates
If rollback doesn't help, undo the last Windows update. Go to Settings > Update & Security > Windows Update > View update history > Uninstall updates. Look for the most recent one. Right-click and uninstall. Reboot.
Step 5: Check Event Viewer for clues
If it still fails, open Event Viewer. Press Windows key + X, choose Event Viewer. Go to Windows Logs > System. Look for errors with source "Application Popup" or "BugCheck" around the time the error appeared. The details there will point to the specific driver or file causing the problem. Write down the filename — then google it with your error code. That's usually faster than guessing.
What to check if it still fails
If you've done all that and the error comes back, you're looking at hardware. Run a memory test: search for "Windows Memory Diagnostic" in Start, run it, let it reboot and test. If it finds errors, replace the RAM. Also run a full disk diagnostic from your drive manufacturer's tool — bad sectors can cause this error too.
One last thing: sometimes the issue is the app itself. Try reinstalling it. But if the error happens across multiple apps, it's definitely the system. Stick with the steps above — they've fixed this for me on dozens of machines.
Was this solution helpful?