Download: AMD Radeon Adrenalin Edition 19.7.5 drivers

Published by

Click here to post a comment for Download: AMD Radeon Adrenalin Edition 19.7.5 drivers on our message forum
https://forums.guru3d.com/data/avatars/m/198/198862.jpg
Let them coming as long they are fixing stuff.
data/avatar/default/avatar29.webp
LEL, another driver?. Maybe im download and test my 5700 xt
https://forums.guru3d.com/data/avatars/m/260/260836.jpg
I didn't know that even new RX 5700XT have stuck memory problems.
https://forums.guru3d.com/data/avatars/m/212/212018.jpg
Fucking hell, 5 drivers in July. No summer for the driver team.
https://forums.guru3d.com/data/avatars/m/243/243702.jpg
At least they work on it and focus on most critical issues.
https://forums.guru3d.com/data/avatars/m/209/209146.jpg
Yeah 19.7.1 to 19.7.3 fixing several issues and then a quick two additional drivers for GTA V and Wolfenstein Youngblood for the 5700 GPU's not bad though I guess the driver overall is fairly similar to 19.7.3 in most other aspects but you never know. 🙂 Oh and the Vulkan runtime is up to 1.1.114.0 now on the official website. https://vulkan.lunarg.com/sdk/home#windows (The driver files are using 1.1.106.0 which was followed by 1.1.108.0 and now 1.1.114.0 but it's mostly extensions so it's not like it's required but eh it's backwards compatible and I like updating. 😀 ) EDIT: Hmm though for known issues and the current priority for the 5700 I had thought the enhanced sync issue would be a priority but I guess it might be for 19.8.1 and maybe a few of the other known issues and whatever else. (Game crashing well that's just a thing, system crashes now that's a problem.) (Well the games in question not even starting is also a issue, wonder what the root cause was but eh probably too technical for me to understand anyway but it got fixed.)
https://forums.guru3d.com/data/avatars/m/258/258688.jpg
Pretty sure these drivers actually fix more things than the read.me's say. Because....I didn't see any funky color screens during the 19.7.5 driver install process--which I saw in all of the 19.7.x drivers before it. I haven't tried the driver overlay for these drivers, yet, but I did have some problems in the earlier drivers with it.
https://forums.guru3d.com/data/avatars/m/275/275511.jpg
waltc3:

Pretty sure these drivers actually fix more things than the read.me's say. Because....I didn't see any funky color screens during the 19.7.5 driver install process--which I saw in all of the 19.7.x drivers before it.
I think it was fixed by the latest cumulative update on the Windows side. Now there is no problem even with "old" stable 19.5.2 driver.
https://forums.guru3d.com/data/avatars/m/266/266474.jpg
The known problems alone should not warrant another driver release - for just one F* game, seriously?!
https://forums.guru3d.com/data/avatars/m/252/252615.jpg
Montville:

The known problems alone should not warrant another driver release - for just one F* game, seriously?!
If AMD don't fix bugs, people complain - if they do, people complain too; typical example of damn if they do, damn if they don't.
https://forums.guru3d.com/data/avatars/m/266/266474.jpg
Jackalito:

If AMD don't fix bugs, people complain - if they do, people complain too; typical example of damn if they do, damn if they don't.
For me, like many others here, nothing has been fixed since April this year - what are you on about?
https://forums.guru3d.com/data/avatars/m/216/216218.jpg
What gamebraking bug needs that urgent fix according to you?
https://forums.guru3d.com/data/avatars/m/266/266474.jpg
Krteq:

What gamebraking bug needs that urgent fix according to you?
Dunno about gamebraking but still waiting for elevated idle clocks (Polaris) to be fixed since month let alone all the other tech problems (not affecting me) - new Games are least priority.
https://forums.guru3d.com/data/avatars/m/209/209146.jpg
Early April...Polaris GPU. Maybe the higher clock speed on things like memory and changes found in Wattman though as a Vega user I haven't kept up much for Polaris issues although for the Vega cards the fan curve and changes in Wattman behavior can be troubling as well and that is still a thing too. Here's 19.6.1 and now the voltage is going to be a bit more aggressive but also dynamic so +20 to +50mv and there goes stability though it's not too hard to correct for but as a unlisted silent change it was a discovery the community made as some users got system stability problems measured and monitored and that little aha moment was found as to what had happened. (Though it's far from the first time.) EDIT: Ah it was the elevated clock issue so that is still a thing then plus from the release notes it's also happening on the VII now though as a separate issue but both need fixing. (And for the 5700 which AMD is prioritizing that enhanced sync problem needs to be resolved sooner rather than later, system stability can't be a thing after all.)
https://forums.guru3d.com/data/avatars/m/243/243702.jpg
Montville:

Dunno about gamebraking but still waiting for elevated idle clocks (Polaris) to be fixed since month let alone all the other tech problems (not affecting me) - new Games are least priority.
I have not had elevated GPU clocks on Polaris even on latest driver. Only elevated memory clocks due to 240Hz screen. But that is to be expected. And power draw from that is nothing crazy. Moving data costs much more energy than just having memory clocked high.
https://forums.guru3d.com/data/avatars/m/198/198862.jpg
Fox2232:

I have not had elevated GPU clocks on Polaris even on latest driver. Only elevated memory clocks due to 240Hz screen. But that is to be expected. And power draw from that is nothing crazy. Moving data costs much more energy than just having memory clocked high.
I think he meant memory clocks. Basically only downside is the higher vram temps on idle.
https://forums.guru3d.com/data/avatars/m/266/266474.jpg
Fox2232:

Only elevated memory clocks due to 240Hz screen.
Wrong - 60HZ screen here and same problem!
Undying:

I think he meant memory clocks. Basically only downside is the higher vram temps on idle.
Both clocks are elevated but ram clock is worst @ constant ~1000Mhz
Undying:

.... Basically only downside is the higher vram temps on idle.
Wrong there coz it results in sporadic desktop screen seizures let alone higher vram temps mean higher power consumption people pay for on top of the already high electricity costs! Stop belittling issues instead fix that S*T is the way to go Just amazing to see what rubbish excuses come up here to not do a proper job!
https://forums.guru3d.com/data/avatars/m/243/243702.jpg
Montville:

Wrong - 60HZ screen here and same problem! Both clocks are elevated but ram clock is worst @ constant ~1000Mhz Wrong there coz it results in sporadic desktop screen seizures let alone higher vram temps mean higher power consumption people pay for on top of the already high electricity costs! Stop belittling issues instead fix that S*T is the way to go Just amazing to see what rubbish excuses come up here to not do a proper job!
You are wrong here. Any elevated GPU clocks would eat more energy than operating VRAM on 1000MHz while not using it. Mine was constantly on 2250MHz due to 240Hz screen. But went to minimal set in vBIOS on 60Hz. Basically you see some elevated clock number and without understanding of it, you try to make it look like disaster. What are those "desktop screen seizures" you talk about? And finally, if you worry about additional 8W eaten while system is idling, maybe you should not start that system at all. Or look for multimedia notebook. That entire device can idle at around 12~15W including PSU power efficiency. Because here 8W 24/7 would cost me around $1.3 a month. Considering those few hours a day my system is running idle, 8W on something like 80~100W total power draw on wall socket is easily ignored. Especially if I compare it to active time when my system may eat 400W+ on wall socket.
https://forums.guru3d.com/data/avatars/m/266/266474.jpg
Perhaps, Fox, you explain why the clocks are elevated when it was fine at idle for years? .. what's the purpose doing so? Why so vehemently refusing to fix that driver issue? No worries, I use an older driver and all is good but this kinda stubborn arrogance from AMD (driver) just tells me no more AMD GPU!
Fox2232:

Any elevated GPU clocks would eat more energy than operating VRAM on 1000MHz while not using it. Mine was constantly on 2250MHz due to 240Hz screen. But went to minimal set in vBIOS on 60Hz.
This here is a single monitor @60Hz and my idle is 300/300 IF the driver works correctly. Lucky I keep old drivers!
data/avatar/default/avatar22.webp
Driver works smoothly. People should realize default clocks and normal monitors are the scope AMD's team works with.