• 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

Drangueos said:
Something weird happened today..
I was using driver 16.11.4 and I got a notification that it was available a new updated driver, even that I disabled this before.
I declined the update, a couple of seconds after my screens started to flicker and I got that windows warning sound that a new device was found, I restarted my pc and it got stuck when loading windows, so I restarted again and when it got back to windows it was showing only 2 GPUS, I have 3 and the driver version was 16.6, instead of 16.11.4 that I was using before.
I removed the AMD driver, installed back the 16.11.4 and now it is working as usual.

I have a friend that had a problem after this update alert, he has one GPU only and after this update message his pc got frozen and he had to restart, he was using the 16.6 driver already.
Click to expand...

similar just happened to me except for the driver actually being installed but i just had a popup to install driver 16.12.2 over the 17.1.1 im using and i dont have auto driver update enabled.
 
I'm using 16.11.5s, due to Wattman allowing my R9 390 hit ~95C while gaming a few times in both 16.12.1 and 16.11.2, not even bothered with 17.1.1s yet as a result.

Then for the first time I can recall in Crimson, I was greeted with a new window earlier...

"New driver has been downloaded and is ready to be installed. Click upgrade to continue."

My guess is that it is 16.12.2s, as they are the "recommended" driver, while 17.1.1s are listed as "optional." But who knows? :D
 
UTmaniac said:
I'm using 16.11.5s, due to Wattman allowing my R9 390 hit ~95C while gaming a few times in both 16.12.1 and 16.11.2, not even bothered with 17.1.1s yet as a result.

Then for the first time I can recall in Crimson, I was greeted with a new window earlier...

"New driver has been downloaded and is ready to be installed. Click upgrade to continue."

My guess is that it is 16.12.2s, as they are the "recommended" driver, while 17.1.1s are listed as "optional." But who knows? :D
Click to expand...


That sounds like it might be a bug similar to the one I experienced, Just before Relive released the auto fan option was turned of and the button to turn it back on was missing, You should install the latest and see if you have a similar situation. For me the fan speed would keep increasing until it hit 100% speeds which caused the gpu to stay under 30 degrees even at full load, The end result may be different but the root cause may be similar plus you could use Afterburner to control it if you can't fix it in the latest Wattman.

Also, put a ticket in to AMD for it.

http://www.amdsurveys.com/se.ashx?s=5A1E27D23A3DE979
 
Phixsator said:
Could be the hardware acceleration option in either a browser or a chat program like curse voice that keeps the clocks locked. i had that problem once with chrome i believe and listening to youtube in the background while playing a game. It would mess with the clock and lock it lower than full speed.
Click to expand...

There's nothing open :(.

After keeping my eye on it, it seems like it is getting stuck when turning the display back on after inactivity.

It doesn't do it every time, but that seems to be where the issue lies. Thing is, I have had this setup for at least 6 months and it's been fine, this issue only reared it's head after a Windows update :(.

I even tried restarting the driver with radeonmod and it still won't budge, only a reboot clears it.

I suppose I could just tell windows not to turn the display off. It's hooked to a tv, so when it's not on the pc, it's either in stand by or on a tv channel anyway.
 
Armadillo said:
There's nothing open :(.

After keeping my eye on it, it seems like it is getting stuck when turning the display back on after inactivity.

It doesn't do it every time, but that seems to be where the issue lies. Thing is, I have had this setup for at least 6 months and it's been fine, this issue only reared it's head after a Windows update :(.

I even tried restarting the driver with radeonmod and it still won't budge, only a reboot clears it.

I suppose I could just tell windows not to turn the display off. It's hooked to a tv, so when it's not on the pc, it's either in stand by or on a tv channel anyway.
Click to expand...

gotta love windows updates.. they only ever fix things..nothing else /sarcasme
 
shankly1985 said:
Seen couple people report this now, they is a work around thread on reddit.
Not had it happen with my 290 so am not sure what triggers this bug.
Click to expand...

Rolled back to the 16.11.5s and this has sorted it.
Nothing in ReLive I wanted anyway, but Windows decided to 'upgrade' my drivers from 16.10.3 to 16.6, so I thought if I was manually updating I might as well go right up to date.
I'm gonna give AMD a bit more time to get ReLive right before I try them again.
 
Reading through the last few pages and I am finding it hard to gather what's the most stable driver to use as I have a 480 coming tomorrow.

Any ideas please?

Thanks.
 
Davanius said:
Reading through the last few pages and I am finding it hard to gather what's the most stable driver to use as I have a 480 coming tomorrow.

Any ideas please?

Thanks.
Click to expand...

17.1.1 I have no issues with it, gain 1% perf clock for clock on my Nano @1140, but the best part I can now OC it to 1150 for more power :P

I wish I had a FuryX, I would be bordering to 1170 if not 1200 atm with my semi-custom WC.
 
Phixsator said:
gotta love windows updates.. they only ever fix things..nothing else /sarcasme
Click to expand...

Managed to find a work around :D.

This issue seems to have plagued the 5XXX for a while. 400/900 is apparently accelerated video clocks. So not quite 2d, but not 3d clocks either, it's just not suppose to get stuck. While an old topic, that I'm not sure if it even applies to 10, said it's Microsoft H264 Video Decoder MFT that causes it and turning off the hardware accel with DXVA tool will fix it, there was also another "fix" that doesn't involve faffing around. Not sure why it seems to mostly do it when turning the tv back on.

Old Amd gpu clock tool for 5XXX. Install, make a shortcut with -restore in the shortcut, run it, clocks get unstuck, then crtl+shift+windows+B to reset/flush the gpu other wise it flickers.

That'll do for now, no need to reboot, can't be bothered investigating any further only takes a second to do if I noticed they are stuck before a game.
 
Last edited:
shankly1985 said:
Some games it will need you too delete the profile and manually add the games location. It seems that some game that are now on the C: driver dont auto run.
Click to expand...

Rezident said:
When that happened to me it was because the profile was disabled. Under each game in the Radeon settings it will say enables or disabled. Make sure it's enabled.
Click to expand...

Whoops. Forgot about this.

Yeah, it's enabled for the individual profile, I've also tried deleting and readding and still nothing. So far the only game it works on for me has been Arkham origins.

Tried it with random games I have installed just to see if it would work and nothing. Tried

Aragami
Rocket League
Snake bird
Salt and Sanctury
Ghost 1.0

Every single one of them ignored the target control. Either I'm unlucky and just picking stuff it doesn't work with or something is broken over here :(, but then it still works on Arkham origins.
 
You must log in or register to reply here.
Back
Top Bottom