• 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

~>Dg<~ said:
how do you set custom fan profile in crimson my boys rig needs to be set but cant find the option to set to 60 percent.
Click to expand...

If you want to set it global, go into gaming tab and then select Global settings and then Global OverDrive and setup in there..

If you want to setup by Application add the games .exe and then click on profile and go into Profile OverDrive.
 
nashathedog said:
The further into Tomb Raider the worse the amount of stutter time becomes, It's no longer playable plus I'm also getting visual errors like this:

https://www.dropbox.com/s/g6qry390xbxl63i/ROTTR 2016-01-31 16-47-29-93.jpg?dl=0
Click to expand...

Errors like that are a sign of bad overclocking! Way back on my 7950s I pushed them and I had errors like this in Alan Wake I needed to add more voltage but instead I just lowered my overclock on both memory and Core.

If you have a GPU with 4GB or less dont use Very High Textures this is for 6GB+ cards.. I also noticed AF 16x in this game is very demanding for some strange reason lower this down to 4x or 8x
 
shankly1985 said:
Errors like that are a sign of bad overclocking! Way back on my 7950s I pushed them and I had errors like this in Alan Wake I needed to add more voltage but instead I just lowered my overclock on both memory and Core.

If you have a GPU with 4GB or less dont use Very High Textures this is for 6GB+ cards.. I also noticed AF 16x in this game is very demanding for some strange reason lower this down to 4x or 8x
Click to expand...

It doesn't matter what settings it has the same issues, I've tried them all and currently have very conservative settings ie FXaa nothing on very high several turned off etcetera, As for overclocks I do not overclock however I have got 10 mhz added to my Fury via Afterburner so that it controls the downclocking issue the Crimson drivers cause. It runs everything fine and it appears that it is driver or game issues with Fury cards nothing else. I have AF at x4, Hair is on not very high, Nothing is on very high. Since reaching the Siberean base map the entire area is a stutter fest for me.
 
Last edited:
r7slayer said:
Right guys anyone have a fix for this issue? Iv'e installed the latest Crimson driver after booting into safe mode using DDU to get rid of the old drivers then installed latest crimson drivers. Everything was working fine however ive since done a fresh install of windows 10, installed the crimson drivers again (fresh install no need for DDU)

Ive then installed MSI afterburner and tried to get it to load my overclock profiles which kept black screening me for some reason and had to restart. In the crimson drivers i enabled overdrive? To give the 50% power boost and then the overclocks wouldn't blackscreen me. So thought right back to normal again. I then enabled the option to start MSI on boot and apply overclocks and now i have the issue again blackscreens however it does it right as im loading to desktop right just before it. Ive un-installed MSI Afterburner and that didn't work so then i tried un-installing Crimson drivers and now i can load to desktop fine.

So im guessing Crimson doesn't like MSI Afterburner and overclocking? People having similar issues on the net from googling no fix though.
Click to expand...

I have this issue and its because the overclock I run needs voltage increase.

Whats happening is crimson/overdrive is holding onto the increased clocks but not voltage set in afterburner. Then when you start up the clocks increase but not the voltage and you get a blackscreen.

I have to reset my overclock when I shut down and apply the profile before I start gaming. If you forget you have to go through what you say
safe mode>DDU>re-install.

Very very annoying
 
All the moaning here is with people OCing there cards and that counts for less than 5% of all GPU users.
This game runs great with current drivers if you just leave them alone.

Wait for the fix if you want to start playing with catalyst settings.

People forget that with AMD not having to release a driver update for this game and yet perform better than the competition at higher res with their specific driver update is quite an achievement and a credit to AMD drivers in general.
 
Ferrari100 said:
All the moaning here is with people OCing there cards and that counts for less than 5% of all GPU users.
This game runs great with current drivers if you just leave them alone.

Wait for the fix if you want to start playing with catalyst settings.

People forget that with AMD not having to release a driver update for this game and yet perform better than the competition at higher res with their specific driver update is quite an achievement and a credit to AMD drivers in general.
Click to expand...

From what I've read TR runs fine on everything except Fury cards. It's atrocious on them and it's nothing to do with overclocking. So no there's no credit due when there flagship cards aren't working right.
 
nashathedog said:
From what I've read TR runs fine on everything except Fury cards. It's atrocious on them and it's nothing to do with overclocking. So no there's no credit due when there flagship cards aren't working right.
Click to expand...

Actually, I have a 390X and a 5820k and it runs far from well on my system. Lots of stuttering and low framerate problems. You have to remember that pcper tested a very small section at the beginning of the game about 10-15 seconds long which is hardly representative of the performance the user can expect.
 
Brizzles said:
Same for me on a single 390X, and it has continued after the Siberian map :(
Click to expand...

ltron said:
Actually, I have a 390X and a 5820k and it runs far from well on my system. Lots of stuttering and low framerate problems. You have to remember that pcper tested a very small section at the beginning of the game about 10-15 seconds long which is hardly representative of the performance the user can expect.
Click to expand...

That's bad news I thought it was fine on Grenada etc. I've stopped playing now as there's no point in going any further when it's this bad, I went back and tried it without my 10 mhz overclock but it didn't change anything,
Interestingly enough the core clocks didn't downclock so I'll leave it at stock and try some other titles again to see if the clocks still drop down to the 3-6 hundred range like they were before I tried locking them with AB, I haven't tried without the 10 mhz overclock since before we got the crimson fix.
The weekends over now anyway so I'll get back to it once they give us the fixed driver.
 
Last edited:
fs123 said:
It's not just the Fiji cards.
I get severe pausing/stutter in Rise of the Tombraider when textures are set to very high on my 290X and VRAM hits 3.9GB. On High the VRAM usage drops to 3.3GB and everything seems fine. Looks like the game is trying to use more than 4GB on Very High settings.
Hopefully they can fix the issue with drivers since I remember Black Ops 3 did the same on release.
Click to expand...

No problems here on a 390X 8GB, so makes sense 4GB is the limiting factor at the moment.
 
need this driver ASAP, sick and tired of seeing this on 16.1 Crimson. Not sure why GPUz is seeing the driver version as 15.8 as I'm on 16.1 but hey ho. Worst driver ever for crossfire.

24655495701_331954434f_h.jpg
 
fs123 said:
It's not just the Fiji cards.
I get severe pausing/stutter in Rise of the Tombraider when textures are set to very high on my 290X and VRAM hits 3.9GB. On High the VRAM usage drops to 3.3GB and everything seems fine. Looks like the game is trying to use more than 4GB on Very High settings.
Hopefully they can fix the issue with drivers since I remember Black Ops 3 did the same on release.
Click to expand...

Thats odd.
Due to no Xfire support i have been playing ROTR on a single 290x with a clock of 1100/1300 for around 3 hours.
Its a steady 27-30Fps (turned hair off)
No issues what so ever. Oh and this is on 4k Btw.
 
have done shanks, this is the only result I get. Crossfire on 16.1's is just an all round **** mate, desperate to get away from it. I've been going back to pre-Crimson at times as they feel so much better.
 
Things may have change and I could be wrong but I believe if the setting isn't under 'CurrentControlSet' then it isn't currently being used.

Usually you'd have 'ControlSet001' and 'ControlSet002' in the registry and then on boot it dynamically loads one of these as 'CurrentControlSet' which is then used by Windows for that boot session.

Check the settings in 'HKLM\System\Select' to see the value of the 'Current' set it is using. And if you do have more than one 'ControlSet00x' add that value in the same place in each of them, reboot and then check 'CurrentControlSet' to see if it gets loaded.


edit: In other news, RotTR seems to be running pretty well for me (Win10, Fury (+5% o/c), i7 3770k @4.4GHz), maxed settings apart from only FXAA and double buffer vsync, 1080p. Though I've only got up to the part where you make the first camp fire. I am also still using the ClockBlocker tool, not tried it with out it but I just default run it now when gaming.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom