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.