This was interesting. I had the same issue and was about to reinstall my system finding this.
so hope there will be an update soon. but it worked fine for me aswell to disable AMD Audio CoProcessor
1 Like
I donāt see the AMD Audio Coprocessor in my devices on my FW13, but disabling the AMD HD Audio Device and AMD USB Audio Device had no discernible ill effects and appears to have resolved the issue. This is on Win11 24H2.
My problems were twofold: Crashes with some USB docks (Dell WD19 and WD19S - not all devices in the model range as we have about 40 of those docks, and not all of our 15 Frameworks had the problem), and crashes with external webcams.
As both the docks and the webcams have audio devices of some sort, I assume that this is the source of the problem. It only occurs when those devices are actively polled, however, such as attempting to switch to the camera in question on a Teams call, or manage the cameras in the Windows settings.
After disabling both it appears to be rock steady. I am also on the 3.06 Beta BIOS right now after a suggestion from support, but I donāt think thatās related - Iām going to test that myself following this post on one of our other devices. I also fed this back up to FW Support, so hopefully this issue will get some attention.
We have 2 FW13ās with 7640U and 7840U and a FW16 with 7840HS, all of them currently experiencing described problems. Initially we started having problems maybe a month ago with the 7640U not working with our conference room Logi Docks. I didnāt check the update version but ended up doing several clean installs to the system doing troubleshooting, after which it most certainly was 24H2. Rest of the laptops worked well until calendar week 51, when both got updated to 24H2 and now none of them work.
The issues are identical to the first post, with audio playback or trying to use microphone or camera just freezing the computers, after which nothing works. Iāve been in contact with Framework support regarding the laptop with 7640U, they were very responsive but unable to solve the problem back then. They replaced the motherboard 3 weeks ago after quite a lot of troubleshooting but that unfortunately didnāt solve the issue, as in hindsight seems obvious. They also asked at that point to try booting the system with web camera module unplugged in case of hardware incompatibility, but that didnāt help either. Windows safe mode was worse than normal, but Ubuntu worked without problems.
Thanks to this thread, I got at least temporary solution. I didnāt have a AMD Audio Co-Processor, but for my FW13, disabling AMD USB Audio Device from Sound, video and game controllers helped. I forwarded this thread to FW support. Hope this gets solved soon.
1 Like
I canāt believe the support didnāt know about this thread!?
3 Likes
Same for me. I couldnāt get my Logitech C922 Webcam to workā¦only the built-in one would. Once I disabled the AMD Audio Coprocessor, my external webcam started working! 
I experienced the issues described here after installing 24h2 on my FW13 w/ Ryzen 5 7640U connected via Anker PowerExpand 12-in-1 TB4 dock to Logitech Brio and LG display, among other things.
I installed AMDās drivers using the installer provided here:
https://www.amd.com/en/support/download/drivers.html
Things appear to be improved. On initial reboot I received USB device errors for my webcam, but an additional reboot while connected to my USB-C dock appears to have solved that.
Iāll report back if things take a turn.
Just chiming in that after loading the latest AMD Adrenalin from Matts link above, seems to have resolved my issues with docking stations and Logitech webcams. I have reenabled the AMD Audio coprocessor and so far have not seen any issues. This is AMD Adrenalin 24.12.1
Disabling the AMD Audio CoProcessor in Device Manager worked for me too. Itās found under āSystem Devicesā.
We need to get a better direction from Framework. I manage IT for a business with 12 Framework 13 AMD laptops and this 24H2 update is causing all sorts of issues with the AMD drivers. Are we supposed to get drivers straight from AMD? Are we supposed to wait for Framework to approve AMD drivers for us? We need to know how to manage this because I want to support Framework, I love the product, but I canāt run an experimental program with these laptops for them to stop working.
2 Likes
Good to hear your feedback. We are running a pilot for our org and Iām in the same boat. I have 125 users on other laptops and Iād like to move to framework. I would say Iām a little more concerned about AMD then I am Framework on this one, but I do have some concerns.
We have 3 AMD Framework 16s and 3 Intel Framework 13s. No issue on the Intel units. I realize there is no Intel option for the 16s.