FRWK16 - AMD Software: Adrenalin Edition 24.9.1 - ISSUES

Yes, I went from 24.9.1 → 24.10.1. Only issue I had with the previous version was while switching monitors using a USB-C hub the monitor would go black and i would have to power cycle the monitor. With 24.10.1 that issues seems to be resolved. I have been switching screens all day without any problems.

  • Machine Framework 16
  • Win 11 Pro (64-bit) 23H2
  • Kingston FURY Impact 64GB 5600 DDR5 CL40
  • Samsung 990 Pro SSD
  • Ryzen™ 9 7940HS
  • BIOS version 3.03
1 Like

24.10.1 didn’t work for me. Same issue as 24.9.1 which was a black screen and driver crash on install and forced reboot/boot.

Tried with and without game mode.

1 Like

Sorry I dont have FW system, but I was in the same problem on 780M system with 24.9.1 and 24.10.1 drivers. I was able to found the culprit, it won’t install on 96GB system. With single stick 48GB it runs well (tried with both sticks). And 2x 32GB also runs well. Please let me know if this can solve your problem.

Also for those who got problem with 96GB ram, what brand/model of your ram? In my case it’s crucial ddr5 5600 sodimm. Since it’s the only brand/model 48GB available in my country, I can’t check on other brand.
Sorry for the bad english

2 Likes

Same. No possible Way to use 24.9 or 24.10. If i leave the 780m deactivated it works fine with the 7700s alone. But the 780m is not working with the Driver.

until the next restart. The Laptop Screen stays white and nothing. Had to revert to 24.8.1 again.

1 Like

Interesting, as I have 96GB in my machine. They are crucial CT48G56C46S5 (if I’ve transcribed that properly). I do have the original DDR modules that were shipped with it, but I don;t really want to go back, given this is probably a SW bug.

Interestingly I had to reinstall a 9950x based system yesterday and using the iGPU on that to get the system up and running had issues with the 24.10.1 with display corruption and that’s a 128GB machine. I wonder if AMD just haven’t tested with these larger memory configs.

Next question is how to get them to fix this

1 Like

I have the same memory.

I submitted a bug report through (24.8.1) Adrenalin. Second from the bottom option in the included screenshot.

Screenshot of AMD Adrenalin

Hopefully enough bug reports will result in a fix.

Edit: Though if a partner, like Framework, also reported it to AMD, it may get eyes on it sooner; especially now that Framework is selling 96GB kits themselves. @Destroya or @nrp

1 Like

I have had the same issues installing 24.9.1 on my Framework 16 and I only have 64GB of RAM. I am sticking with 24.7.1 until this issue is fixed.

For me, 24.10.1 fixed the problem.

1 Like

what brand/model is your ram?

https://www.amazon.com/Kingston-Impact-2x32GB-Comsumption-KF556S40IBK2-64/dp/B0BRTJT5P2

Am affected by this as well (at least with 2024.10.1, hadn’t tested 9.1). Had to fallback to 8.1.

Crucial (2x48GB) 5600 CT2K48G56C46S5

I am using this and no issues with 24.10.1
Kingston FURY Impact 64GB (2x32GB) 5600MT/s DDR5 CL40 Laptop Memory Kit of 2 | Lower Power Comsumption | Intel XMP 3.0 | Plug N Play | KF556S40IBK2-64

This is the one that seems like working best for me with 24.10.1
Kingston FURY Impact 64GB (2x32GB) 5600MT/s DDR5 CL40 Laptop Memory Kit of 2 | Lower Power Comsumption | Intel XMP 3.0 | Plug N Play | KF556S40IBK2-64

Same Problem here. 96GB Crucial ram. Bug report submitted to AMD.

Dude the Ram has nothing to do with the Driver not working. I am on the same 64 Gb Kingston Kit ad you and its not working.

I think the thing that would have more impact is what cpu everyone is using and if the drivers are able to work. 24.9.1 did not work with my 7940hs, and I likely wont try 24.10.1 until either framework updates the graphics drivers or it is known stable on the 7940hs. For what its worth I am running the cl40 gskill 64gb kit.

I also have the 7940HS CPU. UPDATE: 24.10.1 still has the same issue. Do not install!

3 Likes

Has there been any acknowledgement of this issue by the Framework team?

Discussion here is about the driver package that you get directly from AMD, bypassing Framework’s supplied drivers. Thusly, Framework would probably just say this is unsupported scenario.

1 Like

Ultimately the drivers would need to be updated at some point regardless by Framework for their driver pack, unsupported or not the issue would need to be addressed.