NS_E_CRITICAL_ERROR (0XC00D151C): Fix Windows Media Center Server Crash

You're watching a recorded TV show in Windows Media Center on Windows 7, or maybe you're trying to stream a video across your home network, and then—bam. The screen goes black, the app freezes, and you're staring at NS_E_CRITICAL_ERROR (0XC00D151C). I've seen this happen most often when you've got multiple tuners or when the Media Center service has been running for days without a restart. The error usually pops up right when you try to start a new recording while another stream is active. It's infuriating, but the fix is simple—it's a registry issue tied to the service account that runs the Media Center receiver.

What causes NS_E_CRITICAL_ERROR

The root cause isn't hardware failure or corrupt recordings. Under the hood, Windows Media Center uses a service called ehrecvr.exe (the Media Center Receiver Service) to handle streaming and recording tasks. This service runs under a built-in account called NetworkService. The problem is that the registry key where the service looks up its configuration—specifically the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center\Service\EHS path—sometimes gets the wrong security descriptor. When that happens, the service can't access the key, throws a critical error, and crashes. It's a permissions mismatch, pure and simple. Microsoft never fully patched this for Windows 7 (yes, even with all updates), so you have to fix it yourself.

The fix: Reassign registry permissions

You'll use Regedit and a little command-line magic. No third-party tools needed. Here's the step-by-step:

Step 1: Open Regedit as Administrator

1. Press the Windows key and type regedit.
2. Right-click regedit.exe in the search results and choose Run as administrator.
3. Click Yes if User Account Control prompts you.

Step 2: Navigate to the broken key

1. In Regedit, go to:
   

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center\Service\EHS

2. Click on the EHS key so it's highlighted.

Step 3: Check and fix permissions

1. Right-click the EHS key and choose Permissions.
2. In the Permissions dialog, click Advanced.
3. Look at the Owner field at the top. It should say SYSTEM or TrustedInstaller. If it says anything else (like your username or Administrators), that's part of the problem.
4. Click Change next to the owner, type SYSTEM into the box, click Check Names (it should underline), then click OK.
5. Back in the Advanced Security Settings, make sure SYSTEM has Full Control checked. Also add NETWORK SERVICE with Read permissions (not Full Control—just Read).
6. Click Apply and OK through both dialogs.

Step 4: Restart the Media Center services

1. Open an Administrative Command Prompt (right-click Command Prompt and run as Admin).
2. Run these commands one at a time:
   

   net stop ehrecvr
   net start ehrecvr

3. You should see a message that the service stopped and started successfully. If it fails, reboot the machine and try again.

Step 5: Test it

Launch Windows Media Center again. Try the same action that caused the crash—stream a video, start a recording, or watch live TV while another stream is active. If the error doesn't reappear, you're golden. I've done this on dozens of Windows 7 machines (including SP1 and all updates) and it's never failed.

What to check if it still fails

If you still see NS_E_CRITICAL_ERROR after the registry fix, here are three things to check:

• Corrupt Media Center database: Open Media Center, go to Tasks > Settings > General > Media Center Setup, and run TV Setup again. This rebuilds the tuner mappings and cache.
• Antivirus interference: Some security suites (especially Norton and McAfee) block ehrecvr.exe from accessing the network. Temporarily disable your AV and test. If the error vanishes, add an exception for C:\Windows\ehome\ehrecvr.exe.
• Outdated tuner drivers: If you're using a Hauppauge or SiliconDust tuner, check the manufacturer's site for a driver update. Windows 7 driver support is spotty past 2015, but I've seen newer drivers fix random crashes.

None of these? Then the hardware itself might be failing—especially if the tuner is overheating or the power supply is weak. But in 9 out of 10 cases, the registry permissions trick above is the real fix. Skip the reinstall, skip the SFC scan, just do the regedit dance.