AMD CPU stuck in low-speed state after system resume

[RokeJulianLockhart]

@Kevin_Fleming, does that mean that this is a separate problem to: ^{[1] [2]}

Framework 16 stuck at 0.55 Ghz after windows sleep mode

Framework just released a new beta firmware update that seems to address this very issue. “Fixed the issue where the CPU was stuck at 545MHz after the system resumed from sleep.”

Clock stuck at .39Ghz

My DIY edition running Win10 is getting stuck clocked at .39Ghz. This happens even when plugged in. After a reboot it runs at full speed for a minute or two, then reverts to .39Ghz. [image] I’m following the instructions on this thread and this did not fix it.

…or does 0.0.3.7 merely not remediate it? It states that it should:

I ask because I’m attempting to diagnose:

Last update, DBus was so hammered that I could barely do anything

…which I may have misattributed, if the fault was the CPU clock speed.

Unfortunately, because I have been unable to locate an authoritative GitHub issue, IDK how this was discovered, nor what the remediation is.

---

1. reddit.com/r/framework/comments/19d5zey/comment/kj54pc0 ↩︎

2. reddit.com/r/framework/comments/13ehs1t/comment/jjpw6e8 ↩︎