AMD Adrenalin Update - Airpod Pro 2s Leads to Blue Screen

Hi,

Have the Framework 13 7840u.

I’m keen to use the latest FMF2 on AMD Adrenalin. Since at least 24.8.1 (including 24.9.1 and 24.10.1), each time I try to connect my bluetooth earbuds (AirPod Pro 2s), it leads to an immediate blue screen error, with the error cause being “amdacpbus.sys” or alternatively “amdacpbt.sys”. Currently using Windows 11 24H2, but the issue has been on prior versions.

Reinstalling Framework’s own latest drivers resolves this, but it is obviously an older version and only has FMF1. Happy to continue using Framework’s supported drivers, but would be keen to update the graphics drivers if at all possible

Does anybody have any experience with this error or any idea how to fix it?

Thanks!

1 Like

It’s weird that you see this with an audio product – is the AMD “AI Noise Suppression” thing also being installed when you install Adrenaline? Can you try a minimal installation without it?

K3n.

1 Like

Thanks so much for your advice. Something I’ll definitely try this evening.

To clarify, do you mean using “Minimal Installation” or “Driver only”? And would you remove Adrenalin completely (and if so, what’s the recommended method?), or simply rollback to the Framework (working) version?

I believe AI Noise Supression is installed but not activated when I try to connect the Airpods

Just tried the minimum and driver only installs and it’s the same issue unfortunately!

Hey, I just wanted to chime in here because I had the exact same issue the other day with my Framework 16 7840HS with 7700S when I updated to the latest AMD Adrenalin version. I hadn’t linked the issue to my airpods pro, but I had them connected while I was installing, and then there was an immediate blue screen–same error as yours. Every time I rebooted, it would run for a few seconds after logging in and then blue screen. My airpods were definitely connecting automatically, so it was almost certainly the same cause.

I eventually rolled back to before the install and reinstalled the Framework drivers just to be safe. I don’t know what version of AMD Adrenalin I had before, but it was stable for a long time on whatever version it was.

Oh, I was able to dig up the version from my trash! It was AMD Adrenalin 24.7.1. I might try reinstalling it to see if it actually is still stable. The only reason I updated was because of a bug that was causing the app to consume 10% of my CPU constantly in the background. I think that one was a known bug in the software that happens when it gets confused and can’t find the exe in a partially uninstalled game folder, and it’s fixable, so I might as well just reinstall that version.

Unfortunately, that is the issue with the latest graphics drivers; they may be the latest from AMD though they have not been tested with all the different hardware configurations of so many different vendors. The ones in the Framework driver pack will always be “old” (i.e. stable) though they are the ones that passed the internal testing.

A BSOD is a fairly glaring issue though and likely will be resolved in another subrelease from AMD.

@Karl_Jussila
Yeah I think mine was approximately that time (definitely 24.8.1, but could well be 24.7.1). Frustrating as it would be nice to use the new graphics features, but not a dealbreaker.

@pkunk
I’ve sent maybe 4-5 bug reports to AMD about it over the last few versions, but not received confirmation. I’ve submitted a Framework Support request, primarily to inform the support team that it’s an issue.

Bought an AirFly Pro to allow Bluetooth audio whilst getting those extra frames with the latest driver updates. Not ideal but it works for now.

Exactly the same problem with Adrenalin 24.10.1 and Windows 11 24H2
After installing the driver, my FW16 first runs without any problems, playing Horizon forbidden west for 1 hour, until i connect my Airpods pro 2 and immediately got a bluescreen. After that i‘m not able to restart win11 without getting a bluescreen, directly while or after the login screen.
Rolling back to 24.7.1, is the last driver running problem-free.
So let‘s wait for a solution :upside_down_face: