In my experience it made this particular bug much much worse. Look at my post in the 3.06 thread. For me, it would do it even more, for example when steam was rebuilding shaders, or at the launch of any game (very slow game startup).
But give it a try for yourself and report back. I am curious if others have the same issues I had. So far, I have not seen very many report these issues.
I have not seen the 545MHz issue with 3.06 or 3.07. I also have not seen the 1000-1400MHz issue with 3.06 or 3.07 on Windows 11. However, I have a freeze and reboot issue that I can easily trigger by launching pretty much any game after my 16 has resumed from sleep. Windows 11’s system logs only record an improper shutdown, and the behavior seems like power supply instability. After the restart, games launch and run just fine.
Additionally, I’m not sure what has been fixed in 3.06 and 3.07, but my minimum framerates have improved, making gaming on my 16 much more pleasant. Could also be a coincidence with a windows update.
Does anyone know if the following change from version 3.06 made it into this version (3.07)?
Fixed CPU power limits to prevent unnecessary limitation when the GPU is in BOCO mode.
It won’t be changed in 3.07. It will be in the 4.00, which we target to release for Framework Laptop 16 Ryzen 7040 + GN22 BIOS support. We are doing the validation, so it will be released soon.
Will this 4.0 version contain the keyboard sleep update as well? And the new firmware for the keyboard?
If I’m already running the 3.07 Beta, can/should I still upgrade to the stable version?
Bios update went through from 3.05 on my FW16.
It took a little longer on first boot, probably checking RAM again, but then no problems so far 
I’m curious as well. 3.07 beta was awful and had very bad throttling issues. I haven’t seen any notes from Framework on how they fixed those issues for stable.
Can anyone provide more info?
it has not been fixed. it looks like it there will be release bios 4.00 in 1 or 2 weeks should fix this issue. see comments above
I don’t understand how they can mark it as stable with an issue that huge still being a problem.
No, no! It’s stable, but with issues! 
I’m hoping all these things being addressed carry over to the AI 300 series boards and I am not starting from scratch when I make the swap. It would only make sense everything still applies as the only difference is the cpu. But what do I know, I might be in for another wild ride.
I know how you feel. One of the big reasons that I stuck with my first generation mainboard and GPU is that I am very well aware of the outstanding problems and limitations of the first generation platform. My experiences with dealing with (or ignoring in certain cases) the the first generation hardware and firmware defects has me questioning the quality of the “launch day” second generation hardware.
Framework is very determined to discourage any further sales on the FW16 platform.
That was not necessary. I bet you never programmed something at the BIOS level or machine languate or similar, or you wouldn’t talk like that.
I did. And I do. And I would be out of a job if I would ignore bugs for a year.
Neither has Framework….apparently. 
Triage is a thing, and despite how much slips through I assume there is a pretty long tail of testing and qualification you can’t just easily squeeze something in.
I definitely wish they’d focus a lot more resources on polishing the low level firmware stuff.
That may be a little harsh, lenovo, dell and hp probably got orders of magnitude bigger teams working on their firmware and when have they ever given us more than 2 pd ports?
Triage means prioritizing more important issues, while knowingly accepting the consequences.
They decided to build framework desktop instead of polishing the FW16. The upside is Framework desktop sales.
The downside is a disgrunteled customers who will loudly advise against buying anything from framework until they have shown that they care about their released products in a timely manner.
Same…
