On this page I see in a table:
BIOS 3.06 Updated
But only 3.05 is shown as download. How does this work? What do I not understand here?
We move this version to stable today. You can get it from the knowledgebase.
Framework Laptop 16 BIOS and Driver Releases
2 Likes
@Quin_Chou the link you provided still shows 3.05 in the TOP SECTION… i had to search the page for 3.06 and it was just a text box … no download.
Did i misunderstand? or i’m blind?
As I understand, this update is just the driver bunde. Not the uefi bios update. But the 3.06 is mentioned in the text box.
Is it the same as the first post? If i’m already on this version no need to download and reinstall right?
Correct.
The download page is a bit confusing. I had installed the beta release earlier, and it upgraded my graphics driver to 24.20.60.01, which is also what the top post says. However, the knowledgebase page here says it’d “upgrade” the driver to 23.40.18.02. Is this an error?
I also have the same question about the BIOS version, how the page mentions 3.06 but only 3.05 is available to download.
1 Like
My system specs: 7840HS, 7700S, 2TB P41 NVMe, 2x16GB Crucial 5600MHz.
I installed the beta v2.04 drivers from here on the forums, when they were first announced. When I tried them, I ran into some issues with game stability and AMD Smartshift, so I rolled back to the original drivers and waited for the stable release. Later, Framework pushed the driver bundle to stable, and I wasn’t sure if anything changed so I tried again and got the same issues. Another user in the thread said they weren’t experiencing the issues I was, so I wondered if it was just my system and decided to do a full reinstall of Windows 11. I did last night, and I tried the latest driver bundle again… and got the same issues as before. Someone else in the drivers thread said they were not experiencing the issues I described, so at this point I’m not sure if I should be submitting bug reports or a support ticket. I figured I’d ask the community to find out if it’s just me.
Issue 1: AMD SmartShift issues switching from battery/AC power
I’m having some difficulty pinning down exactly what the cause is with this one, but I think it occurs whenever I start the laptop on battery, then plug into AC power (using the included 180w brick and original cables), then try to run something that would require a MUX switch, like a game. The game runs poorly or not at all, I don’t get that 2-second hitch that tells me the MUX engaged properly, and AMD SmartShift reports 100% CPU bias (see photo below). This persists even when the game is closed and doesn’t fix until I restart the computer.
Issue 2: Helldivers 2 crashes
(Disclaimer: I have no idea how many other games this may or may not affect. I really just want to play Helldivers. 
) Issue is simple: I can’t get through a single round without crashes on these drivers. The original drivers were stable, aside from not being able to use the AMD FPS overlay, but on these I can barely get 10 minutes of playtime before the game freezes, then closes, but Steam still thinks the game is running, so I have to force-stop the still-running .exe in the task manager and restart my computer to get everything back to normal. Time spent on the destroyer doesn’t seem to count, it’s only when I drop in that the crash happens.
Keep in mind, both of these issues are happening on a fresh install of Windows 11, and they were happening before my fresh install, too. Has anyone else experienced these issues or similar? I think I’m going to roll back to the original drivers (again) for the time being.
1 Like
I had crashes and MUX problems as well, make sure to DDU the old drivers before upgrading. Solved the issue for me.
Glory to Super Earth! 
For those unaware, DDU is a reference to Display Driver Uninstaller, which is in-practice more thorough than simply uninstalling the driver:
Display Driver Uninstaller (DDU) download latest version 18.1.1.0 | Wagnardsoft
1 Like
Thanks for the replies @TheLPeink @TechPriestNhyk . I did try DDU before my Win11 reinstall and it didn’t help. I also just tried it again on the fresh install; no dice. Am I really the only one having problems with this driver bundle? In addition to the above I also get all manner of weird hangs and glitches.
1 Like
The version is the same. Just move it from beta to stable.
1 Like
We apologize for the error. The correct version is 24.20.60.01, and I have notified the internal team to make the necessary corrections.
1 Like
Thank you @TechPriestNhyk for explaining DDU. I had no idea what this ment and thought it was something in the FW driver bundle or in the AMD software provided in the FW bundle. Cheers, mate!
1 Like
Weird behavior I noticed with these drivers:
Before, with the Framework driver bundle, AMD GPU drivers would not update to the latest release and stay at the version supplied by Framework. Now, even after a DDU uninstall and installing this driver bundle, the AMD software updates automatically to the latest 25.3.1 version (I think there’s an optional 25.3.2 so I guess technically the latest recommended version). I’m guessing that’s not intentional, but I’m still not sure how FW’s custom AMD drivers are different than the general drivers available from AMD.
1 Like
Ran the driver update and BSOD mid way through.
Brilliant.
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
IMAGE_NAME: dxgmms2.sys
This driver update was the last nail in the coffin for using the dGPU on 140W chargers for me. It used to work in previous versions (could not hit the full 100W target obviously), but now any game launched with a 140W charger attached crashes the driver. Works wonders on 180W though. We need the power management fix ASAP! (bios 3.06 maybe?)
Same behaviour here. I think it’s related to having AMD Install Manager installed?
and its removed amd adrenalin.
just going to go back to the amd drivers, was easier.
Did you ever got this fixed?
I had to roll back to an older version since I got the same problem after upgrading, I did DDU before after reading this thread.