Device Information
System Model or SKU
BIOS VERSION
04.05
DIY Edition information
DIY edition.
Memory: A-DATA Technology AD5S560032G-SFW — 2 x 32 GB DDR5-5600 (64 GB total)
Storage: Samsung SSD 990 PRO 4TB
Port/Peripheral information
This isn't a port or expansion card issue, so most of this section doesn't apply — but for completeness:
- Peripheral vendor and name: Bose QuietComfort 35 (also reproduced with other Bluetooth audio devices per the linked reports)
- Port the peripheral was connected to: N/A — connected over Bluetooth, not a physical port.
- The component actually involved is the M.2 Wi-Fi/Bluetooth card: a Qualcomm QCNCM865 (FastConnect 7800), installed as an aftermarket replacement for the stock card.
Expansion cards installed (none believed to be involved in this issue):
- USB-C
- DisplayPort
- USB-A
- HDMI
- USB-C
- USB-A
Standalone Operation (Laptop Only)
No — running as a normal laptop, standalone mode not enabled.
Describe the bug
If you install the Qualcomm QCNCM865 (FastConnect 7800) Wi-Fi/Bluetooth card in an AMD Framework Laptop and run Windows 11, Bluetooth audio devices pair and connect normally, appear as a proper A2DP output device, can be selected as the default output — and then play nothing at all. Total silence.
The cause turns out to be AMD's BT Audio Offload path. Disabling AMD BT Audio Device in Device Manager (under Sound, video and game controllers) fixes playback immediately.
The misleading part is that everything looks correct. No error, no yellow triangle in Device Manager, no missing endpoint, nothing useful in Event Viewer. It presents like a headphone fault or a pairing problem, so it sends you down entirely the wrong troubleshooting path — I spent a while chasing driver versions before finding the actual answer buried in user forums.
Why I think this happens: as I understand it, AMD's BT Audio Offload is a platform feature — the audio coprocessor takes the Bluetooth stream directly rather than encoding A2DP on the CPU, to save power. That path is configured for the radio the OEM validated and shipped. Swap in a Qualcomm card and the offload path is still enabled, still expecting a radio that speaks its handoff protocol, and the Qualcomm doesn't. Both drivers are arguably behaving correctly for hardware that isn't present; the stream goes into the offload path and evaporates. Happy to be corrected on the mechanism — that's inferred from the symptoms and the fix, not something I can verify from the outside.
Steps To Reproduce
- Install a Qualcomm QCNCM865 (FastConnect 7800) M.2 card in an AMD Framework Laptop, running Windows 11.
- Pair a Bluetooth audio device (Bose QC35 in my case). Pairing succeeds, no errors.
- Connect it. Windows shows it as connected.
- Open the sound output flyout. The device appears as Headphones (QC35) — note that's the A2DP stereo endpoint, not a Hands-Free/headset endpoint, so Windows has enumerated the right thing.
- Select it. It becomes the active output.
- Play any audio. Silence. The volume meters move; no audio reaches the headphones.
To confirm the cause: Device Manager → Sound, video and game controllers → AMD BT Audio Device → Disable device → reconnect Bluetooth. Audio works instantly.
Expected behavior
Bluetooth audio should play through a connected and selected A2DP output device. Failing that, if the platform's audio offload path can't service the installed radio, it should fall back to software encoding rather than silently swallowing the stream — or at minimum surface an error rather than presenting a fully healthy-looking, completely silent audio endpoint.
Screenshots
(Attach the sound output flyout showing the QC35 selected as the active output, and/or the Device Manager entry for AMD BT Audio Device — or delete this section.)
Operating System
- OS/Distribution: Windows 11 Pro
- Version: 25H2, build 26200.9168
- Qualcomm Bluetooth driver: 3.1.0.1647, dated 21 Jan 2026 (current release at time of writing — this is not a stale-driver problem)
Additional context
Why the workaround isn't a great resting state
Two problems with "just disable it."
It doesn't survive updates. AMD chipset driver packages re-enable the device. So this recurs, months later, with a symptom that gives no hint of its cause. Anyone who hits it a second time gets to rediscover it from scratch.
It appears to trade playback for the microphone. A user on the FW13 with the same card reports:
AMD BT Audio Device disabled = desktop audio works but teams does not. AMD BT Audio Device enabled = Teams audio/mic works but desktop audio does not.
That's the A2DP-vs-HFP split. If it's general, the workaround means toggling a device in Device Manager depending on whether you're listening to music or taking a call.
What I'd like to ask for
A BIOS option to disable BT audio offload at the platform level. This is the main ask. It would be a clean fix rather than a driver-level hack, it would survive AMD chipset updates, and it would cost nothing for people running the stock card — leave it enabled by default and nothing changes for them. It also seems like the correct layer to solve it at, given that the offload path is a platform feature rather than something either driver owns.
Some documentation, even just a line. The QCNCM865 is a popular upgrade in this community and this trips up a meaningful number of people. A note in the Wi-Fi card documentation or the knowledge base — "on AMD systems, disable AMD BT Audio Device in Device Manager if Bluetooth audio is silent" — would save a lot of people a lot of time, regardless of whether the BIOS option ever happens.
Ideally, clarity on the HFP/A2DP tradeoff. If disabling the offload device genuinely breaks the headset mic, that's worth knowing and stating, because it changes the workaround from "fine, done" to "pick one."
Related reports
Not Framework-specific
Worth noting that this isn't just us. The same card, the same symptom and the same fix show up on other AMD laptops:
I mention this not to say "so it's not your problem" but the opposite: it's a consistent, reproducible interaction between an AMD platform feature and a widely-sold third-party card, and Framework is the one vendor whose users routinely swap this card in on purpose. A BIOS toggle here would land better than anywhere else.
Thanks for reading — happy to test a BIOS build or gather more logs if that's useful.
Device Information
System Model or SKU
BIOS VERSION
04.05
DIY Edition information
DIY edition.
Memory: A-DATA Technology AD5S560032G-SFW — 2 x 32 GB DDR5-5600 (64 GB total)
Storage: Samsung SSD 990 PRO 4TB
Port/Peripheral information
This isn't a port or expansion card issue, so most of this section doesn't apply — but for completeness:
Expansion cards installed (none believed to be involved in this issue):
Standalone Operation (Laptop Only)
No — running as a normal laptop, standalone mode not enabled.
Describe the bug
If you install the Qualcomm QCNCM865 (FastConnect 7800) Wi-Fi/Bluetooth card in an AMD Framework Laptop and run Windows 11, Bluetooth audio devices pair and connect normally, appear as a proper A2DP output device, can be selected as the default output — and then play nothing at all. Total silence.
The cause turns out to be AMD's BT Audio Offload path. Disabling AMD BT Audio Device in Device Manager (under Sound, video and game controllers) fixes playback immediately.
The misleading part is that everything looks correct. No error, no yellow triangle in Device Manager, no missing endpoint, nothing useful in Event Viewer. It presents like a headphone fault or a pairing problem, so it sends you down entirely the wrong troubleshooting path — I spent a while chasing driver versions before finding the actual answer buried in user forums.
Why I think this happens: as I understand it, AMD's BT Audio Offload is a platform feature — the audio coprocessor takes the Bluetooth stream directly rather than encoding A2DP on the CPU, to save power. That path is configured for the radio the OEM validated and shipped. Swap in a Qualcomm card and the offload path is still enabled, still expecting a radio that speaks its handoff protocol, and the Qualcomm doesn't. Both drivers are arguably behaving correctly for hardware that isn't present; the stream goes into the offload path and evaporates. Happy to be corrected on the mechanism — that's inferred from the symptoms and the fix, not something I can verify from the outside.
Steps To Reproduce
To confirm the cause: Device Manager → Sound, video and game controllers → AMD BT Audio Device → Disable device → reconnect Bluetooth. Audio works instantly.
Expected behavior
Bluetooth audio should play through a connected and selected A2DP output device. Failing that, if the platform's audio offload path can't service the installed radio, it should fall back to software encoding rather than silently swallowing the stream — or at minimum surface an error rather than presenting a fully healthy-looking, completely silent audio endpoint.
Screenshots
(Attach the sound output flyout showing the QC35 selected as the active output, and/or the Device Manager entry for AMD BT Audio Device — or delete this section.)
Operating System
Additional context
Why the workaround isn't a great resting state
Two problems with "just disable it."
It doesn't survive updates. AMD chipset driver packages re-enable the device. So this recurs, months later, with a symptom that gives no hint of its cause. Anyone who hits it a second time gets to rediscover it from scratch.
It appears to trade playback for the microphone. A user on the FW13 with the same card reports:
That's the A2DP-vs-HFP split. If it's general, the workaround means toggling a device in Device Manager depending on whether you're listening to music or taking a call.
What I'd like to ask for
A BIOS option to disable BT audio offload at the platform level. This is the main ask. It would be a clean fix rather than a driver-level hack, it would survive AMD chipset updates, and it would cost nothing for people running the stock card — leave it enabled by default and nothing changes for them. It also seems like the correct layer to solve it at, given that the offload path is a platform feature rather than something either driver owns.
Some documentation, even just a line. The QCNCM865 is a popular upgrade in this community and this trips up a meaningful number of people. A note in the Wi-Fi card documentation or the knowledge base — "on AMD systems, disable AMD BT Audio Device in Device Manager if Bluetooth audio is silent" — would save a lot of people a lot of time, regardless of whether the BIOS option ever happens.
Ideally, clarity on the HFP/A2DP tradeoff. If disabling the offload device genuinely breaks the headset mic, that's worth knowing and stating, because it changes the workaround from "fine, done" to "pick one."
Related reports
Not Framework-specific
Worth noting that this isn't just us. The same card, the same symptom and the same fix show up on other AMD laptops:
I mention this not to say "so it's not your problem" but the opposite: it's a consistent, reproducible interaction between an AMD platform feature and a widely-sold third-party card, and Framework is the one vendor whose users routinely swap this card in on purpose. A BIOS toggle here would land better than anywhere else.
Thanks for reading — happy to test a BIOS build or gather more logs if that's useful.