This absolutely feels like a damaged slot. Please open a ticket if you have not already.
1 Like
I’ve started experiencing the same thing over the past few months but on my 13th gen intel. I’ve tried updating to the latest beta BIOS 3.06 and still have the same problem. I’ve raised a support ticket. Fingers crossed it can be fixed.
1 Like
After debugging with support it seems to be solved but I don’t know which step solved it, it was one of combination of:
- Disconnecting the battery, running in standalone, then reconnecting it
- Dismantling the fan/heatsink and cleaning it (it wasn’t very dusty)
- Resetting the mainboard (see instructions below)
It’s been happily running as expected for nearly a week without issue.
Mainboard reset:
- Plug in system to AC
- Remove input cover
- Press the chassis open switch in the center of the mainboard 10 times, you must press it slows, so press for 2 seconds. Release, wait for the red blink on the Mainboard LEDs, and repeat.
See the photo below for reference:
- Press the power button to boot the system.
- BIOS settings will be reset to defaults.
The issue started again a few weeks ago, framework support have now told me to go buy a new mainboard because it’s out of warranty which is a complete joke I’ve been having issues with this thing in one form or another since I got it. So much for framework’s mission to prevent e-waste now this thing will end up on the scrap heap and be replaced with a thinkpad.
I also have had this problem come back recently. It is weird because it oscillates between long periods of 400mhz and then sometimes wakes up and becomes snappy again. It is incredibly annoying.
Hi, for what it is worth I had something similar on my 13th gen - have a check of the fans and cooling tunnels, and possibly the thermal paste on the CPU.
Do you have a specific workload that triggers the 400mhz behavior?
No, it was nothing special or distinctive in the workload. My devices all run Ubuntu 24.04 so are reasonably lean once they’ve started up but it really didn’t take a lot for it to throttle and the fans going full pelt.
The issue in my case was simply that the fans and cooling vent were blocked causing it to throttle back with a very very low threshold.
I had the issue in both my Framework 13 and the Mobo I run as my desktop in a Coolermaster case with the Coolermaster case being the worst at clogging up. Both these are running Intel 13th gen (the laptop a 1340p, the desktop a 1370p) with 64GB RAM and either a 500GB or 2TB NVMe drive so most of the time neither is exactly stressed out with memory management.
For me it was caused due to thermal.
I was experiencing this issue occasionally in the past but recently it became every day struggle to the point that it made every day work a challenge.
I started checking temps and noticed that it ran quite hot most of the time ~80c but never over 90c.
I cleaned the fan and applied new thermal paste I haven’t had the issue since.
1 Like
Bumping this, as I also have the issue on Core Ultra 125H.
It was capping out at 77˚C. After taking out the battery for a while and plugging it back in, it could suddenly go to 90. But it caps out there.
I’m really hoping to get it to reach 95. These chips are supposed to work up to 110. It’s very disappointing that the BIOS settings prevent the chip from getting the advertised performance.
As a reference, the CPU score on Intel Core Ultra 5 125H Benchmark is supposed to be over 20K. I was getting 9K before the BIOS reset and am only getting 16K now.
If anyone would like to share their results, It’d be welcome.