Why AudioEndpointBuilder Crashes on Wake From Hibernate on Windows 11

After resuming from hibernate, your Windows 11 computer may lose all sound output. The system tray speaker icon shows a red X, and apps report no audio device. This problem occurs because the AudioEndpointBuilder service, which manages audio endpoints like speakers and headphones, crashes or fails to restart during the wake process. The crash is often tied to a driver state mismatch or a power management conflict between the audio driver and the hibernate-restore cycle. This article explains the root cause of the AudioEndpointBuilder crash on wake from hibernate and provides a set of tested fixes to restore audio reliably.

Why AudioEndpointBuilder Fails After Hibernate on Windows 11

AudioEndpointBuilder is a Windows service that enumerates and manages audio endpoints — the logical devices representing your speakers, headphones, and microphones. When you put the PC into hibernate, the system saves the entire memory contents, including the state of all drivers and services, to the hiberfil.sys file. On wake, Windows restores this state. If the audio driver’s power management routines do not handle the transition correctly, the driver can be left in an inconsistent state. AudioEndpointBuilder then attempts to query the driver for endpoint information but receives a corrupt or invalid response. This causes the service to crash with an access violation or a timeout. The crash is logged in Event Viewer under System logs with source “AudioEndpointBuilder” and event ID 1 or 1000.

The most common root cause is the audio driver’s power management policy combined with fast startup — a hybrid shutdown setting that uses a partial hibernate file. Fast startup is enabled by default on Windows 11. When fast startup interacts with a full hibernate cycle, the driver may not reinitialize its hardware correctly. Another frequent cause is a third-party audio enhancement or virtual surround sound driver that does not survive the hibernate-restore sequence.

Steps to Fix the AudioEndpointBuilder Crash on Wake from Hibernate

The following steps address the most common causes. Perform them in the order listed. After each step, test audio by putting the PC into hibernate and waking it.

Step 1: Disable Fast Startup in Power Options

1. Open Power Options
   Press Win + R, type powercfg.cpl, and press Enter. In the left pane, click Choose what the power buttons do.
2. Change settings that are currently unavailable
   Click the link labeled Change settings that are currently unavailable (requires administrator privileges).
3. Uncheck Fast Startup
   Under Shutdown settings, uncheck Turn on fast startup (recommended). Click Save changes.
4. Restart and test
   Restart the PC, put it into hibernate, wake it, and check audio playback.

Step 2: Prevent the Audio Driver from Being Powered Off

1. Open Device Manager
   Right-click the Start button and select Device Manager.
2. Locate your audio driver
   Expand Sound, video and game controllers. Look for your audio device — typically Realtek High Definition Audio, Intel Display Audio, or NVIDIA High Definition Audio. Right-click it and select Properties.
3. Disable power saving
   Go to the Power Management tab. Uncheck Allow the computer to turn off this device to save power. Click OK.
4. Repeat for other audio devices
   If multiple audio devices appear in the list, repeat the steps for each one. Then restart and test hibernate wake.

Step 3: Configure the Windows Audio Endpoint Builder Service to Restart on Failure

1. Open Services
   Press Win + R, type services.msc, and press Enter.
2. Find the service
   Scroll down to Windows Audio Endpoint Builder. Right-click it and select Properties.
3. Set recovery options
   Go to the Recovery tab. For First failure, select Restart the Service. For Second failure, also select Restart the Service. For Subsequent failures, select Take No Action. Set Reset fail count after to 1 day. Click Apply then OK.
4. Restart the service
   Right-click Windows Audio Endpoint Builder again and select Restart. Then restart the PC and test hibernate wake.

Step 4: Refresh the Hibernate File and Power Policy

1. Open Command Prompt as Administrator
   Right-click the Start button and select Windows Terminal (Admin) or Command Prompt (Admin).
2. Disable hibernate
   Type powercfg /h off and press Enter. This deletes the hiberfil.sys file.
3. Re-enable hibernate
   Type powercfg /h on and press Enter. This creates a fresh hiberfil.sys file.
4. Reboot and test
   Restart the PC. Put it into hibernate, wake it, and check audio.

Step 5: Remove Third-Party Audio Enhancements

1. Open Sound settings
   Press Win + I to open Settings. Go to System > Sound. Under Advanced, click More sound settings.
2. Disable enhancements
   In the Sound window, select your default playback device and click Properties. Go to the Enhancements tab. Check Disable all enhancements. Click Apply then OK.
3. Uninstall third-party audio software
   If you have installed audio enhancement software — such as Dolby Atmos, DTS Sound, or Nahimic — open Settings > Apps > Installed apps, find the software, and click Uninstall. Restart and test hibernate wake.

Step 6: Update or Roll Back the Audio Driver

1. Check for driver updates
   Open Device Manager, expand Sound, video and game controllers, right-click your audio device, and select Update driver. Choose Search automatically for drivers. If Windows finds an update, install it and restart.
2. Roll back the driver if the issue started after an update
   Right-click the audio device, select Properties, go to the Driver tab, and click Roll Back Driver (if available). Follow the prompts and restart.
3. Download the driver from the manufacturer
   Visit your PC or motherboard manufacturer’s support site. Download the latest audio driver for your model. Install it manually and restart.

If the AudioEndpointBuilder Crash Continues After the Main Fixes

If the above steps do not resolve the crash, the following issues may be present.

AudioEndpointBuilder crashes only after a specific app is run before hibernate

Some applications that use exclusive audio mode — such as communication apps or games — can leave the audio endpoint in a locked state. Before putting the PC into hibernate, close all applications that use audio. Press Ctrl + Shift + Esc to open Task Manager and end any processes under the Audio category. Then test hibernate wake.

AudioEndpointBuilder crashes on wake with a USB audio device connected

USB audio devices often have their own power management settings. Open Device Manager, expand Universal Serial Bus controllers. Right-click each USB Root Hub entry, select Properties, go to Power Management, and uncheck Allow the computer to turn off this device to save power. Repeat for all USB Root Hub entries. Restart and test.

AudioEndpointBuilder crashes after a Windows Update

A recent Windows Update may have replaced your audio driver with a generic Microsoft driver that does not manage hibernate correctly. Open Device Manager, right-click your audio device, select Properties, go to Driver tab, and note the driver version. Visit the manufacturer’s site and install the driver matching your hardware. After installation, use the Show or hide updates troubleshooter from Microsoft to block the problematic driver update from reinstalling.

Item	Fast Startup Enabled (Default)	Fast Startup Disabled
Description	Uses a partial hibernate file for faster boot	Performs a full cold boot each time
Effect on AudioEndpointBuilder	Driver state may mismatch on wake from hibernate	Driver reinitializes cleanly, reducing crash risk
Boot speed	Faster boot from shutdown	Slower boot from shutdown
Hibernate wake behavior	Can trigger AudioEndpointBuilder crash	Generally stable after hibernate wake

After disabling Fast Startup and applying the driver power management fix, the AudioEndpointBuilder crash on wake from hibernate should stop. Test by putting the PC into hibernate and waking it three times in a row. If the crash persists, run the System File Checker by opening Command Prompt as Administrator and typing sfc /scannow. Corrupted system files can also cause this service to fail. As an advanced step, consider creating a custom Task Scheduler trigger that restarts the Windows Audio service 30 seconds after system resume. This provides a safety net for any residual wake failures.