FRWK16 - AMD Software: Adrenalin Edition 24.9.1 - ISSUES

I also rolled back to the GPU driver from the Framework driver bundle on my Windows 11 23H2 install.

In 24.8.1, the GPU driver crashed every 2-3 minutes during video playback, coincident with this message in the event log:

Display driver amduw23g stopped responding and has successfully recovered.

In 24.9.1, the GPU driver failed to start at all. The system fell back to the generic unaccelerated display driver. In Device Manager, the GPU device’s status description was something like “The device is disabled because its driver failed to start”. System shutdown hung, requiring a hold-the-power-button turnoff.

Rant: Generally, I ignore vendor-supplied drivers because they almost always are old, contain unwanted bloatware, or have baked-in choices I don’t like. Framework so far seems better than most, but even there, I prefer to install each driver manually rather than running Framework’s installer. I do that so that I can install AMD GPU drivers in “driver only” mode and with telemetry disabled.

1 Like

In case you didn’t already know: if you use a third-party zip unlocker (I use 7-Zip installed via Ninite), you can use it to “unzip” the Framework Driver bundle, and it will result with a folder containing each of the separate driver installers included in the driver bundle.

4 Likes

As drivers are for both FW13 & 16 (I have 13) i can also confirm major issues with newest Adrenalin SW.

I had Adrenalin installed as well. However, the newest update also breaks my system

Gets stuck when /not shutting down (trying to reboot(ing) / black screen and my cpu fan goes crazy.

After forced shutdown the restart takes long and I’m getting serveral AMD error messages pointing to driver update failure. Only uninstalling amddriveruninstaller fixes all issues but replaces graphics driver with standard Microsoft and multimedia driver non-functional.

2 Likes

I initially assumed that the issue was with the relatively uncommonly used RX7700S dGPU used in the Framework 16 (and an Asus?), but it’s looking increasingly clear that the software issues are more serious for the iGPU than the dGPU. I’m curious if there’s any strong commonalities between the systems that are having issues vs the ones that seem to be relatively problem-free.

I am running

  • Windows 11 Pro (64-bit) 23H2
  • 96GB RAM
  • 2 SSDs
  • 7940HS (w/ 780M iGPU)
  • RX7700S dGPU
  • Stable 3.03 “BIOS”

And, as stated above, I have been unable to update to 24.9.1 without the system crashing to a black screen, and the system fan ramping to 100%.

My 2c: I reinstalled my drivers back from 24.9.1 to the latest Framework-supplied drivers after 24.9.1 broke Helldivers 2 for me. I didn’t have any other problems, but the game would crash pretty much as soon as I stepped out of the hellpod. That’s been my go-to for time wasting lately, so it was enough to make me roll back. Unfortunately, the latest Framework-supplied drivers are from before Helldivers even launched, so they come with their own set of bugs. Just not game-crashing ones.

I, too, would love to see some more frequent validated driver updates. 24.8.1 worked fine for me. And why do I have to go hunting for the latest BIOS, too? When I google “Framework 16 drivers” the top hit is the official drivers page and that still says 3.03. I would have had no clue 3.05 existed if not for this thread.

I have looked far and wide and haven’t found a firmware update for 3.05 for the Framework 16. I have seen a beta firmware update for 3.04 for the Framework 16 from July, but it was still in beta due to issues that were found. There is a 3.05 stable firmware for the AMD Framework 13 that was linked above, but it explicitly says:

Please note that this software is for Framework Laptop 13 (AMD Ryzen™ 7040 Series) ONLY!

For other Framework Laptops, please read the article located HERE.

The forum thread for the beta 3.04 firmware for the Framework hasn’t had any official Framework posts since July 31, except for @Destroya, on August 22, linking to a previous post, acknowledging that Framework was aware of (and tracking) the issues plaguing the update.

1 Like

3.03 is the current version, we had 3.04 as a beta release. Driver package is updated last week (so that it can work with Windows 24H2).

1 Like

Why not roll back to v24.8.1? As far as I’m aware, you can install any version freely on top of any other one.

1 Like

The release of new bios and new drivers proves terrible For a gaming laptop, bios at the level of 500-600 euros, some kind of fraud…

1 Like

The Blackscreen Issue was already at the AFMF2 Beta Driver, that it still persist is pretty sad.

1 Like

Just download 24.10.1 from AMD drivers support website. After couple of hours of using my machine no issues to report yet. I picked the clean install option and drivers only option.

https://www.amd.com/en/support/download/drivers.html

Had you previously installed 24.9.1 and had issues, like many of us?

Did you skip 24.9.1?

Or were you a lucky one, who successfully installed 24.9.1 without issue?

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