I can confirm that 25.3.1 works on my Framework 13 7840 with 96GB of RAM, BIOS 3.07. Chipset driver update was also successful.
I am on Gaming mode, which in this case translates to 8GB of RAM allocated.
I don’t do hybernation though, for I am machine.
Steven, thank you! I was able to get it working on my FRWK16 with 48GB of RAM and 96GB of RAM. I installed it in auto GPU mode using one stick of RAM, and everything works without any black screens. I installed the second stick after the fact, and everything is working as others have reported.
Most importantly, for my use case running Solidworks 2024 (note that it mentions 2020 because I upgraded from an older version), the dGPU mux position switches correctly when in laptop mode (using only the laptop display), as shown below.
LAPTOP MODE (ONLY USING LAPTOP DISPLAY)
I’m not entirely sure why the mux position doesn’t change when I connect a 4K display to the back of the 7700S, as shown below. However, the performance indicates that the 3D rendering is being handled by the correct dedicated GPU. Perhaps this is just a software glitch?
DGPU CONNECTED DIRECTLY TO 4K MONITOR
When I use my OWC Thunderbolt Pro Dock with 4K and 1080P monitors connected to the upper right USB4 port, the mux position shows APU. However, the performance indicates that the 3D render is utilizing the correct dGPU. This might be just a software glitch.
USB4 PORT TO OWC PRO DOCK TO 4K/1080P MONITORS
It works well in this configuration.
The next issue to address is rendering with SolidWorks Visualize. This software does not work with the Adrenaline package. In the past, I was able to get it working by installing an older version of the AMD PRO software, but this process came with many challenges and less-than-optimal performance. I will retest this situation and report my findings.
In the future, it would be fantastic to have the ability to install either package or for the Adrenaline versions to be compatible with AMD PRO Render technology.
I have always preferred AMD graphics in SolidWorks over NVIDIA, as they have consistently performed better for me. In the past, NVIDIA would often create graphical imperfections while I was designing. However, with newer drivers, the latest version of SolidWorks (2021 and onward), and advancements in GPUs, these issues are less noticeable with NVIDIA cards, provided the hardware isn’t outdated. Currently, I am using my RZR16-4090 to render all of my projects.
It’s also possible that these issues stem from the limitations of SolidWorks Visualize. Perhaps SolidWorks could explore ways to utilize the NPU, CPU, and DGPU, maximizing the capabilities of FRAMEWORK platforms for development, gaming, and workstations alike, especially with the upcoming FRWK DESKTOP on the horizon.
I almost forgot that my main request is to be able to select the dedicated GPU (dGPU) in the BIOS. This change would alleviate many of the issues I’m facing. However, with the introduction of USB4, I’m unsure if this is still possible. From my previous experience with Dell and my Razer 16 (intel based), I know that it is possible to switch the dGPU.
Hey everyone, just wanted to drop in and say I finally beat you all to it 
Today is 5/8/25 and I successfully updated to the latest AMD driver:
whql-amd-software-adrenalin-edition-25.5.1-win10-win11-may8-rdna.exe
So far no issues at all. No black screens. No installer bugs. Just smooth sailing.
I’m running 96GB of RAM and my GPU MUX is set to Gaming. SolidWorks 2024 SP5 is running great too with no graphical weirdness or crashes.
Kinda surprised nobody’s replied to this thread yet besides the two people who favorited it — maybe everyone’s waiting to see who flinches first? Well consider this your green light.
Happy to report it’s working for me 
Let me know if anyone else gives it a try!
-CMAX
Since 25.2.1 the Drivers worked flawlessly for me, i told i here.
The Main Culprit for most, was that with RAM Configs more than 32GB and the Vram Setting for the iGPU not at Gaming.
That caused the black/white Screening with thos Driver Generations.
I also installed the AMD 25.2.1 (drivers only). Also happy to report no issues encountered thus far.
FW16 Ryzen 9 7940HS
64 Gb(2×32) Kingston Fury DDR5 5600
4TB Samsung 9100 Pro SSD
Windows 11 Pro 24H2
I don’t have the dGPU
This is really encouraging - thanks so much for the feedback; gonna go update now 
Installed the newest AMD driver (as I always do) v25.5.1 and it works without any problems so far.
Same, 25.1.1 and no bother after I did a clean install of the driver as the last FW driver pack caused an issue with one of the DX sys files.
At this point I just keep using the AMD supplied GPU and Chipset drivers and pick the other driver updates out of the FW package as needed. Seems to be more reliable than the FW package.
Just circling back in because… looks like I beat everyone to this again
On 6/10/25, I installed the latest WHQL driver:
whql-amd-software-adrenalin-edition-25.6.1-win10-win11-june5-rdna.exe
(First appeared on AMD’s site on 6/5/25)
Everything installed cleanly. No black screens. No failed attempts. No funny business.
System Details:
This time, I noticed something new: the AMD Install Manager also handled:
No tweaking or workarounds needed. Just click and go.
Here are some screenshots showing the install and Adrenalin UI after reboot:
Hopefully this helps someone else hit update with confidence.
Let me know if anyone else tests it. So far so good
Hey my friend,
Could you tell me your install order method for a clean install? I am curious on what as successful for you.
Thanks,
CMAX
When I updated to 24H2 with 25.5.1 installed everything was fine except the laptop was blackscreening when waking up from Hibernate. Do you use Hibernate? If so, was yours working fine?
Mine has been blackscreening when coming back from hibernate (or the hybrid hibernate/power off) since the most recent “BIOS” update (that conveniently also fixed a security bug and therefore can’t be downgraded). I saw someone that linked to the issue in the GitHub bug tracker, but haven’t seen any motion on it since. Admittedly, I don’t check it very often even though it’s extremely frustrating.
I installed the video driver from the latest official Framework 16 driver bundle and this fixed the wakeup from Hibernate for me, just FYI
The chipset driver is the same, so you can get them from wherever.
@PSierra117
I do not know if the 24.20.60.01 (latest from framework) fixed the RAM issue or not. I have 32GB of memory, and I had not ran into any issues with either gaming or not-gaming.
This is known behavior.
- Some users have reported display issues after the update which are resolved by reinstalling the AMD GPU drivers. Please note that there is also a known issue we have duplicated when running AMD drivers 24.10.xx with windows 24H2 with 64GB or more of RAM. The display may be blank/white after booting. This will require downgrading the AMD graphics driver, or downgrading to windows 23H2 until this issue is resolved.
Github issue
Some users report reinstalling the graphics driver may fix this. In addition you may want to adjust the bios option Advanced->GPU memory to gaming to see if this can change the behavior of the system.
Well unfortunately the framework driver has proved to be less reliable than the amd oficial.
And tbh I’ve not seen any major issue by running the amd driver. In fact it’s fixed some issues running the 7700S.
The white screen at boot issue is a simple fix of changing the igou mode in the bios iirc. Unfortunately framework resets this on a bios update but it’s a simple fix.
If framework could keep up with amd official and the fixes that provides id probably be more included to run it but it’s always seriously behind.
So far the Framework one has proved to be more reliable for me. The official AMD one cannot hibernate, in addition to the sleep crashing, and a few times I was getting graphical glitches.
Though the software itself from Framework can sometimes just quit, oddly.
It would be desirable for them to have at least quarterly updates on this, yeah. But there is a reason Framework tell you to use the official stuff – is because there are customized bits.
I can confirm that both 25.6.1 and 25.6.2 have the same issue as 25.5.1 when waking Windows 11 24H2 from Hibernate - black screen with some corrupted pixels. So I went back to the Framework official driver.
is that just for hibernate? tbf i only use sleep
I don’t care about the customizations. I have only problems with the FW drivers, not with the official ones.
And if the device doesn’t work with official drivers, I will throw it away as it’s crap.
Never ever I will buy a device that won’t work with OEM drivers.
I don’t use sleep on the other hand because in the last years I’ve lost all trust in it in Windows - my laptops were always waking up when you don’t want them to - in the bag, plugged in on the desk.
Great if Sleep’s working for you, but since I got used to the longer delay of waking from hibernate, I don’t feel the need to go back.
Next time I try AMD driver, I’ll check how it behaves waking up from sleep.
