• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

The AMD Driver Thread

Using 26.6.3 with Win 10 currently. 26.6.2 was a complete fail for me

Might give 26.6.4 a try later today if I get time.
Cheers, I'm very much in the "if it's not broke, leave it alone" camp for drivers... the ones I'm running are probably well over a year old (shortly after they added FMF), but will have to give these a try... crossing my fingers it doesn't break everything for the few games I do play currently!
 
Last edited:
Further to previous - I cannot find any trace of Ryzen Master - may be a hangover from time I considered using it?

Overall as it is not , so far as I can tell, causing any issues will not lose any sleep on the error code that came up;)
 
@AMD_Vik - I'm still seeing some weird installation issues with these drivers. 26.6.2 installed with no problems even through the AMD Install Manager. I remembered to kill FanControl first and the screen flickered for a couple of seconds on installation of the new driver.

However 26.6.3 and 26.6.4 both took a lot longer (30-40 seconds of black screen) to install the new drivers, caused a LiveKernalFault (Windows 11 did not like having the driver rug-pulled from under it), killed FanControl, and on the next reboot the "settings -> system" windows in the Adrenalin control panel was just a black, blank window. In the end, a full reset installation of Adrenalin while saving the previous settings was needed to bring back the blank window.

I'm guessing the fix for installation problems on Windows 10 with 26.6.2 created some reversion for installation on my Windows 11 PC with 26.6.3 & 26.6.4. I have logged a bug report, but I don't know if it's something you want to chase up. My PC is a relatively new (six months old) all 9800X3D/9700XT AMD system, all up to date with BIOS, drivers and Win 11.
 
:( booo!

... @AMD_Vik - is this one on the radar? (and I'm having that issue with 26.6.4 as well btw!)
I need a bit more context. Does it crash on launch or during gameplay? If the latter, is there anything specific causing this in-game?
@AMD_Vik - I'm still seeing some weird installation issues with these drivers. 26.6.2 installed with no problems even through the AMD Install Manager. I remembered to kill FanControl first and the screen flickered for a couple of seconds on installation of the new driver.

However 26.6.3 and 26.6.4 both took a lot longer (30-40 seconds of black screen) to install the new drivers, caused a LiveKernalFault (Windows 11 did not like having the driver rug-pulled from under it), killed FanControl, and on the next reboot the "settings -> system" windows in the Adrenalin control panel was just a black, blank window. In the end, a full reset installation of Adrenalin while saving the previous settings was needed to bring back the blank window.

I'm guessing the fix for installation problems on Windows 10 with 26.6.2 created some reversion for installation on my Windows 11 PC with 26.6.3 & 26.6.4. I have logged a bug report, but I don't know if it's something you want to chase up. My PC is a relatively new (six months old) all 9800X3D/9700XT AMD system, all up to date with BIOS, drivers and Win 11.
My colleagues and I are tracking a whole bunch of install related problems. Seems there's a lot of areas where this falls over, and I'm not sure why this got so bad lately.
The next time you hit an install issue, try sending me your setupapi.dev.log from C:\Windows\INF\ and we'll take a look through.
 
Last edited:
I need a bit more context. Does it crash on launch or during gameplay? If the latter, is there anything specific causing this in-game?
Hi Vik, it launches ok, but crashes pretty consistently after some time playing (20-30 minutes at a guess).
Not linked to any specific activity or location as far as I can tell.
What I quoted before was from their patch notes ('the weekly grind') - I haven't tried any other troubleshooting yet (borderless window, disabling overlays etc.), but assume as it's listed that they would have tested those as workarounds.... although 'just use old drivers' seems to be their solution to most issues :D

I had seen one post yesterday (which I can't find again now) suggesting it's possibly a memory leak, I haven't validated whether there is any noticeable accumulation of RAM/VRAM usage but can try to do that later if it would help.
Running W10 22H2 (I think on the June update - 19045.7417).

If there's any other troubleshooting steps I can take or more info I can provide, let me know, I should have time to test for a bit this evening.

Thanks for your help!
 
@AMD_Vik - I'm still seeing some weird installation issues with these drivers. 26.6.2 installed with no problems even through the AMD Install Manager. I remembered to kill FanControl first and the screen flickered for a couple of seconds on installation of the new driver.

However 26.6.3 and 26.6.4 both took a lot longer (30-40 seconds of black screen) to install the new drivers, caused a LiveKernalFault (Windows 11 did not like having the driver rug-pulled from under it), killed FanControl, and on the next reboot the "settings -> system" windows in the Adrenalin control panel was just a black, blank window. In the end, a full reset installation of Adrenalin while saving the previous settings was needed to bring back the blank window.

I'm guessing the fix for installation problems on Windows 10 with 26.6.2 created some reversion for installation on my Windows 11 PC with 26.6.3 & 26.6.4. I have logged a bug report, but I don't know if it's something you want to chase up. My PC is a relatively new (six months old) all 9800X3D/9700XT AMD system, all up to date with BIOS, drivers and Win 11.
Don't forget to give Windows a quick check just in case it is a localised issue causing your recent headache. So by that i mean SFC and DISM checks. :)
 
Hi Vik, it launches ok, but crashes pretty consistently after some time playing (20-30 minutes at a guess).
Not linked to any specific activity or location as far as I can tell.
What I quoted before was from their patch notes ('the weekly grind') - I haven't tried any other troubleshooting yet (borderless window, disabling overlays etc.), but assume as it's listed that they would have tested those as workarounds.... although 'just use old drivers' seems to be their solution to most issues :D

I had seen one post yesterday (which I can't find again now) suggesting it's possibly a memory leak, I haven't validated whether there is any noticeable accumulation of RAM/VRAM usage but can try to do that later if it would help.
Running W10 22H2 (I think on the June update - 19045.7417).

If there's any other troubleshooting steps I can take or more info I can provide, let me know, I should have time to test for a bit this evening.

Thanks for your help!
I see. i'll ask QA if they have the game in their library / to get it if not and check in with it.
 
I see. i'll ask QA if they have the game in their library / to get it if not and check in with it.
Little update - Played some more earlier and took longer to crash but did eventually, then went on again and it eventually BSOD, rather than crash to desktop.
RAM and VRAM usage was fairly high, but not at maximum and the graph looked fairly flat when it crashed.
Windows version is correct as above.
Can't find a minidump file for the BSOD, but can look in to whether I need to enable that (thought it was on by default), assuming I can re-create the BSOD.
Both crashes were in fairly different parts of the map (one in Market Mile and one in Gullcrest), but both where while I was doing missions.
Didn't try any variations of fullscreen or overlays yet
 
Little update - Played some more earlier and took longer to crash but did eventually, then went on again and it eventually BSOD, rather than crash to desktop.
RAM and VRAM usage was fairly high, but not at maximum and the graph looked fairly flat when it crashed.
Windows version is correct as above.
Can't find a minidump file for the BSOD, but can look in to whether I need to enable that (thought it was on by default), assuming I can re-create the BSOD.
Both crashes were in fairly different parts of the map (one in Market Mile and one in Gullcrest), but both where while I was doing missions.
Didn't try any variations of fullscreen or overlays yet
Grab windbg from Microsoft Store if you do get a mini dump file. Should help analyse it.
 
Grab windbg from Microsoft Store if you do get a mini dump file. Should help analyse it.
Eww... MS Store!
(I've always just used Nirsoft BlueScreenView :P )

Edit: but if it offers more functionality, I'll grab it with PS/winget...
Just checked and minidumps are enabled, but none was created (nor does the folder exist)
 
Last edited:
Eww... MS Store!
(I've always just used Nirsoft BlueScreenView :P )

Edit: but if it offers more functionality, I'll grab it with PS/winget...
Just checked and minidumps are enabled, but none was created (nor does the folder exist)
Hah. I have used Blue screen view as well yeah. Spot on lol
 
Had some crashes this evening. No issues with heat on the CPU or GPU, the SSD was toasty at the sensor 2.
Ran a CPU stress test and no issues then ran the stress test on AMD adrenaline with the same undervolt settings that have been applied for a while now and got a green screen then restart, it's -25mv, mem on fast timing and power limit on -1. Went back in and put the tuning to default and ran the stress test again and got a black screen and restart. Temps seem ok, nothing over 80, even on the hotspot and GPU memory. All drivers are upto date and have nothing running in the background as it's just a gaming pc.
Anyone else have any similar issues with the latest drivers?
 
Last edited:
Had some crashes this evening. No issues with heat on the CPU or GPU, the SSD was toasty at the sensor 2.
Ran a CPU stress test and no issues then ran the stress test on AMD adrenaline with the same undervolt settings that have been applied for a while now and got a green screen then restart, it's -25mv, mem on fast timing and power limit on -1. Went back in and put the tuning to default and ran the stress test again and got a black screen and restart. Temps seem ok, nothing over 80, even on the hotspot and GPU memory. All drivers are upto date and have nothing running in the background as it's just a gaming pc.
Anyone else have any similar issues with the latest drivers?
I updated yesterday to latest - all good here. I couldn't help noticing though in your sig your PSU. Taken from manufacturer website:

Recommended power supply for AMD Radeon RX 7900 GRE graphics card is minimum 800W or greater power supply with 12V output > 62A.

Could your 650w be the problem here? It can spike over 350w. As you say, everything checks out temp wise and even at default settings the stress test caused a black screen and restart. The PSU only has 54A rail as well.
 
Last edited:
I updated yesterday to latest - all good here. I couldn't help noticing though in your sig your PSU. Taken from manufacturer website:

Recommended power supply for AMD Radeon RX 7900 GRE graphics card is minimum 800W or greater power supply with 12V output > 62A.

Could your 650w be the problem here? It can spike over 350w. As you say, everything checks out temp wise and even at default settings the stress test caused a black screen and restart. The PSU only has 54A rail as well.
Think AMD says 750w Tech Power Up suggests a 600w PSU... Seems a bit on the low side TBH would guess a decent 700w would probably be ok but 600w... but they are usually pretty good I think... But guessing this is where I get a ton of comments telling me the TPU GPU database sucks lol
 
I updated yesterday to latest - all good here. I couldn't help noticing though in your sig your PSU. Taken from manufacturer website:

Recommended power supply for AMD Radeon RX 7900 GRE graphics card is minimum 800W or greater power supply with 12V output > 62A.

Could your 650w be the problem here? It can spike over 350w. As you say, everything checks out temp wise and even at default settings the stress test caused a black screen and restart. The PSU only has 54A rail as well.
Maybe I was a bit to over confident with the PSU and should have upgraded earlier.
I was intending to pick up a Lian Li SP 850 in August but I might have to bring this forward.

I kept the 650 and went through all the PSU calculator website, Reddit, OcUK forum and based my choice to keep it as they said different values and requirements. I didn't however double check the 12v rail amps on the actual PSU. Lesson learned, check the manufacturers site only next time lol.

I do have a Corsair RM750e 2023 I think, will check it tonight and if it have the amps then I may move it over as a stop gap for now until I can pick up the Lian Li.
 
Think AMD says 750w Tech Power Up suggests a 600w PSU... Seems a bit on the low side TBH would guess a decent 700w would probably be ok but 600w... but they are usually pretty good I think... But guessing this is where I get a ton of comments telling me the TPU GPU database sucks lol
Try the PSU calculator sites, they are random. Some say 650w and others are calling 1000w.
 
Its the power spikes that the psu can handle during heavy gaming is generally what to watch for. Not just the max wattage rating.
 
Last edited:
Back
Top Bottom