The AMD Driver Thread

red eye · 17 May 2017 at 18:41

locodice said:
Try the AB 4.4.0 Beta 9 (The latest).

Might be looking in the wrong place, but Guru3d and msi both only have 4.3

locodice · 17 May 2017 at 20:59

red eye said:
Might be looking in the wrong place, but Guru3d and msi both only have 4.3

http://forums.guru3d.com/showpost.php?p=5431939&postcount=367

Here you go, Beta 9 is bundled with the latest RTSS.

UTmaniac · 19 May 2017 at 08:33

17.5.2 has been released overnight.

TonyTurbo78 · 19 May 2017 at 09:27

UTmaniac said:
17.5.2 has been released overnight.

beat me to it, was just coming here to post the same thing

Here are the noteworthy bits anyway, grab em here. http://support.amd.com/en-us/kb-art...mson-ReLive-Edition-17.5.2-Release-Notes.aspx

It's nice to see them fix the Forza Horizon 3 long loading times.

Radeon Software Crimson ReLive Edition 17.5.2 Highlights

Support For

Prey®

Up to 4.5% performance improvement measured on Radeon RX 580 8GB graphics when compared to Radeon Software Crimson ReLive edition 17.5.1(1)

Fixed Issues

NieR™: Automata may experience a random hang or application crash after short periods of gameplay.

Forza™ Horizon 3 may experience very long map/launch load times.

The primary display adapter may sometimes appear disabled in Radeon Settings while driving a display from the linked adapter in Multi GPU system configurations.

Radeon RX 550 series graphics products may experience a system hang when entering sleep or hibernate modes.

Known Issues

Virtual Super Resolution may fail to enable on some Radeon RX 400 and Radeon RX 500 series graphics products.

The Display feature in Radeon Settings "GPU Scaling" may not function for some games.

A small amount of apps may still experience issues with Borderless Fullscreen mode and AMD FreeSync™ technology if other applications or game launchers are running on the primary screen in the background.

Counter-Strike™: Global Offensive and World of Warcraft™ may experience flickering or performance issues the first time the game is launched on a system boot with AMD FreeSync™ technology enabled. Workarounds include exiting and restarting the application or task switching (alt+tab) in and out of the game to fix the issue.

Known Issues for Radeon ReLive

The XBOX™ DVR application may cause conflicts with Radeon ReLive, users are suggested to disable XBOX™ DVR if Radeon ReLive is experiencing issues.

Radeon ReLive may fail to install on AMD APU Family products or experience a system hang or failure to record when using the recording feature on AMD APU Family products.

Radeon ReLive may intermittently fail to work after performing task switches of applications. A work around is to disable and then enable the feature in Radeon Software.

Radeon ReLive may exhibit corruption in recordings when capturing Microsoft Office applications.

Radeon ReLive may experience recording or streaming issues when task switching using ALT+TAB.

Nexus18 · 19 May 2017 at 11:34

Using the second last drivers for the last week, all good so far, however, I don't think my MSI AB undervolt is "sticking" as the temps are ramping up as well as the fan speed so probably going to have to roll back to 16.11.5 yet again.....

Any idea what I need to adjust in AMD's awfully presented wattman to achieve the same as what I have in MSI AB i.e. -31mV???

@AMDMatt

shankly1985 · 19 May 2017 at 12:42

Possible fix for you guys that have Wattman reset on system start up. Seems like its a glitch that happens when you have Windows 10 Fast boot enabled... If fast boot fails to load it will load the last known clean settings that also restores Wattman settings. I just found this out by my Fast boot glitched and failed to load some programs at start up and I also got Wattman failure.

Too see if this is the case for you, does wattman only fail from a full system power on meaning you first have shutdown then system? Or does it also fail even with a simple system restart?
If it doesn't happen with a normal restart then you will need to delete or temp disable and re-enable Hibernation

https://www.tenforums.com/tutorials/2859-enable-disable-hibernate-windows-10-a.html

shankly1985 · 19 May 2017 at 15:32

Nexus18 · 19 May 2017 at 16:07

It's pointless doing any benchmarks for that broken game as the screen space reflection setting doesn't work properly i.e. you have to turn it off, apply and on, hit apply upon a new game load in order for the setting to be turned on and when it is properly activated, it is an artifacting mess:

Plus missing shadows and some other effects.

shankly1985 · 19 May 2017 at 18:14

Nexus18 said:
It's pointless doing any benchmarks for that broken game as the screen space reflection setting doesn't work properly i.e. you have to turn it off, apply and on, hit apply upon a new game load in order for the setting to be turned on and when it is properly activated, it is an artifacting mess:

Plus missing shadows and some other effects.

Working perfectly fine here mate even went looking for all this shadows etc after the nvidia issue. I been streaming my full gameplay

Nexus18 · 19 May 2017 at 18:37

shankly1985 said:
Working perfectly fine here mate even went looking for all this shadows etc after the nvidia issue. I been streaming my full gameplay

Shadows is a hard one to notice I find, most stuff has shadows but I am finding a few things are missing their shadows.

As for screen space reflections. Upon launching the game:

- turn off SSP
- hit apply
- turn it back on to full resolution
- hit apply

Looking at the likes of neogaf, steam etc. it seems to be affecting the vast majority of players, even looking on reddit, the developers have confirmed that there is a problem with SSR:

Have you tried turning off SSR and restarting to see if that resolves it? We're working on a fix for SSR, but in the meantime turning it off has helped people resolve the issue.

FredFlint · 20 May 2017 at 21:03

Keep getting this error when trying to load a BF1 or Dragon Age Inquisition:

It happens about 70% of the time, sometimes a reboot will fix it but other times I do a clean install of the driver but I don’t know if the install fixes it or the reboot? To be fair, I don’t know if this is a driver problem, game problem or Origin problem as I have not had this problem with any other games yet. When this happens the resolution selector in games is not populated which is why they crash, it cannot set a screen res. With BF1 I can delete the settings profile and it will load using borderless mode. I ran my PC 100% stock to rule out memory problems but it still happens.

Phixsator · 21 May 2017 at 06:29

Got Prey working mostly flawless with Crossfire but its been a pain. Not so much from the game itself but more about hitting the right reinstall of drivers. That said I seem to get what looks like a memory leak after an extended play session of 45+ minutes. I think that is the game though.

UTmaniac · 21 May 2017 at 15:55

shankly1985 said:
Possible fix for you guys that have Wattman reset on system start up. Seems like its a glitch that happens when you have Windows 10 Fast boot enabled... If fast boot fails to load it will load the last known clean settings that also restores Wattman settings. I just found this out by my Fast boot glitched and failed to load some programs at start up and I also got Wattman failure.

Too see if this is the case for you, does wattman only fail from a full system power on meaning you first have shutdown then system? Or does it also fail even with a simple system restart?
If it doesn't happen with a normal restart then you will need to delete or temp disable and re-enable Hibernation

https://www.tenforums.com/tutorials/2859-enable-disable-hibernate-windows-10-a.html

Early days, but promising since doing this, thanks so far!

D1craig · 21 May 2017 at 16:01

Nexus18 said:
Using the second last drivers for the last week, all good so far, however, I don't think my MSI AB undervolt is "sticking" as the temps are ramping up as well as the fan speed so probably going to have to roll back to 16.11.5 yet again.....

Any idea what I need to adjust in AMD's awfully presented wattman to achieve the same as what I have in MSI AB i.e. -31mV???

@AMDMatt

have you tried the chill setting? that has worked wonders for me. dropped my temps by as much as 7 and max power by almost 50.

shankly1985 · 21 May 2017 at 16:19

UTmaniac said:
Early days, but promising since doing this, thanks so far!

Great stuff let's hope that's sorted then.

Nexus18 · 21 May 2017 at 16:22

D1craig said:
have you tried the chill setting? that has worked wonders for me. dropped my temps by as much as 7 and max power by almost 50.

No not yet, although I thought that only applied to when you weren't moving in game at all or/and not much was happening in the scene i.e. no input detected from you?

D1craig · 21 May 2017 at 16:39

i dont understand it fully but it tends to slowly jump up to full power. say you are just running to next place it doenst use full power but in the midst of battle it wont hold back at all. give it a try it might be exactly what you are looking for. and when you figure out how to get the undervolt to work it will be even more effective.

before using it my gpu would get close to 60C and hit 280 power. now the highest ive seen temps wise is 53C and 250 power.

Nexus18 · 21 May 2017 at 16:48

D1craig said:
i dont understand it fully but it tends to slowly jump up to full power. say you are just running to next place it doenst use full power but in the midst of battle it wont hold back at all. give it a try it might be exactly what you are looking for. and when you figure out how to get the undervolt to work it will be even more effective.

before using it my gpu would get close to 60C and hit 280 power. now the highest ive seen temps wise is 53C and 250 power.

Nice, will try it out and see how it goes.

And yeah I need someone to clarify how I would get the same undervolt as MSI -31mV in the AMD control panel as with these newest relive drivers, MSI AB doesn't seem to be applying the undervolt... Instead of a max temp of about 70/73 with a max fan speed of 59%, I am now hitting 81+ degrees with a max fan speed of 71%..... :/

EDIT:

Seems like it doesn't work in the current game I'm playing, mafia 3.

EDIT:

On a separate note:

290 still holding up very well.

chaosophy · 22 May 2017 at 01:15

My understanding of under volting the card in the drivers...

Turning off the 'Frequency (%)' setting will give you a box for each power state where you can manually change the frequency for each, or you can leave it on % and then the slider raises each state's frequency by that amount.

Turning on 'Voltage Control (mV)', changes it from Auto to manual then you can input a voltage value for each state. So you should be able to drop any and all of these -31 for each state you want to undervolt by that amount.

I think anyway. Seems to work ok for me that way. Used to use Trixx but it was either a driver update and/or the last Win10 creators(?) update that seemed to stop that working for me and not been back and tried it since.
Which is a PITB as I had a nice fan profile set up with that.

Also think there is much better info from Matt somewhere but not sure if it's this thread it's buried in or one of the Fury ones. :/

DragonQ · 22 May 2017 at 09:43

chaosophy said:
My understanding of under volting the card in the drivers...

Turning off the 'Frequency (%)' setting will give you a box for each power state where you can manually change the frequency for each, or you can leave it on % and then the slider raises each state's frequency by that amount.

Turning on 'Voltage Control (mV)', changes it from Auto to manual then you can input a voltage value for each state. So you should be able to drop any and all of these -31 for each state you want to undervolt by that amount.

I think anyway. Seems to work ok for me that way. Used to use Trixx but it was either a driver update and/or the last Win10 creators(?) update that seemed to stop that working for me and not been back and tried it since.
Which is a PITB as I had a nice fan profile set up with that.

Also think there is much better info from Matt somewhere but not sure if it's this thread it's buried in or one of the Fury ones. :/

Yeah that's pretty much it. I put in a mild overclock at the top frequency, then I found I could run that at 1070 mV, so I then just set all power states that were over 1070 mV down to that level. Anything below I didn't touch because finding instability at lower power states is more difficult. I use MSI Afterburner for fan control since WattMan is a bit pants for that.