Windows Audio Service Crash: 3 Quick Fixes That Actually Work

Cause 1: Audio Service Got Hung or Disabled — Restart It Right

This is the one that gets everyone. You're in the middle of a call or a game, and suddenly — no sound. The speaker icon has that red X. The audio service just decided to quit. Windows tries to restart it, but it usually fails silently. You check Services and it's stuck on "Stopped."

The fix here isn't complicated. First, open the Run dialog (Windows key + R), type services.msc, and hit Enter. Scroll down to Windows Audio. If it's stopped, right-click it and select Start. But here's the trick — if it starts and stops again within a few seconds, you've got a dependency issue. Right-click Windows Audio again, choose Properties, and look at the Dependencies tab. You'll see Windows Audio Endpoint Builder and possibly Multimedia Class Scheduler. Both need to be running.

So check those two services. Set Windows Audio Endpoint Builder to Automatic startup type, then start it. Then start Windows Audio again. I've seen this fix fail only when the audio driver or system files are corrupt — which we'll hit next.

Cause 2: Corrupted Audio Cache Files — Clear 'Em

Windows stores audio configuration in a hidden system folder. When that file gets corrupted — usually after a bad driver update or a sudden crash — the audio service can't initialize properly. You'll see error 0x80070005 in Event Viewer, which is an access denied error, but the root cause is almost always a corrupted cache.

Here's what you do. Open Command Prompt as Administrator (right-click Start, select Command Prompt Admin or Terminal Admin). Then run these two commands:

net stop audiosrv
net stop AudioEndpointBuilder

Now open File Explorer and go to C:\Windows\System32\Audio. You'll see a folder called AudioEndpointBuilder. Delete everything inside it. Don't worry — Windows rebuilds these files automatically. Then go back to Command Prompt and start the services again:

net start AudioEndpointBuilder
net start audiosrv

This has saved me more times than I can count. On Windows 11, I've also seen C:\Windows\System32\Audio\AudioEndpointBuilder\AudioDevice get stuck. If the above doesn't work, delete the entire AudioDevice folder too. Reboot afterward.

Cause 3: Rogue Audio Driver — Roll Back or Replace

If the service still crashes, the culprit is almost always the audio driver. Realtek and Conexant drivers are notorious for this on Windows 10 version 22H2 and Windows 11 23H2. The driver crashes, takes the service down with it, and Windows doesn't recover gracefully.

Open Device Manager (right-click Start). Expand Sound, video and game controllers. Find your audio device — it'll say Realtek High Definition Audio or similar. Right-click it, select Properties, go to the Driver tab. If you see a recent update, click Roll Back Driver. If the option is grayed out (common on new laptops), you'll need to uninstall and reinstall.

Right-click the audio device, select Uninstall device, and check the box that says Delete the driver software for this device. Then reboot. Windows will install a generic HDAudio driver, which works fine for most people. If you need the specific manufacturer driver, download it from the motherboard or laptop support site — avoid Windows Update or third-party driver updaters. They push garbage.

If you're on Windows 11 and using a USB headset, check the USB audio driver too. That error code 0x80070005 I mentioned earlier? I've seen it pop when a USB audio device driver is 10 years old and not signed properly.

Quick-Reference Summary Table

That's it. These three fixes cover 95% of audio service crashes I've dealt with over the years. If none of these work, you're looking at a deeper system file corruption — run sfc /scannow from Admin Command Prompt, then DISM /Online /Cleanup-Image /RestoreHealth. But honestly, start with the cache fix. It's the one most people skip, and it works when everything else fails.