Hi Razer team and fellow Insiders,
I'd like to share a detailed finding about a long-standing issue with Razer 7.1 Surround Sound, in the hope it helps the software team fix it.
SYMPTOM
After 6–10 hours of headset use with 7.1 Surround enabled, audio starts crackling and then stops completely on every output. The usual workaround is to repair/restart 7.1 Surround in Synapse.
ROOT CAUSE (what I measured)
The Windows audio engine process (audiodg.exe) keeps accumulating handles until it hits the Windows per-process handle limit (~16.7 million). At that point it can no longer open resources and audio dies.
- Failure #1: audiodg.exe at 16,711,677 handles and 12.4 GB private memory after 12.2 h of uptime
- Failure #2: audiodg.exe at exactly 16,711,677 handles and 12.4 GB private memory after 9.7 h
- Growth rate today: 2.43 million handles after only 1.45 h (~1.6–1.7 million/hour), which reaches the limit in ~10 h
- A healthy audiodg.exe uses ~500 handles and ~17 MB
- Restarting only the Razer surround service/helper does NOT fix it (same audiodg PID keeps the leaked handles)
- Restarting the Windows Audio service (Audiosrv) creates a fresh audiodg.exe (~500 handles) and audio works again, until the count climbs back
WHY I SUSPECT RZSurroundApo.dll
The only third-party Audio Processing Object (APO) loaded into audiodg.exe on my system is:
C:\Windows\System32\RZSurroundApo.dll ("RZ Surround HP APO"), version 10.0.10011.16384, dated 2019-11-11.
It is registered only on the Razer headset endpoint. All other endpoints use Microsoft's default APOs only.
I have not yet run a full control day with 7.1 disabled, so this attribution is strong but not 100% proven.
ENVIRONMENT
- Headset: Razer BlackShark V3 X
- Windows 11 Home 10.0.26100
- Razer Synapse 4.0.823 / Razer Chroma 4.0.823
- 7.1 Surround Sound 1.0.1.21
HOW TO REPRODUCE / VERIFY
1. Enable 7.1 Surround on the headset and use it normally (games, music, calls).
2. Open Task Manager > Details, enable the "Handles" column and watch audiodg.exe.
3. The handle count grows by more than a million per hour while audio plays through 7.1, and audio fails when it approaches ~16.7M.
I have the raw snapshots (before/after each recovery, with PID, handle count, private memory and process start time) and a summary CSV, and I'm happy to share them with the team or run any additional diagnostics you need.
Thanks!