The AMD Driver Thread

Matkinson · 10 Nov 2017 at 09:15

No, only when booting up MSI Afterburner. I just assumed it was drivers due to practically nothing.

I believe I've seen some posts about Afterburner and AMD drivers, however I could just be imagining things.

My card isn't anything other than stock. It's an MSI r9 290 as well lol.

lowdog · 10 Nov 2017 at 10:39

it seems inevitably that every time you use wattman to under volt and change any State it will sooner or later craaaaap the bed ultimately leading to the drivers becoming corrupted and needing a complete uninstall and DDU to get stable stock functionality back.

Example; Custom setting - State 6 - 1702/1130 and State 7 - 1752/1150 and mem at 950mv 1100Mhz (Vega 64 AIO) gives what seems like completely stable 1740MHz in games with what seems like roughly 200W power draw as monitored in game using HWiNFO64......finish gaming hit wattman reset, go away and comp goes to sleep, wake up comp and later on try same settings and FAIL! FFS!....reset wattman, reboot, try again and FAIL! FFS!, reset wattman, reboot and sooner or later drivers are stuffed and no longer seems to function stably......uninstall and DDU....AGAIN!

The only time they seem to retain stability is if you use the standard presets of "Power Save" - "Balanced" or "Turbo" otherwise this driver for me is utter craaaaaaaaaaaaap. :rolleyes:

SpudMaster · 10 Nov 2017 at 11:33

lowdog said:
it seems inevitably that every time you use wattman to under volt and change any State it will sooner or later craaaaap the bed ultimately leading to the drivers becoming corrupted and needing a complete uninstall and DDU to get stable stock functionality back.

Example; Custom setting - State 6 - 1702/1130 and State 7 - 1752/1150 and mem at 950mv 1100Mhz (Vega 64 AIO) gives what seems like completely stable 1740MHz in games with what seems like roughly 200W power draw as monitored in game using HWiNFO64......finish gaming hit wattman reset, go away and comp goes to sleep, wake up comp and later on try same settings and FAIL! FFS!....reset wattman, reboot, try again and FAIL! FFS!, reset wattman, reboot and sooner or later drivers are stuffed and no longer seems to function stably......uninstall and DDU....AGAIN!

The only time they seem to retain stability is if you use the standard presets of "Power Save" - "Balanced" or "Turbo" otherwise this driver for me is utter craaaaaaaaaaaaap.

Probably wasn't stable in the first place as 1752/1150 seems rather optimistic to me and for it to only be drawing 200w. My V56 draws upto 250w at 1630/1050 and 1100mhz hbm

henson0115 · 10 Nov 2017 at 12:33

SpudMaster said:
Probably wasn't stable in the first place as 1752/1150 seems rather optimistic to me and for it to only be drawing 200w. My V56 draws upto 250w at 1630/1050 and 1100mhz hbm

sounds like your not undervolting, i see 150-180w depending on the undervolt. 950 for example gives around 150w roughly

henson0115 · 10 Nov 2017 at 12:36

lowdog said:
it seems inevitably that every time you use wattman to under volt and change any State it will sooner or later craaaaap the bed ultimately leading to the drivers becoming corrupted and needing a complete uninstall and DDU to get stable stock functionality back.

Example; Custom setting - State 6 - 1702/1130 and State 7 - 1752/1150 and mem at 950mv 1100Mhz (Vega 64 AIO) gives what seems like completely stable 1740MHz in games with what seems like roughly 200W power draw as monitored in game using HWiNFO64......finish gaming hit wattman reset, go away and comp goes to sleep, wake up comp and later on try same settings and FAIL! FFS!....reset wattman, reboot, try again and FAIL! FFS!, reset wattman, reboot and sooner or later drivers are stuffed and no longer seems to function stably......uninstall and DDU....AGAIN!

stability in wattman has gone down since the 3rd driver release for Vega most definitely. never had resets, now with the latest driver i am seeing more and more, on pretty much stock clocks - same as the older drivers.
seems game crashing causing wattman resets and before anybody mentions stability, its 100% stable and was also in older drivers to.

Overlag · 10 Nov 2017 at 16:50

Is it just me or have the Drivers taken a proper dive in the last few months?

Martini1991 · 10 Nov 2017 at 16:53

Wattman stopped keeping my settings. Why's it to hard to make it as user easy as Afterburner?

EDIT : Just got Afterburner on and set to -125mv and I'll just stick with that.

Nexus18 · 10 Nov 2017 at 17:39

Yup wattman is beyond awful, got to be the most confusing/irritating UI ever.

Nexus18 · 10 Nov 2017 at 17:40

Overlag said:
Is it just me or have the Drivers taken a proper dive in the last few months?

I been saying this for a while now, to me it just feels like vega followed by polaris has been getting all the attention/time/resources, seems to be showing for other amd gpus too i.e. as the fury gpus performance is dropping big time

Dicehunter · 10 Nov 2017 at 18:30

Just curious but when I ran Nvidia and DSR on a 4K display I had the option of using 8K in games, For screenshots of course

would that be an option on AMD through VSR if I hooked up my Vega64 to a 4K display ?

lowdog · 10 Nov 2017 at 20:06

SpudMaster said:
Probably wasn't stable in the first place as 1752/1150 seems rather optimistic to me and for it to only be drawing 200w. My V56 draws upto 250w at 1630/1050 and 1100mhz hbm

It was stable and that was the average power draw.

My 56 @ 64 bios with 1620MHz core and 1075mv undervolted was around 180W - 200W

wattman and driver stability are just pure craaaaaaap plain as that.

shankly1985 · 10 Nov 2017 at 22:45

Had a system crash tonight, complete white screen! @AMDMatt any experience with a white screen of death?

This is a known issue from driver 17.8.2 and is very much what I experienced was away from PC and watched a youtube video when it happened.

After resuming from sleep and playing back video content the system may become unresponsive on Radeon RX Vega series graphics products.

megatron · 10 Nov 2017 at 22:48

Not sure if I should post this in the vega 56 thread but I got a reply from AMD on my issues. Not impressed. I personally think they need to do a performance pass on the game, and the other bug should just not exist at all. I tried updating my bios to F7 but went back to F6 (Z97X-Gaming 5) because my clock which was previously stable was no longer. Here is the reply:

Dear ,

Your service request : SR #{ticketno:[8200777836]} has been reviewed and updated.

Response and Service Request History:

Thank you for the response.

I see that you have tried the latest drivers and experiencing the same issue with all the vega compatible drivers.

Please make sure you have updated the motherboard BIOS and all the settings are default.

Also try disabling hardware acceleration in Google Chrome settings and check if the graphic corruption occurs.

Additionally, If possible try the graphic card on a different computer and check the status.

Thank you for contacting AMD.

In order to update this service request, please respond, leaving the service request reference intact.

Best regards,

Santosh

AMD Global Customer Care

Here is my thread on one of the issues:
https://forums.overclockers.co.uk/t...nd-clocks-utilization.18796490/#post-31245884

heartburnron · 10 Nov 2017 at 23:43

Overlag said:
Is it just me or have the Drivers taken a proper dive in the last few months?

I've had no significant issues with any of the drivers since Vega was released and I'm playing with Wattman daily. Aside that is from having difficulty enabling HBCC but that turned out to be the 450 game profiles loaded into the settings that was impacting on performance and causing the application to time out...

shankly1985 · 10 Nov 2017 at 23:49

My wattman settings are also fine, undervolt quite abit

LtMatt · 11 Nov 2017 at 06:37

megatron said:
Not sure if I should post this in the vega 56 thread but I got a reply from AMD on my issues. Not impressed. I personally think they need to do a performance pass on the game, and the other bug should just not exist at all. I tried updating my bios to F7 but went back to F6 (Z97X-Gaming 5) because my clock which was previously stable was no longer. Here is the reply:

Dear ,

Your service request : SR #{ticketno:[8200777836]} has been reviewed and updated.

Response and Service Request History:

Thank you for the response.

I see that you have tried the latest drivers and experiencing the same issue with all the vega compatible drivers.

Please make sure you have updated the motherboard BIOS and all the settings are default.

Also try disabling hardware acceleration in Google Chrome settings and check if the graphic corruption occurs.

Additionally, If possible try the graphic card on a different computer and check the status.

Thank you for contacting AMD.

In order to update this service request, please respond, leaving the service request reference intact.

Best regards,

Santosh

AMD Global Customer Care

Here is my thread on one of the issues:
https://forums.overclockers.co.uk/t...nd-clocks-utilization.18796490/#post-31245884

I just watched your video, looks good, FPS up to 100 at times and smooth performance.

GPU utilization is low, so looks CPU/Engine/API bound. Our optimisations will already be in place for this game.

I don't really see a problem there other than what i mentioned above.

shankly1985 said:
Had a system crash tonight, complete white screen! @AMDMatt any experience with a white screen of death?

This is a known issue from driver 17.8.2 and is very much what I experienced was away from PC and watched a youtube video when it happened.

After resuming from sleep and playing back video content the system may become unresponsive on Radeon RX Vega series graphics products.

No experience at all my friend.

SpudMaster · 11 Nov 2017 at 08:23

henson0115 said:
sounds like your not undervolting, i see 150-180w depending on the undervolt. 950 for example gives around 150w roughly

sounds like your not reading my post

1630mhz with 1050mV and 1100mhz hbm draws upto 250w on my system when playing pubg. Thats an undervolt of 150mV. Other games around draw 215w but still more than 200w with 100mV and 120mhz less than lowdog is using who says is averaging 200w draw.

Maybe is card wasn't boosting to full speed cos in games like SFV my card uses less than 150mV at the same wattman settings as the game is lockeded at 60fps

henson0115 · 11 Nov 2017 at 11:47

SpudMaster said:
sounds like your not reading my post 1630mhz with 1050mV and 1100mhz hbm draws upto 250w on my system when playing pubg. Thats an undervolt of 150mV. Other games around draw 215w but still more than 200w with 100mV and 120mhz less than lowdog is using who says is averaging 200w draw.

Maybe is card wasn't boosting to full speed cos in games like SFV my card uses less than 150mV at the same wattman settings as the game is lockeded at 60fps

apologies missread on my part

shankly1985 · 11 Nov 2017 at 15:53

Post 14267

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

Put this here also from VEGA 56 thread so more people can see it.

Windows 8 and 10 added a feature called Fastboot it uses hibernation to create a image off all the Windows loaded settings so when you power on the PC you will start much faster.. When you pull the PSU switch you will reset all the Windows setting and even remove the fastboot image so Windows will fall back to the default settings.
I just tried it myself and it failed my Wattman settings.

If a user shutdowns Windows with Fastboot enabled, and then switches the PSU off next start up will fall back to default windows image and result in Wattman settings from failing.

This could explain why users on here are saying the wattman doesn't always remember settings after see do these guys power off the PSU!!!

Steampunk · 11 Nov 2017 at 16:00

shankly1985 said:
Post 14267

Put this here also from VEGA 56 thread so more people can see it.

Windows 8 and 10 added a feature called Fastboot it uses hibernation to create a image off all the Windows loaded settings so when you power on the PC you will start much faster.. When you pull the PSU switch you will reset all the Windows setting and even remove the fastboot image so Windows will fall back to the default settings.
I just tried it myself and it failed my Wattman settings.

If a user shutdowns Windows with Fastboot enabled, and then switches the PSU off next start up will fall back to default windows image and result in Wattman settings from failing.

This could explain why users on here are saying the wattman doesn't always remember settings after see do these guys power off the PSU!!!

Nope, I never power off my PSU and it happens to me. For some people Wattman doesn't seem compatible with Windows Fastboot.