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!?
4 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.
1 Like
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.
3 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.
Update:
I updated to [Adrenalin Edition 24.12.1] Driver for WindowsĀ® 10 & WindowsĀ® 11 64-bit] and followed that with the 24h2 Windows 11 Update. My initial assessment is that the 24.12.1 update has resolved the problems previously experienced with Win11 Pro 24H2 and my WD19S docking station is now working as expected with my FW13 AMD Ryzen 5 7640U.
Fingers crossed - a solution is now in place and working and I hope that it works for others with this issue.
3 Likes
Solved my issue. Thanks for that!
16 days later and disabling the AMD Audio CoProcessor has still worked, however this highlights issues from within Framework of them failing to adjust to updates and there may be another issue that pops up and we canāt fix it.
When will Framework start taking their products seriously? Why build a 16-inch laptop at all if we still canāt get the 13-inch laptop 100%?
1 Like
Thanks for your posts. My browser randomly crashes after the 24H2 update and Iāve lost an entire day of work. Your suggestions worked. Very frustrated at Framework, to say the least. It feels like Iām riding a unicycle.
1 Like
I have chatted with a few reps from Framework on this and they are reaching out the AMD for follow up. Im hopeful they get this worked out and this helps their process for future troubleshooting with AMD.
2 Likes
Wow, thanks to this thread-
I had been avoiding 24H2 because of still reading about people having issues but my computer installed it this morning, and I instantly had problems. The taskbar quick settings (network/sound/battery) icon would just load a blank panel on screen and freeze and there was no way to remove it from the screen without restarting. Other clicks in the task manager would take two clicks (one click on the windows start icon would do nothing and a second click would open it). I hadnāt installed the previous October driver bundle and I tried to do that but it it was getting stuck at step 2. I restarted a few times, and my computer was getting stuck at the login screen (Startingā¦) for way too long. I finally realized that I was able to boot at least with the Thunderbolt dock unplugged, and found this thread. I disabled the AMD audio co-processor, and then was able to finish the latest framework driver bundle install (running as administrator), and then was able to plug in my thunderbolt dock and still have the quick settings taskbar icon load the settings. I also restarted the computer with the dock plugged in and everything came up as expected.
Without this thread, I wouldnāt have known where to start (I have another thread here where I discussed an issue where my microphone inputs would get terrible static pops/crackles on a recurrent basis, and I fixed that by disabling the āAMD High Definition Audio Deviceā and āAMD Streaming Audio Deviceā in device manager, so it seems clear that the AMD audio software provides comes with a lot of strange issues- I wonder what function/value it is supposed to provide?
1 Like
I can confirm this is still a problem. We have 2 framework 13 AMD and a Framework 16. as of the last 2 weeks we have been having a ton of issues with one of our FW13 and have been racking our brains at to what the issues are. 24H2 seems to be the culprit disabling the AMD coprocessor seems to have fixed the issue for us. I did not try updated the Adrenalin software but it is currently installed at 23.40.18.02. I believe this is version from the FW13 driver package. As a business customer these issues and lack of resolutions seriously impact my decisions on weather to continue to deploy FW thought our enterprise. At this time we have paused moving forward with FW and are moving back to Lenovo. I truly believe in the framework mission but from a business stand point we need better support and resolutions. I hope framework can get this figured outā¦soon!
2 Likes
Also just wanted to chime in all of our Framework 16s are experiencing this exactly as John describes in the first post.
1 Like
UPDATE: (I canāt seem to find the edit option for the original post, or I would have added this to the original. )
We have done a bunch of testing across our 4 Framework 16 Laptops. All Units are on the latest BIOS. We have reinstalled all of the most recent driver/firmware pack for the FW16. We even reinstalled Windows 11 on one of the units just to be sure. The issues are still there.
We recently tested individual USB devices independent of the docking stations. By swapping around these devices, we have isolated the issue for us to the USB C camera connected to the dock and not the dock itself. This is consistent with 3 different docking stations models and 3 different USB cameras. We did not test other audio capable devices to see if we could trigger the same problems but Im not that invested in help AMD fix this. But we have this:
- The dock connected to the FW16 with just external monitors did not cause issues. This was the same for USB-C to Display Port connections and USB-C to HDMI connections. I was concerned the HDMI cable might trigger some audio issue on the laptop but it did not.
- The USB cameras connected to the computer through the dock caused the crash symptoms
- The USB cameras connected directly to the computer caused the crash symptoms
Disabling the Audio CoProcessor is still a valid fix if you want to use the external camera. I have opened a new ticket with Framework to update this.
I was in contact with a few account support people at Framework but their responses have gone from slow to almost nonexistent on this recently.
Wanted to add that upgrading to the newest AMD drivers from the AMD website also solves the problem, however it may induce other issues that I do not know of yet. So far, so good.
I spoke with a Framework business representative about this issue, and he reassured me that driver updates are something they are wanting to be better at. This is reassuring, but I guess weāll have to see what actually comes through the pipeline. I stressed to him that we need better driver support, especially as Windows keeps updating and Framework needs to keep up.
With the new AMD laptop being released, I hope that the older version doesnāt get overlooked. I also hope that they keep this new one updated with at least quarterly driver updates.
1 Like
Can you please verify the actual version on these because on all 3 our units this is not correct. We have run the AMD driver updates from their website repeatedly and up until 6 days the issue still occurs for all 3 of the units.
To further add to this, Framework support confirmed in an open ticket that there is no fix for this and that their official recommendation is to uninstall 24H2 and block it from running. This points to the issue being Microsoft and not AMD if the fix is to wait on MS to correct 24H2.
1 Like