• 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

Windows Update driver is 17.1 (which is actually 17.4.1). This is the only driver that would be downloaded to your system from Windows Update.

Did you check Radeon Settings to see which version was installed? Our drivers just don't reinstall themselves, perhaps MSI AB was reading the driver version wrong.

Either way, try DDU and then pick the driver of your choice.
 
@AMDMatt I figured the cause of stuttering in DayZ, disabling shadows pretty much fixes it, most other settings maxed out now.. any chance of driver team looking into this? I will post on DayZ forums about this too and see what they have to say about it.. Thanks :)
 
I'm having weird issues that might be 17.7.2 related. I was on 17.4.4 but updated mainly to try out Enhanced Sync. Now I notice that in Overwatch three things have changed:

- My FPS drops (to 50-60 or even lower from 100+) in heavy fight scenes. Never used to happen - I'm very sensitive to drops like that.
- My in-game GPU temperature is 10-15 degrees higher for no apparent reason. Fan curves are the same (assuming latest Afterburner is actually setting and reporting correctly) and we're not exactly in a heatwave right now!
- My GPU isn't holding its maximum clock any more (used to be 1300 MHz solid, now hovers between 1280 and 1300 MHz).

The problem is I haven't played in around a month and there's been three changes since then: new AMD drivers, big Overwatch patch, and new Afterburner. I can see lots of posts on the Overwatch forums about recent performance problems in the latest patch but they could also be coincidence as others are likely to have updated drivers also. My first step was to revert to the 17.4.4 drivers but when I tried to install it, the installer just downloaded an "installer update" and installed 17.7.2 instead!

So basically: Anyone else experienced similar issues with 17.7.2? Anyone know how to force-install an old driver?
 
Nearly installed 17.7.2 last night, glad I didn't now.

Not sure there's much point updating drivers for my 480 for the foreseeable.
 
just a question i have not had crimson tell me about an update for a fair while, has windows 10 been doing the driver updates behind my back? im on 17.1.1 and i don't see any update option in crimson.
 
Last edited:
DragonQ said:
Anyone know how to force-install an old driver?
Click to expand...
Figured out I had the minimal installer rather than the offline one so grabbed that and I'm back on 17.4.4. Will test if that's fixed anything tonight.

Yrkoon said:
just a question i have not had crimson tell me about an update for a fair while, has windows 10 been doing the driver updates behind my back? im on 17.1.1 and i don't see any update option in crimson.
Click to expand...

17.1.1 is pretty old by now but maybe Windows installed it? Just do a manual update check in Crimson.
 
Can anyone confirm the most recent drivers for RX Vega? I've read that there was a 'new driver drop hitting just hours before launch that enabled some level of consistent tuning' from one review site and that the drivers are 17.8.1 although the only drivers available to download from AMDs site that could I find are not specifically labelled 17.8.1 - the driver file once downloaded is called win10-64bit-radeon-rx-vega-software-17.30.1051-b6-aug7.exe.
 
Yeah that's 17.8.1 Beta 6 and is available at loads of sites. For some reason AMD uses very different customer-facing version numbers for their drivers compared to their internal versioning.
 
TNA said:
Yeah. Had no luck. Still have the issue.

I could just turn off screen sleep to never which would solve the problem, but we should not have to. Would get AMDMatt's attention on the matter, but I get the feeling he and AMD are super busy at the moment :p
Click to expand...

Might be a bit pointless now but I think I accidentally found the cause which coincides with your sleep comment TNA. If I turn my monitor off using the OSD after shutting down my PC instead of leaving it to go to standby the issue doesn't occur on boot up. Leaving it on standby and the error pops up.

Odd but not a game changer as I don't mind turning my monitor off after each use anyway.
 
Kidge said:
Might be a bit pointless now but I think I accidentally found the cause which coincides with your sleep comment TNA. If I turn my monitor off using the OSD after shutting down my PC instead of leaving it to go to standby the issue doesn't occur on boot up. Leaving it on standby and the error pops up.

Odd but not a game changer as I don't mind turning my monitor off after each use anyway.
Click to expand...
I always turn off PC and then turn off monitor. Will mess around and see if I see anyway changes :)
 
LoadsaMoney said:
Yeah rumours that Vega 17.8.1 driver is old, tiled raster not working etc...., AMD didn't up the newer driver, as found bugs last minute.
Click to expand...
These new drivers will push performance past 1080Ti right? :p

So Vega sales have slowed down since the rumours of 88 Jigawatts of hash power of Vega turned out not to be true, now we have a new one for one last push of sales eh? :D
 
I see the drivers for RX Vega still haven't fixed The Evil Within - the first Crimson Relive drivers completely broke this game, it hasn't worked since 16.11.5. I raised a ticket on this but nothing happened - maybe when the The Evil Within 2 gets released they will have a look at it...
 
You must log in or register to reply here.
Back
Top Bottom