If you are looking to get rid of it, i will be glad to take it as long as it boots up on 16GB RAM. I can give it to my sister she’s writing a book about our family. She is a retired teacher and her 6 year old toshiba is on its last legs.
@Zidane, @alderonmatt, and any others, my apologies, I was wrong. My very narrow point regarding the existence of notes about 48gb dimms not being fully vetted was correct but irrelevant to the issue at hand. Again, my apologies, and I will try to do better.
You all should hold Framework and AMD accountable to addressing this issue as well as to making you whole, whatever form that might take.
I hope that things get resolved for you and that you are able to enjoy the machine rather than be frustrated by it
Once again, I am sorry, and I will try to do better going forward. This is a great community and I want to help to make it that way, not take away from it.
I hope that you all have great days.
3 Likes
IMHO this issue does need an official response from Framework. Whether this specific issue affects only those with 96GB ram or not doesn’t really matter because Framework is not keeping up with driver updates in their own supported packages. The official driver package from Framework is over a year old (the October Framework bundle graphics driver is the same as from the April bundle and is a non-standard release from between 24.1.1 and 24.2.1) and many new games in the past year aren’t even supported on the old drivers. That is entirely unacceptable for a gaming laptop.
2 Likes
Yeah the worst part about this is framework doesn’t seem to care and I get these horrible responses from mods on the framework discord that it’s not a big deal.
There are new laptops shipping soon and I think ill just leave the ecosystem here. This product is not ready for end user consumption it’s at best a beta unfinished developer product.
Even if we get a response that they are working on it. It’s been over a year how many months and years is this going to take to have game ready drivers.
In framework’s defense, this issue isn’t affecting just framework laptops. It’s an issue with AMD’a drivers across multiple system manufacturers.
Presumably the newer chips shouldn’t have this issue, if AMD made changes to the hardware that caused the issue. Aside from the newer updates, there weren’t really issues that I know of from updating the drivers after installing the framework driver pack.
After all, (as an example) if you have an asus laptop with an nvidia gpu, you wouldn’t point fingers at asus if the nvidia drivers weren’t working across multiple models/manufacturers.
The OEM is on the hook to ship driver updates.
Framework is where we purchased the device from and our support contact for this device.
Newer chips shouldn’t have this issue? Am i going to get a replacement to the new chip for free? What about all the time I wasted on this chip that doesn’t work. Why are we still selling chips that don’t work then.
ASUS, Razer all ship AMD laptops too and those laptops work with the same amount of RAM.
it’s frameworks job to disclose these problems to customers ideally on the store page.
I understand if you disagree, I just wish people held high standards for this type of thing and had a higher bar.
I don’t necessarily disagree, just playing devil’s advocate.
Framework isn’t the only OEM with this issue though, here is an example from AMD’s website: Re: Ryzen 8700G / Radeon 780M driver crash after u... - AMD Community
I didn’t say they weren’t.
I believe the OEM gets the driver updates from the chip manufacturer (AMD), and makes the changes they need before they go in the OEM’s drivers (framework driver pack graphics driver being a modified version of an older one, specific to the framework laptop.)
I agree they should disclose it, for customer awareness.
I’m making that assumption because if they release a new model with a different processor, it should have a different iGPU. The chips do work with the driver provided by Framework, and the laptop works great on the latest version of the Linux graphics drivers. The issue is with AMD’s driver software for windows, which presumably would be provided to Framework by AMD.
I’m not saying framework is perfect, I’m just saying the issue is something AMD would need to look into. If framework has brought it up to them, they can’t really do much as to forcing AMD to fix it.
I previously had 23.40 installed (the driver that came packaged with the 3.05 bios release)
Made the big jump to 25.2.1. Did not have any issues.
My specs are as follows…
Processor: AMD Ryzen 7 7840HS w/ Radeon 780M Graphics 3.80 GHz
Installed RAM: 32.0 GB (31.3 GB usable)
Windows 11 Pro
Version: 24H2
OS build: 26100.3194
Experience: Windows Feature Experience Pack 1000.26100.36.0
Still running 25.1.1; planning to update this weekend when I have more time (in case I have to DDU, reinstall Framework drivers, then 25.1.1 again).
32GB of RAM wasn’t enough for my general usage, and 96GB is still causing driver crashes. Begrudgingly, I have purchased a 64GB kit of RAM, and it is working just fine.
I would still appreciate some communication from Framework about if they have been able to replicate the issue, and if so, what their intended game plan is to address (or even if they have a plan to address) this issue. Even if the issue is AMD’s fault (which I assume it is), Framework is AMD’s customer, and has better means of reaching out to people at AMD who can enact changes vs even a handful of end users.
3 Likes
With less than 64GB there are no Problems with the drivers.
But all in all 25.2.1 is fine for me.
1 Like
I upgraded yesterday to 25.2.1 from 24.12.1 and no issues thus far (other than thermal which everyone has by default):
- Ryzen9 7940HS
- 64GB Kingston Fury DDR5 5600
- 2TB Samsung 990 Pro SSD
- Windows 11 Pro Version: 24H2
- NO dGPU
Another report, upgraded to 25.2.1 successfully.
Heads up for anyone else, I had to do the BIOS iGPU gaming trick as per the BIOS update instructions otherwise I kept booting into a black screen:
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.
- Ryzen 7 7840HS / Raden 780M
- 64GB G.SKILL Ripjaws DDR5 5600MT/s
- Windows 11 Pro Version 24H2
- RX 7700S
I can’t test this because I’m having interposer problems AND lost my FW screwdriver AND this is my sole laptop for college, but I’m not seeing anybody checking for 96GB yet. If I can find a screwdriver that’s compatible and some alcohol wipes then I’ll try it.
The Framework bundle seems to be “old”.
Is there any plan getting it updated?
2 Likes
There is now a 128 GB kit you can buy CT2K64G56C46S5
Sounds like it would have the same problem but i can test it aslong with 96 GB squad.
Ill let you know how it goes.
4 Likes
I found this reddit post from XMG about this issue and they say the fix is expected to come out in March.
We have found that issue may only appear with RAM configurations larger than 32GB (such as 64GB or 96GB).
…
January 30, 2025:
- AMD has sent us a Beta release of a new driver that fixes the issue.
- We can confirm that the driver fixes the issue in our testing on all (multiple) laptop models we tested.
- We are not allowed to release this Beta version to customers or public
- AMD tells us that the release of the solution is scheduled with a public (non-Beta) driver update for March 2025
12 Likes
It was updated today again, looks like it’ll be released March 20th!
5 Likes
That reddit post from XMG is a case study for how companies should handle this kind of issue.
- Acknowledging the issue after receiving reports
- Posting workarounds and mitigations
- Posting regular updates as more information is discovered
I really believe in Framework and I hope they are able to allocate their time and resources to try and deliver a response like XMG did.
6 Likes
Completely agree with this one, wish we had a similar response from framework.
2 Likes
Thanks for the info. I can confirm it doesn’t work for 48GB and 96GB of RAM. I am going to go try it with 32GB or less shortly and see if that works.
On a side note, I started this thread a while back, and I’m glad it’s getting addressed. Not as fast as I had hoped, but at least there is a solution. Not sure if any other big manufacturer (dell, hp, etc) would even care about a solution, so Thanks to Framework, the community, and AMD.