Fix NS_E_WMP_OUTOFMEMORY (0XC00D11C6) in Windows Media Player

Windows Media Player throws NS_E_WMP_OUTOFMEMORY (0XC00D11C6) with the message "Your computer is running low on memory." But here's the thing — it's almost never about actual RAM. I've seen this on machines with 32GB of RAM playing a 10MB MP3. What's actually happening is that WMP's library database has gone stale, or a codec filter is leaking handles. The error is misleading because WMP is bad at distinguishing "no memory" from "can't allocate because something else is broken."

1. Corrupted Media Library Database (Most Common)

The #1 trigger: WMP's library database (CurrentDatabase_*.wmdb) gets corrupted after a crash or an interrupted sync. The player tries to index a file with a broken thumbnail or metadata, the allocation fails, and you get this error. You'll often see it right after launching WMP or when you click the Library tab.

Here's the fix — blow away the database and let WMP rebuild it:

1. Close Windows Media Player completely. Check Task Manager to make sure no wmplayer.exe process is running.
2. Press Win + R, type %LOCALAPPDATA%\Microsoft\Media Player, hit Enter.
3. You'll see files like CurrentDatabase_372.wmdb (the number varies). Delete every file in that folder. Yes, all of them.
4. Reopen Windows Media Player. It'll say "Welcome to Windows Media Player" and scan your monitored folders again.

Why this works: WMP stores the entire library as a single-file Extensible Storage Engine (ESE) database. Corruption in any table (metadata, thumbnails, playlists) makes the whole thing refuse to open. Deleting the files forces a clean rebuild. The library scan can take 5-10 minutes on a large collection, but the error will vanish.

2. Faulty Third-Party Codec Pack (Second Most Common)

If the library fix didn't help, blame codec packs. People install K-Lite, Shark007, or CCCP to play MKVs or FLACs. These pack DirectShow filters that sometimes register badly or conflict with WMP's internal decoders. The memory allocation failure here is actually the filter graph failing to negotiate a pin connection — WMP interprets that as an out-of-memory condition.

The fix: disable all third-party codecs temporarily.

• Open WMP, press Alt to show the menu, go to Tools > Options > Plug-ins.
• Under Video DSP and Audio DSP, uncheck any third-party filters. Leave the Microsoft ones enabled.
• Under Background, uncheck everything that's not Microsoft.

If the error stops, you've got a bad codec. Uninstall the codec pack — I've seen the most trouble with K-Lite Mega Pack versions 17.0.0 and 17.2.5 — and install a lightweight alternative like LAV Filters instead. It's cleaner, doesn't screw with the system codecs, and WMP won't choke on it.

3. Corrupted or Missing WMP System Files (Less Common)

Sometimes the problem isn't the library or codecs — it's the player itself. A Windows update or a failed repair can leave WMP's core DLLs in a bad state. The error shows up even after a library reset and codec removal. You'll see it when opening any file, even a fresh MP3.

Use the Deployment Imaging Service and Management Tool (DISM) to fix system files:

1. Open Command Prompt as Administrator.
2. Run: DISM /Online /Cleanup-Image /RestoreHealth. Wait for it to finish. It'll check the component store and replace corrupted files from Windows Update.
3. Then run: sfc /scannow to check all system files, including WMP's.
4. Reboot.

If DISM can't find the source files (common on offline systems), run DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\replacement\windows\sxS /LimitAccess pointing to a Windows installation media or a known-good system. The key insight: DISM fixes the base OS image, while SFC fixes the running files. You need both.

4. Virtual Memory Too Small (Rare, But Real)

I've seen this exactly twice in ten years. If the paging file is set to "No paging file" or is smaller than 200MB, WMP might genuinely run out of virtual address space when loading cover art for a large library. This is a corner case — you'd usually get a different error. But if you've done everything above and still get the error, check your virtual memory settings.

Go to System Properties > Advanced > Performance > Advanced > Virtual Memory. Set it to "System managed size". If you're on a system with 4GB RAM or less, set the initial size to 1.5x your RAM (e.g., 6144 MB for 4GB) and the max to 3x (12288 MB). Reboot.

Quick-Reference Summary

Start with the library delete. Nine times out of ten that kills the error. Skip the RAM upgrades — your computer has enough memory. The error message just picks the wrong explanation.