Since some people are mentioning it, my BIOS was already set to Gaming VRAM for the integrated GPU. Still can’t upgrade to 24.12.1
I can confirm that installing anything higher than 24.8.1 will not work for me. My BIOS is 3.05 and memory is set to gaming. I have tested this with and without dGPU.
My specs are as follows…
Processor: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics 4.00 GHz
Installed RAM: 96.0 GB (87.8 GB usable)
Windows 11 Pro
Version: 24H2
OS build: 26100.2605
Experience: Windows Feature Experience Pack 1000.26100.36.0
2 Likes
Can confirm 24.12.1 (upgrade from 24.8.1) is working on my FW16. My setup:
- 64GB RAM (in Gaming mode)
- Windows 11 24H2 (all possible updates installed before upgrading
- Bios 3.05 (installed first)
- Windows in performance mode with 240Watt charger (probably makes no difference)
- iGPU and dGPU
Has survived several reboots with no black screen.
I can also confirm that Gaming mode in the BIOS, took my 780M from 2GB to 8GB of memory, but only after the upgrade from 24.8.1
1 Like
So odd one that I’ve not noticed before. It looks like the Mux no longer switches from the iGPU to the dGPU. Now I’ll be honest and say that I’ve been neglecting gaming on the FW16, so this could have been true for a while. But I swear it used to work pre upgrade, or at leaston the FW provided drivers.
Anyone experiencing this?
I can force use of the dGPU in Windows settings (nothing in Adrenaline) but this seems clunky.
Same, still can’t get nothing over 24.8.1 work.
7840HS, tried with and without the RX 7700S Expansion module, Crucial 96GB, tried on 23H2 with and without DDU, also tried on fresh install of W11 24H2, tried fresh direct install from nothing to 24H2 and also updating from 24.8.1
3.05 BIOS and also in Gaming mode because some people seemed to had more luck with that option.
Tried while using the Framework’s 180W charger
1 Like
I’m also stuck on 24.8.1 with 96 gigs of RAM. And 96 is not a supported configuration, so might not be fixed ever if they took care of the same issues for people with 64 gigs.
It’s probably some part of code not being able to handle the amount of free RAM over some amount, so I hope they’ll deal with it once 64 GiB SODIMM modules come out 
1 Like
I can confirm it must be related to that, I just tried removing one of the two 48GiB SODIMMs and I could install 24.12.1 without any issue, as soon is I popped back the other 48GiB stick, black screen and failing driver.
So there is absolutely a problem with high RAM capacities, I’m not sure if the driver or the BIOS is to blame, certainly it worked before, whatever the driver made, it is not acknowledged yet in known issues and surely they know by now, so I would assume that the drivers did something that shouldn’t create this issue or they aren’t publicly acknowledging the issue (and with they I’m referring to AMD here).
The 3.05 BIOS just made the gaming mode use 8GiB of RAM as VRAM for the iGPU instead of 4GiB, which was barely enough to workaround the issue on 64GiB of RAM, but that solution is not viable for 96GiB of RAM unless one is okay to conceding like 40GiB of the RAM to the iGPU.
I don’t know who to blame, but what bothers me is that the issue is like 4 months old by now.
I hope a proper fix is given early next year, specially considering 96GiB IS a supported configuration (although not initially), 96GiB of RAM is a option at the time of purchase for their DDR5 laptops thanks to the recently added 96GiB Framework branded sticks
3 Likes
I remember someone from Framework mentioning here that it’s one of AMD’s known issues, when it was affecting people with 64 GiB of RAM. Pity is that the issue was fixed for users of 64 GiB, so they had it on their agenda, and now they probably don’t anymore. Since they don’t really support two 48 GiB sticks of RAM, it was always a possibility that something like this will happen. As I said, I hope, the issue comes back into focus once higher-capacity DIMMs are sold, because my conjecture is that they both would want to support 128 GiB of RAM and that the issue we’re experiencing will reappear once they try to do so.
Well Framework supports 96Gb Ram as they sell the Framework 16 with up to 2x48GB RAM.
2 Likes
Good point!
This sounds like a AMD problem more that a FW problem.
Even the Linux AMD gpu drivers a getting pretty flakey in recent 6.12.x kernels.
I think there software quality is not great at the moment. I think they are breaking more than they fix. Similarly for ROCMBLAS. Their non-happy path error handling is really sloppy.
1 Like
I was experiencing increasingly often random software crashes and swapped back to 32GB RAM (from 96GB) as a troubleshooting/diagnostic step. Around the same time , I saw an optional release of AMD Adrenalin 25.1.1. I can confirm that for me, it installed and ran without issue at 32GB, but upon swapping back to 96GB, it crashed/failed to boot.
1 Like
This GitHub issue might be worth following: Laptop 13 Ryzen 7840 - GPU not recognized in windows after updating to 3.06 · Issue #11 · FrameworkComputer/SoftwareFirmwareIssueTracker · GitHub
How are you forcing the dGPU to always be in use? I haven’t been able to find any option to do so globally
Also having this on Framework 13 and 16 in the 96 GB of RAM club.
Pretty awful quality control on AMDs side, its affecting other devices other then framework.
For something reported in Oct 2024 or earlier its certainly taking its time on the fix.