0XC00D10BD

Fix NS_E_DDRAW_GENERIC 0XC00D10BD in Windows Media Player

Windows Errors Beginner 👁 1 views 📅 May 27, 2026

Windows Media Player throws this video card error when it can't initialize DirectDraw. Usually a driver clash or corrupted codec. Fix takes 30 seconds to 15 minutes.

30-Second Fix: Disable Video Acceleration in WMP

This is the first thing I try on every machine that throws this error. Windows Media Player's video acceleration sometimes chokes on older graphics cards or weird codec combos. I've seen this exact 0XC00D10BD code pop up on a Dell OptiPlex from 2015 running Windows 10 22H2 — the machine was fine for YouTube but WMP kicked the bucket.

  1. Open Windows Media Player.
  2. Click Tools (if you don't see the menu bar, press Alt).
  3. Select Options > Performance tab.
  4. Under Video acceleration, drag the slider all the way to None.
  5. Click Apply, then OK. Close and reopen WMP. Try playing the video again.

If that works, you're done. Don't touch the slider again unless you update your driver. This fix works about 40% of the time in my experience.

5-Minute Fix: Update or Roll Back Your Video Driver

If disabling acceleration didn't cut it, the video driver is the next suspect. The 0XC00D10BD error fires when DirectDraw can't get a surface from the driver. That's almost always a driver mismatch — either it's too old, too new, or just plain broken. I had a client last month whose entire print queue died because of a junk driver update from Windows Update; same principle here.

Option A: Get the latest driver from the manufacturer

  1. Press Win + R, type devmgmt.msc, hit Enter.
  2. Expand Display adapters. Right-click your GPU, select Update driver.
  3. Choose Browse my computer for drivers > Let me pick from a list. Select the latest driver and install.

Option B: Roll back to a working driver

  1. In Device Manager, right-click your GPU, go to Properties.
  2. Click the Driver tab. If Roll Back Driver is available, click it.
  3. Restart your PC.

Skip Windows Update for drivers. Go straight to NVIDIA, AMD, or Intel's website. I've seen WU push an Intel driver on an AMD machine once. That caused all sorts of DirectDraw weirdness.

15-Minute Fix: Clean Reinstall Codecs and WMP

Drivers didn't do it? Then something is corrupt in the codec pipeline. Windows Media Player relies on DirectShow filters. A third-party codec pack (like K-Lite) can mess with these. Or a failed update left a broken filter behind.

Step 1: Reset WMP settings

Close WMP. Open Command Prompt as Administrator (press Win + X, select Terminal (Admin)). Run these commands in order:

regsvr32 wmp.dll
regsvr32 wmpeffects.dll
regsvr32 wmpdxm.dll
regsvr32 wmpnssci.dll
regsvr32 wmpui.dll

Each should say DllRegisterServer in [file] succeeded. If any fail, note which one — that's your clue.

Step 2: Uninstall third-party codec packs

Go to Settings > Apps > Installed apps. Look for K-Lite Codec Pack, CCCP, or any codec bundle. Uninstall it. Reboot. Test WMP again.

Step 3: Re-register DirectShow filters

Open Command Prompt as Admin again. Run:

regsvr32 quartz.dll
regsvr32 devenum.dll

These two handle DirectShow — the engine behind WMP's video playback.

Step 4: Replace corrupted system files (if still broken)

Run the System File Checker:

sfc /scannow

Let it finish. Then run DISM to fix the component store:

DISM /Online /Cleanup-Image /RestoreHealth

Restart after both complete. This catches corrupted DLLs that regsvr32 can't handle. I had one machine where quartz.dll was zero bytes — SFC fixed it.

Why This Happens: The Short Version

The error code 0XC00D10BD maps to NS_E_DDRAW_GENERIC. DirectDraw is the old-school graphics API Windows Media Player uses for video overlay. If your driver doesn't support it well, or a codec filter is pointing to a non-existent function, WMP gives up and throws this error. It's not your video card dying — it's a software handshake failure.

One last thing: if none of these work and you're on Windows 10 or 11, consider switching to VLC media player. It uses its own DirectDraw bypass and handles this error without breaking a sweat. But that's a workaround, not a fix — I'd still do the driver update first.

Was this solution helpful?