• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Overall most Stable Amd driver?

GreiverBlade said:
i will just stop it there
Click to expand...
Nice try
qubit said:
On the upside for AMD, I haven't seen so many people reporting issues with them lately, so they must have improved a fair bit.
Click to expand...
They did and Nvidia got worse ... and also big titles were never an issue, it's always a couple of unknown buggy games that have issues with amd and more often than not they use opengl
 
BiggieShady said:
Nice try

They did and Nvidia got worse ... and also big titles were never an issue, it's always a couple of unknown buggy games that have issues with amd and more often than not they use opengl
Click to expand...
Hmmm, can't say NVIDIA have gotten worse in my experience, but I do seem to remember some hastily issued hotfixes lately, which doesn't sound so, err, hot. :p Wasn't there a version recently that could actually damage a card? Fan speed control maybe?
 
Stay on topic (not Nvidia).

Thanks.
 
I've only had what I would call a "stability" issue with one AMD driver release in the last 5+ years(caused my card to become almost entirely unusable). Which I reported, and they fixed with the next release. Other than that I've only experienced one other minor performance issue that only effected one particular game(causing erratic framerates). Which I reported, and was also fixed in the next driver release.

There's also this other ongoing issue. Which I've also reported. But they've yet to fix. It doesn't make any difference as far as stability or performance are concerned. It's just annoying to have to use a workaround to fix it.
Frag Maniac said:
That said, after downloading and installing 17.6.2 from AMD's site, GPU-Z shows it as 17.6.1. This has happened with one or two previous versions of their drivers, but I'm not sure if it's a glitch on AMD's part, or the way GPU-Z is reading it.
Click to expand...
I downloaded it from TPU. And when installed GPU-Z shows it as 17.6.2. So maybe you don't really have 17.6.2 installed. Then again maybe you do and something else is wrong.

gpuz.PNG
 
MrGenius said:
I downloaded it from TPU. And when installed GPU-Z shows it as 17.6.2. So maybe you don't really have 17.6.2 installed. Then again maybe you do and something else is wrong.
Click to expand...
OK, thanks for that, will check it out when I get time. Though AMD's site DOES list it as 17.6.2. I also see no update popup for GPU-Z. I doubt it's that my GPU is an older model, since your 280X is basically same.

Anyways, just another report on Wolfenstein: The New Order. Unfortunately when I get to the prison roof at the spot to take out the guy up there before infiltrating to rescue the resistance group, it instantly crashes to desktop. As far as I can tell by threads I've seen on Steam, this is common with W10 running this game.

There have been two workarounds mentioned, both apparently with hit and miss results, or some might just not be implementing them properly I suppose. I first tried what appeared to be the easier one, which involves changing two registry entries via RadeonMod. Unfortunately it didn't work, and when I tried to revert the reg with the backup Radeon Mod made, it screwed up my PC. I actually had to format W10.

The other workaround involves renaming the x64 exe to x32, and making a bat file. I have not tried that one yet.

https://steamcommunity.com/app/201810/discussions/0/144513670982717226/

By the way, I managed last night to play all the way up to the catacombs just before the final boss fight in Wolf The Old Blood, and not one crash. So I really don't get why it's happening in this game.
 
Last edited by a moderator:
17.6.1 is the best so far for Fiji based cards. Good performance and no driver crash.
 
Frag Maniac said:
OK, thanks for that, will check it out when I get time. Though AMD's site DOES list it as 17.6.2. I also see no update popup for GPU-Z. I doubt it's that my GPU is an older model, since your 280X is basically same.

Anyways, just another report on Wolfenstein: The New Order. Unfortunately when I get to the prison roof at the spot to take out the guy up there before infiltrating to rescue the resistance group, it instantly crashes to desktop. As far as I can tell by threads I've seen on Steam, this is common with W10 running this game.

There have been two workarounds mentioned, both apparently with hit and miss results, or some might just not be implementing them properly I suppose. I first tried what appeared to be the easier one, which involves changing two registry entries via RadeonMod. Unfortunately it didn't work, and when I tried to revert the reg with the backup Radeon Mod made, it screwed up my PC. I actually had to format W10.

The other workaround involves renaming the x64 exe to x32, and making a bat file. I have not tried that one yet.

https://steamcommunity.com/app/201810/discussions/0/144513670982717226/

By the way, I managed last night to play all the way up to the catacombs just before the final boss fight in Wolf The Old Blood, and not one crash. So I really don't get why it's happening in this game.
Click to expand...

I had to do the x64 to x86 mod to get the old blood working seeing as that is also a known problem
 
I need the best driver for a 7970 Matrix, in both Windows 10 and 7 the second monitor flickers all the time, but wen I installed the latest Beta Driver it stopped, but games ran like crap.
 
Melvis said:
I need the best driver for a 7970 Matrix, in both Windows 10 and 7 the second monitor flickers all the time, but wen I installed the latest Beta Driver it stopped, but games ran like crap.
Click to expand...
Sounds like the next release might fix both then
 
He said flicker and then I remembered something. I noticed a bad flicker issue with my 280X in NesterJ(NES emulator) during fullscreen mode a few months ago. Which I'd never seen in the past. So I figured it was definitely a driver issue. And proved it was. By dropping all the way back, one version at a time, to Catalyst 15.5, which fixed it. All later drivers I've tested still cause the issue. And I haven't got around to reporting it. Nor do I expect I ever will. I don't run the program often enough to care that much about having to switch drivers when I do.

Not that that's likely going to be of any help. I just figured I'd mention it.
 
Last edited:
Nuckles56 said:
I had to do the x64 to x86 mod to get the old blood working seeing as that is also a known problem
Click to expand...
Did you find a guide that was easy to follow? If so could you link it?

I had no trouble with Old Blood, did you mean The New Order?
 
Nuckles56 said:
I meant the old blood as I couldn't get it to run at a frame rate above 19fps no matter what settings I had. Here's the link to the fix https://steamcommunity.com/app/350080/discussions/0/154644928858134876/?ctp=2
Click to expand...

OK, thanks, I just read some were able to get the x86 rename to work instead of x32. Did you do this on W10 though, or an older OS? Some claim the rename trick doesn't work at all on W10.

On a YouTube vid I saw for this trick, someone in the comments said just using -dx9 as a launch option also works (reverts the game to Dx9 mode), which might be better for me because it would probably yield better performance.
 
Frag Maniac said:
OK, thanks, I just read some were able to get the x86 rename to work instead of x32. Did you do this on W10 though, or an older OS? Some claim the rename trick doesn't work at all on W10.

On a YouTube vid I saw for this trick, someone in the comments said just using -dx9 as a launch option also works (reverts the game to Dx9 mode), which might be better for me because it would probably yield better performance.
Click to expand...
I'm using windows 10 and none of the compatibility options
 
Nuckles56 said:
Good luck
Click to expand...
It worked great! I also implemented the cvaradd r_skipadaptiveglare 1 and cvaradd r_postprocessdofmode -1 commands to a my.cfg file I made, and wow, the game looks way better now even on Med settings. The only bummer is the game won't recognize an autoexec.cfg file, so you need to type exec (your cfg name) into the console every time you launch the game. That's why I chose a short my.cfg file title (exec my.cfg).

Note that the -1 value only works if you have post processing on Med in the graphics settings. You need to use a value that totals -1 when you add it to the value of what the game is running at with the settings you're using. To determine that you type r_postprocessdofmode into the dev console and hit Enter. It will report back what value it's currently at.

I got that tip from a guy that wrote a guide on it in a Steam Forum thread he made. The funny thing was he gloated a lot about how his method worked, and others using a one size fits all -1 example didn't, but he was in fact wrong with the command because it won't report back if you type it cvaradd r_postprocessdofmode as he suggested.

I'm also launching it via a profile I made in the Crimson GUI to enable Vsync. For some reason renaming the exe to x86 added lots of screen tear and broke in game vsync (won't stay enabled). Previously I could run it with no vsync without tear.

It's all good now though, FPS averages 50-60. I really don't get why there's these silly guides having you make a bat file and DL a tool to convert them to exe, when all you need do is rename the exe to x86 and run it in admin mode.

Thanks again.
 
Last edited by a moderator:
Frag Maniac said:
It worked great! I also implemented the cvaradd r_skipadaptiveglare 1 and cvaradd r_postprocessdofmode -1 commands to a my.cfg file I made, and wow, the game looks way better now even on Med settings. The only bummer is the game won't recognize an autoexec.cfg file, so you need to type exec (your cfg name) into the console every time you launch the game. That's why I chose a short my.cfg file title (exec my.cfg).

Note that the -1 value only works if you have post processing on Med in the graphics settings. You need to use a value that totals -1 when you add it to the value of what the game is running at with the settings you're using. To determine that you type r_postprocessdofmode into the dev console and hit Enter. It will report back what value it's currently at.

I got that tip from a guy that wrote a guide on it in a Steam Forum thread he made. The funny thing was he gloated a lot about how his method worked, and others using a one size fits all -1 example didn't, but he was in fact wrong with the command because it won't report back if you type it cvaradd r_postprocessdofmode as he suggested.

I'm also launching it via a profile I made in the Crimson GUI to enable Vsync. For some reason renaming the exe to x86 added lots of screen tear and broke in game vsync (won't stay enabled). Previously I could run it with no vsync without tear.

It's all good now though, FPS averages 50-60. I really don't get why there's these silly guides having you make a bat file and DL a tool to convert them to exe, when all you need do is rename the exe to x86 and run it in admin mode.

Thanks again.
Click to expand...
I'm glad to hear it worked for you and that you can now play it without major issues
 
So far the most stable drivers for me were 16.10.1 and 17.4.3. I hardly ever install "beta" drivers and I recommend exactly the same for you.
 
Komshija said:
So far the most stable drivers for me were 16.10.1 and 17.4.3. I hardly ever install "beta" drivers and I recommend exactly the same for you.
Click to expand...
That's the kind of recommendation that will leave anyone that likes to get games at release struggling through problems often fixed by beta drivers. Surely you must know the real reason they're called beta is MS takes their sweet time approving drivers for WHQL status, and often times it has far more to do with things other than gaming. You can't expect every gamer to wait for WHQL status when it's obvious MS cares more about Xbox than PC. At the end of the day, WHQL doesn't mean much really.
 
You must log in or register to reply here.
Back
Top