It was a clean install of 24H2. Driver install/update order might have something to do with it, Windows Update updated quite a few after the initial setup.
Resuming from standby also seems to “reset”/change to the 115/100W profile sometimes despite the mode being set to “High Performance”. Switching to Balanced and then back to High Performance does the trick.
I wouldn’t be surprised if some of the benchmarks are a bit off tho.
Indeed and I’m surprised Framework aren’t on this a bit more in terms of reviews.
Pretty sure the Framework Desktop would get 90%+ easy, but not if its defaulting to “laptop” high performance levels. I mean they do want to sell this stuff don’t they 
Lovely for passive cooling but this is cross-platform and most people appear unaware of it.
AMD drivers are presumably the issue.
Indeed. AMD appears to be taking care of the target group that presumably consists of only one person, me.
The GitHub - FlyGoat/RyzenAdj: Adjust power management settings for Ryzen APUs utility supports Linux and Windows and has most of the basic Strix Halo power limits.
Performance mode on the Framework Desktop I believe is:
This is in Watts. You set things in mW, you can safely enter high values as the are BIOS-locked limits (132, 176, 154).
For extra performance, set tuned to use tuned-adm profile accelerator-performance to turn all the performance dials. Set amd_iommu=off for slightly better MBW performance.
With Clear Linux shuttered, CachyOS is probably the easiest way to get optimized packages (core packages compiled with flags optimized for modern CPU architectures), although surprisingly in Phoronix testing on a Framework 13 Ryzen AI 9 HX 370 (Zen5) laptop earlier this year, Debian 13 actually is up there for perf as well: https://www.phoronix.com/review/framework-13-amd-linux-2025/9
i wonder if those bios limits are based on what the VRM is capable of handling or not. Because according to the AMD spec page the cpu has PBO and Curve Optimizer (Voltage Offset) support. I was planning on trying to run core cycler once i get mine to get the per-core voltage offsets tuned to squeeze a bit of extra performance out of the system.
I activated my acount in this community only to thank you for this comment, a couple weeks ago I recived my Framework desktop motherboard, I decided to cut some cost by purchasing only the motherboard and finish the build with parts I already had (SSD/PSU/fan/case). and I last night I got curious about some benchmarks and overall max TDP of my build and if I was thermal throttling my APU or not due to my custom build and 3D printed case. that is how I got here the moment I nottice the 100/115 beheavour and the fact that is was quite far from thermal throttling.
now thank to your comment I was able to unlock the TDP and I’m now having the 160/140 beheavour and zero thermal throttling.
I can’t thank you enough.
Hey there. Just curious which fan you are using? One of the Framework supplied ones and which or another one? Only asking as a data point to define the context under which this behavior is/was occurring.
I know peak and sustained temperatures were discussed. Curious however if what was at the fan spinning at 100% or lower (didn’t see that discussed but I skimmed), and which fan. Since even different Noctua NF-A12x25 fan variants have a different capability for pressure and airflow per RPM.