Framework Laptop 13 - 12th Gen Intel Core BIOS 3.19 Release STABLE

Framework Laptop 13
,
21

Not a forum warrior. Yeah all the bios threads are full of people clamoring for a fix…yeah that is what I would call maybe two dozen entries with no real data on how to reproduce. No driver lists, no OS details, no application lists and application details, no kernel versions, no configurations…no logs, nothing anyone would actually need to explore and resolve it.

From my experience I added thermald to the mix to apply the default dptf profiles and it never happened again. Hence the user, in this case me, applied the correct thermal profile apparently and it never happened again. So based on my experience and others I have helped with a variety of issue including this one, it was a user based issue and not a hardware based issue.

3 Likes
22

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.

image
image1207×939 66.8 KB

23

hm, well … imho Framework should make the contact and ask for the specific information they need including the way how to retrive it (because there are many not so tech savy ppl out there).

We all are consumers and not their technicians, well … at least as long as they don’t pay me I’ll stick to my role in this game.

I’ve found a workaround I’m more or less (more less) ok with and my solution is to not buy one again.

1 Like
24

No they haven’t. BIOS updates, yes. Fix it, no.

Maybe you don’t get it because you bought the cheap one?

No I don’t.

You assume I haven’t spent days of my life getting the runaround from Frameworks’s awful support. You assume this isn’t the second board I have that has this problem.

Why are you spending so much energy to defend your favorite widdle tech company?

FW dropped the ball. This generation was a disaster and they refuse to do anything about it.

25

I didn’t assume anything because you never actually said anything that was helpful and still haven’t.

I’m not defending anyone. Simply asked you for information that would be helpful - not just for you or me but for anyone who came across this.

But hey, since you’ve decided to be insulting, sort it out yourself.

2 Likes
26

For those that are reading this and having the 400MHz issue here’s a couple of things that may or may not help:

  1. Make sure, when running Windows at least, is to make sure you run the Windows retimer updates AFTER doing the BIOS update.
  2. You may want to also try updating the firmware of your SSD, so if you’re running a WD SDD like I am this is what I did to update the firmware of the SSD: Western Digital Drive Update Guide Without Windows/WD Dashboard - #62 by Vikram
1 Like
28

Never claimed to be anything especially “Framework Jesus”.

And I “chimed in” because that’s the literal point of a community forum. People trying to help each other with issues.

Suggestions may or may not work and that’s fine.

And there’s no denying you are having issues that, from what you’ve said, you’ve clearly laid out to Framework the exact steps you’ve taken to replicate/reproduce the issue.

Should Framework work with you to resolve it ? Yes. Absolutely.

Is it okay to try solutions/workarounds that have been put up by others in this thread and in other threads until Framework resolves it? Yes. Of course. It’s your choice.

But, for whatever reason, you’ve decided to take the road where if anyone tries to help by asking simple questions you’re going to respond with horrible attitude. Fine. Your choice. You clearly don’t want anyone’s help and just purely want to vent. Fine.

Just don’t expect anyone to help you if you’re going to be insulting.

3 Likes
29

I will try the latest BIOS again but also change the thermal paste. I haven’t done so since I got the laptop. Maybe that has something to do with it. From my previous report, I could see the CPU spike at 100°C when the 400 MHz bug happened so I will try to reproduce it with new thermal paste.

30

Hello,

I just updated my firmware from 3.06 to 3.19. I used the EFI method on a USB key plugged into my Firewire 4 dock (the dock itself being plugged into the front right port of my computer). I think that everything went OK.

Before the process, both charging LEDs behave the same : orange when charging, white when battery was charged.

During the update process, I had both charging LEDs solid green, and later in the update process, they both flashed green.

Now that the firmware is updated to 3.19, I have a strange behaviour : the left charging LED behaves like with firmware 3.06 (orange = charging ; white = charged), but the right charging LED shows new colors : red when charging, pink when battery is charged.

What does this mean ? How do I fix this ?

Thanks !

Cobus.

31

If this helps, here are the green “COMPLETE” page informations I had after the update :

Mainboard Hadware
Type: Laptop (12th Gen Intel Core)
Revision: MassProduction
UEFI BIOS
Version: 03.19
Release Date: 09/18/2025
EC Firmware
Build version: hx30_c0.0.1-a3deac9 2025-09-01 14:53:16 runner@pkrvmccyg1gnepe
Current image: R0
PD Controllers
Right (01): 0.1.2E (MainFw)
Left (23): 0.1.2E (MainFw)
Retimers
Left: 0x136 (310)
Right: 0x136 (310)

32

So @Quin_Chou @nrp ?

That’s it? Crickets? Tumbleweed? Flat out ignoring our requests now?

Is it EOL? Are you still dedicating any resources to it?

The last official comment on the issue was “we can’t reproduce it (therefore it doesn’t exist), just change your thermal paste”

That didn’t work.

Pretending it’s not an issue doesn’t make it go away.

33

I’m going to be sending them soon a 12th gen motherboard that has issue (2nd rma for this) hopefully this time they solve it for others. I’m not going to try intel ever again

1 Like
34

AMD has suffered from a similar issue

Under Fixed Issues, you’ll note that they fixed the CPU locking to .55Ghz.

Plus other driver issues. Pick your poison.

35

Oh yeah I know for sure. It just seems that framework and amd in general are much more focused on fixing such issues on the amd side of the story.

Also support will get sick of me if I will have such issues that can’t be fixed

1 Like
36

@Quin_Chou @nrp

Untitled
Untitled1438×978 78.4 KB

This thing is useless to me if I can’t export a video and not have it spend more time at 400mhz than not.

When is the recall happening?

37

I can almost guarantee there will be no recall. There wasn’t for the 11th gen RTC issue so I see no reason why Framework would change their ways here.

38

Well, clearly not, but RTC battery at least had a path out that you could do yourself.

But if I can keep this thread bumped and expose their awful handling of this issue and ward off even a single customer from giving FW any money, then i’ll be satisfied :slight_smile:

39

I know it’s a workaround and not a resolution but have you tried using the Intel Extreme Overclocking Utility to tweak some settings as mentioned by @mahe on this post: Framework Laptop 13 - 12th Gen Intel Core BIOS 3.19 Release STABLE - #20 by mahe

Maybe @mahe could share what settings they tweaked?

40

I think I posted it somewhere around here. However, I know it’s nearly impossible to find and I’m pretty sure I’ve changed some settings since posting it the last time.

So here are my current settings:

Turbo Boost Short Power Max Enable: Enable (Default: Enable)
Turbo Boost Short Power Max: 50 W (Default: 60 W)
Turbo Boost Power Max: 20 W (Default: 28 W)
Turbo Boost Power Time Window: 64 Seconds (Default: 28 Seconds)

Edit:
The reason I set the PL1 Time (Turbo Boost Power Time Window) that high (compared to before) is, because I run a few VMs at the same time (2-3 Windows Server 2025, 1-2 Windows 11).
With this settings the high boosts are shorter and a little lower (because PL1 Time is longer and PL1 Limit a little bit lower), which helps the CPU staying a little bit “cooler”.

1 Like
41

Thanks for sharing those settings. Hope it helps others experiencing the same issue to at least workaround it for now.

@Quin_Chou maybe you and the @Framework team can look into this using the information from @mahe post above to determine what’s going for those experiencing the 400Mhz issue?