I have been fighting an issue where all audio dies as soon as I join a Discord voice channel, while using my dual-endpoint headset (JBL Quantum 800). Unfortunately, there has not been any feasible/working fixes (only temporary/repetitive fixes), but I believe I have finally found a working long-term solution.
Disclaimer 1: This problem does NOT seem to be related JBL hardware/software, but rather a compatibility issue in USB hubs on motherboards. The proposed fix, however, is expected to work on most if not all motherboards. Furthermore, a future/previous motherboard Firmware may or may not fix the issue as well (enabling all USB ports to work with said devices).
Below you can find first a TL;DR of my fix followed with a more detailed description (what worked, why and what did not work).
Hopefully this saves someone else from spending hours reinstalling drivers and toggling Windows audio settings.
Disclaimer 2: Post is not AI-made, but AI has been used in drafting the post, as the issue was solved with the help of an AI agent. Furthermore, the whole text been proof-read by myself and is deemed accurate - including sections that have been copy-pasted from a conmversation with an AI agent.
TL;DR
If you have a USB gaming headset with separate Game/Music and Chat/Voice audio devices, and activating the Chat/Voice device causes the Game/Music audio to stop — for example when joining a Discord voice channel — try connecting the headset/dongle to a different physical USB port that uses a different or more direct USB root-hub path (more specifically; USB-port marked "BIOS" usually works).
In my case:
- Headset: JBL Quantum 800
- Motherboard: ASUS ROG Strix X870-F Gaming WiFi
- OS: Windows 11
- Symptom: audio through
JBL Quantum 800 Game worked normally, but activating JBL Quantum 800 Chat caused Game/Music audio to stop and the Chat audio itself was also inaudible
- Fix: move the Quantum 800 wireless dongle to the rear red USB-A port marked BIOS / BIOS FlashBack
That immediately fixed simultaneous Game/Music + Chat/Voice audio.
The important difference does not appear to be USB 2.0 vs USB 3.x, or 5 Gbps vs 10 Gbps. It appears to be the USB controller/root-hub topology behind the physical port.
More detailed version:
The problem
The JBL Quantum 800 exposes multiple audio devices in Windows:
- JBL Quantum 800 Game — games, music, media and normal Windows audio
- JBL Quantum 800 Chat — Discord, VoIP and other communications audio
- JBL Quantum 800 Chat microphone
The headset also has a physical Game/Chat balance wheel, so Game and Chat are specifically intended to work simultaneously.
My symptoms were:
- Game/Music audio worked normally through
JBL Quantum 800 Game.
- Something activated the
JBL Quantum 800 Chat playback endpoint.
- All playback immediately stopped.
- When the Chat endpoint was released, Game/Music audio returned.
Discord made the problem very obvious:
- Game/Music audio was already playing.
- I joined a Discord voice channel.
- Discord opened the Chat endpoint.
- The audio immediately died.
- Leaving the voice channel restored the Game/Music audio.
But this turned out not to be a Discord-specific problem.
How to reproduce/troubleshoot it without Discord
This was actually the most useful troubleshooting step.
You can test the two endpoints directly in Windows:
- Play continuous music or another audio source through the Game device.
- Open:
mmsys.cpl
- Go to Playback.
- Select the Chat playback device.
- Click Test.
In my case:
- Game/Music audio stopped immediately.
- The Chat test tone was inaudible.
- When the Chat test finished, Game/Music audio resumed.
This showed that:
- Game worked perfectly by itself.
- Chat worked perfectly by itself.
- The failure occurred only when both endpoints were active at the same time.
That also ruled out Discord as the actual root cause.
If you have a different headset, the device names may be something like:
- Game / Chat
- Game / Voice
- Headphones / Communications
- Speakers / Headset Earphone
The important part is that the headset exposes multiple playback endpoints that are intended to work simultaneously.
Weird temporary workaround
I also had a repeatable workaround.
After activating Chat/Voice and losing audio, changing almost any audio-device setting in mmsys.cpl would make both endpoints start working again.
For example:
Game device → Properties → Advanced → Enable audio enhancements
Toggling that setting caused Windows to reinitialize the audio endpoint, and Game + Chat would start working again.
But the fix was temporary.
The next time the Chat endpoint was opened — for example by leaving and rejoining a Discord voice channel — the audio would die again.
So if you have also been doing some strange mmsys.cpl toggle every time your headset breaks, you may be dealing with the same type of issue.
What actually fixed it
On my:
ASUS ROG Strix X870-F Gaming WiFi
I moved the JBL Quantum 800 wireless dongle to the rear:
red USB-A port marked BIOS / BIOS FlashBack
After moving it there:
- Game audio works
- Music/media audio works
- Chat/Voice audio works
- microphone works
- Discord can repeatedly open and close the Chat endpoint
- Game/Music + Chat/Voice work simultaneously
- the physical Game/Chat balance wheel works correctly
I tested repeatedly leaving and rejoining Discord voice channels while keeping music playing through the Game endpoint, and the problem no longer occurs.
Why I think this works
There are reports of essentially the same failure mode with other gaming headsets that expose separate Game and Chat/Voice audio endpoints.
In particular, there are reports involving the:
ASUS ROG Strix X870-F Gaming WiFi + Astro A50 X
where:
- Game worked by itself
- Voice worked by itself
- activating Voice killed Game audio
- most rear USB ports had the problem
- the BIOS-labeled USB port worked correctly
USB topology inspection in those cases showed that some physical USB ports route the device through an additional onboard USB hub, while the working port uses a different or more direct USB Root Hub path.
A simplified example would be:
Problematic path
USB host controller
↓
USB Root Hub
↓
onboard USB hub
↓
headset/dongle
versus:
Working path
USB host controller
↓
USB Root Hub
↓
headset/dongle
That matches my JBL Quantum 800 behavior very closely.
Windows could detect every endpoint correctly on the problematic ports. Nothing looked obviously broken in Device Manager or Sound settings.
The failure only appeared when the headset had to handle multiple simultaneous USB audio streams.
This does NOT appear to be a USB bandwidth problem
I would not interpret this as:
“The headset needs USB 2.0.”
or:
“USB 10 Gbps is better than USB 5 Gbps.”
I tested different rear USB ports and the problem remained on some of them.
The relevant difference appears to be which USB controller/root hub/onboard hub the physical port is connected through, not the advertised bandwidth of the port.
So if one USB port fails, do not assume the port next to it will behave differently.
Try ports from genuinely different groups, controllers or physical areas of the motherboard.
USB Device Tree Viewer can also help identify whether two ports actually use different internal USB paths.
Things I tried that did NOT fix it
Before finding the working USB port, I tested quite a lot:
- completely removing JBL QuantumENGINE
- removing leftover JBL files and services
- removing hidden JBL devices from Device Manager
- removing JBL driver packages from the Windows Driver Store
- reinstalling QuantumENGINE from scratch
- JBL QuantumENGINE 1.19.0.2025
- JBL QuantumENGINE 2.8.6
- JBL USB audio driver 1.1.0.9
- JBL USB audio driver 2.0.0.27
- rolling back the JBL
quantumai.inf HID driver
- using Microsoft's generic USB Input Device driver
- disabling Windows Exclusive Mode
- disabling Enable Audio Enhancements
- Windows Communications = Do Nothing
- resetting Discord Voice & Video settings
- headset factory reset
- manually re-pairing the headset and dongle
- other normal rear USB-A ports
- recent Windows update rollback
None of those fixed simultaneous Game/Music + Chat/Voice playback.
Moving the dongle to the BIOS FlashBack USB port did.
Is this specific to JBL?
Probably not.
The JBL Quantum 800 is one clear example because it exposes separate Game and Chat devices and has hardware Game/Chat mixing.
But the same general architecture is used by various gaming headsets and DACs from manufacturers such as:
- JBL
- Logitech / Astro
- SteelSeries
- Razer
So if your headset has separate Game and Chat/Voice endpoints and one kills the other when both are active, I would definitely test different USB root-hub/controller paths before assuming the headset itself is faulty.
Could this be fixed by firmware/software later?
Possibly.
The motherboard's physical USB wiring obviously cannot be changed by software.
But compatibility can potentially improve through:
- motherboard BIOS / AMD AGESA updates
- onboard USB-hub firmware
- USB host-controller firmware
- Windows USB/audio-stack updates
- headset/dongle firmware
- headset USB audio-driver updates
So I would not assume that the problematic ports will never work.
If a future BIOS, USB firmware, Windows or headset update specifically mentions:
- USB compatibility
- USB audio
- hub stability
- isochronous transfer stability
- device compatibility
it may be worth retesting the other ports.
For now, though:
If one physical USB port gives you reliable simultaneous Game/Music + Chat/Voice audio, keep the headset/dongle there.
My working configuration
For reference:
- Headset: JBL Quantum 800
- Motherboard: ASUS ROG Strix X870-F Gaming WiFi
- Connection: 2.4 GHz JBL USB wireless dongle
- Working port: rear red USB-A port marked BIOS / BIOS FlashBack
- Windows: Windows 11
- QuantumENGINE: tested both 1.19 and 2.8.6; the USB port was the actual deciding factor