Except in your previous post you said:
And yet now you’re saying
>apply load to processor
>thermal throttles.
SImple.
So you see why I’m asking what you did to produce this behaviour?
If you read the links to the threads I posted in my previous post you can see that Framework have acknowledged this as happening and have done BIOS updates to fix it.
If the BIOS updates haven’t fixed it for you then it is important you can clearly define the steps you took with your Framework laptop to produce the issue.
There’s other information, too, that can help such as whether it’s on battery or plugged in to power, if plugged into power what charger are you using, your CPU, your RAM, etc etc.
In fact the first post in this thread I linked to previously Framework Laptop 13 Intel 12th Gen: Stuck on 400 MHz or not? not only has a “Yes/No” poll about the issue but also has an “If Yes” and “If No” poll, too, collect further information as I mentioned.
My Framework laptop - Windows 11 Pro 24H2, i5-1240P, 16GB RAM, 1TB SSD, two USB C (Aluminium) expansion cards (one the left and the right closest to the hinge), two USB A expansion cards (one of the left and right in the remaining two spots) - having fully discharged (I had left it on at the BIOS screen and it to had discharged) then plugged, while it was still off, plugged in to charge using the supplied Framework 60W power adapter and left to fully charge.
Right now, having turned it on and using Chrome with Task Manager and Windows Update running in the background for just over 30 minutes now while still plugged into the power adapter and on hard surface (table), everything is running fine. Clearly, I’m not running my laptop the same way you are.
As @nadb said in the post above mine - data is needed in order to reproduce the issue.
It could well be, as they and @mahe have said (and has actually been mentioned in other threads on this issue), that you need to use a utility to tweak settings/thermal profile for your situation (which you should detail in order for Framework to actually fix it and log a support ticket as well) until Framework is able to have a clearer understanding of what is causing it and how to resolve it.
