For me, installing Radeon software version 25.2.1 with drivers fixed this at least temporarily. I think Windows update may override the drivers, so disabling driver updates from Windows should help.
1 Like
We have 18 Framework 13s, so I can only state that running the latest auto-detect update apparently works. I currently am running a Framework 13 on 24H2 with the AMD 24.12.1 driver and that seems to be fine as well. Iâll run the latest update and will report if it causes problems.
In my opinion, Framework and AMD need to get together with another Framework-approved driver update that solves this, I donât think itâs on Microsoft to fix this problem, unless AMD wants to battle it out with Microsoft.
1 Like
Same issue here, all the same symptoms, all easily replicable on AMD Frameworks, 13 or 16.
Intel mainboard, or running Linux on AMD hardware has no problem at all.
Thank you for sharing the workaround â Iâll give that a try. Otherwise, waiting with baited breath on a resolution, this issue is pretty much holding us off on adopting larger use of Frameworks.
1 Like
We updated 2 of the active devices to 25.3.1 using the AMD download and not the Framework bundle.
First shot it worked and seemed to be running smooth. Overnight both devices went to sleep and had issues waking up correctly. We had to hard reboot one and the other one I had to disconnect everything and reconnect the USB devices and it worked again.
So⌠better I guess but still a little cumbersome. Certainly not âfixedâ.
I would echo what the previous poster said. Framework needs to update its driver pack and connect with AMD on this. I know they pointed fingers at MicrosoftâŚbut each new iteration of AMDs drivers seems to get closer to addressing this. We also have stopped ordering 16s for production because the AMD issue just isnât viable for a normal business user if they have to fuss with the setup every day.
Following up on my upgrade to 25.3.1 on the Framework 13 7640U, it has been smooth and havenât had any issues. It actually fixed some issues from my previous version (24.12.1). Framework just released a new BIOS version as well (v3.07), so that shows some promise that theyâll continue support. Still waiting on that new Framework-vetted AMD driver bundle, itâs been 6 months now since our last update. It would be nice to have some transparency with this.
Overall, I still appreciate Framework and what they are trying to accomplish, especially with the new announcements. I just hope they donât run too fast before theyâre balanced.
We have had mixed results still on the FW 16âs. The issue is much better than it was at the start of this thread, but we have random issues with docking stations and peripherals still. Disconnecting from a Dock causes the system to hang trying to access the camera that used to be attached via the dock. Needing to hard reboot after undocking and even occasional monitor connection issues.
As a team our company has decided against using the FW 16 in production. Itâs too unreliable for what we need for our remote workforce and would undoubtedly create more problems than itâs worth. I still donât know who shoulder more of the blame on this, AMD directly or Framework. I still use the 16 myself because I love the larger screen and I can handle the quirks, but I couldnât expect a business user to feel comfortable needing to force reboot often.
We are still using the FW 13 with the Intel chipset and have pushed those out to our team. We have around 15 of them is use with no issues at all with our docking habits. This is why I feel like the issue is something that AMD is failing to adequately address.
1 Like
I installed 24H2 in July for both my FW13 and FW16. On my FW16 Iâve had constant freezes when connected to a Pluggable TBT4UDZ. Seems very much like the USB issues from early on in the x570 days. Maybe it is a firmware issue? The AEGSA version does seem quite a bit behind, at least compared to desktop.
Also, Iâve had this pluggable dock since June 2024, before I bought the FW16. The 2.5Gbs ethernet only works at 600Mbps at best with both laptops. When I raised this issue with pluggable, they said its the firmware and there was not much they can do, but they would love to work with Framework directly on the issue.
When I emailed support, I included the email chain from pluggable. I pretty much got boiler plate âDid you turn it off and on againâ and âReset the BIOSâ responses.
As an update on our Framework 13s, they have been pretty solid with recent Windows updates and the continuing updates from Framework. We are pretty pleased with the progress Framework has made and are continuing to buy more Frameworks. Current issues that plague us are excessive fan noise, some minor docking station issues (sometimes power doesnât connect or other random issues), along with little quirks here and there. If Framework can continue to adjust their power and fan curves, continue their support of devices and docks, we would be extremely pleased.