[Reddit] Crimson Driver Fanspeed Issue, Some GPUs Reported Dead

[SithSolo1]

Were you able to see what your temps got up to?

If the game and card runs fine after bumping up the fan speed I wouldn't worry about it.

I never saw it go above 92F when it was locked at 20% but the clocks were in the low 800s and dropping. Once the fan was auto adjusting again the temp was similar but the clock was steady at 947 and my framerate was pegged at 60 again.

I'm sure the card is fine, I was just testing to see if I had the issue that was being reported so I didnt run it that long at 20%.

 

[Techhog]

Well, there goes any chance of the bad driver myth ever dying. Ugh.

 

[KaRLiToS]

Well, there goes any chance of the bad driver myth ever dying. Ugh.

 

[psolord]

I just noticed my fan profile I set in Afterburner wasnt working. My fan got set at 45% so I had no lasting problems but still strange.

i mean, am i they only who uses his own fan profile with msi afterburner?

nvidia, amd i don't care.

i am the one who chooses my fan speeds.

my 980's have never once overheated.

nor have my 280x's

I use a custom fan profile in AB as well.

I uploaded a video yesterday, trying to show to people why a single 7950 is better than 5850 crossfire. And no that is not obvious to everybody. I am getting a lot of questions regarding 5850 crossfire nowadays, which I find weird.

(nsfw wallpaper warning)

Assassin's Creed Unity 1920x1080 custom 7950 @1.1Ghz Q9550 @4GHz

no need to click the link though

Here's what MSI Afterburner registered regarding fan speed and temps during the run



All the above is somewhat irrelevant however. A driver should work out of the box, without users having to know how to setup custom profiles, or what MSI Afterburner is.

In any case for me the driver works fine.

I am intrigued to test the system without a custom profile in place now.

 

[Actaeon]

I never saw it go above 92F when it was locked at 20% but the clocks were in the low 800s and dropping. Once the fan was auto adjusting again the temp was similar but the clock was steady at 947 and my framerate was pegged at 60 again.

I'm sure the card is fine, I was just testing to see if I had the issue that was being reported so I didnt run it that long at 20%.

I think the Hawaii's limit is 95C, so you should be ok and nothing to worry about. Good thing you caught it in time though. While that is the limit, I'm sure it doesn't like to sit there for extended periods of time.

 

[Actaeon]

FWIW, I couldn't reproduce it on my own setup. Tri-X 290X. I tried a number of different things to see if I can get the fans to lock at 20% but nope. My fan would always ramp up and GPU core never got warmer than 75F.

So bummer for the people who ran into this, but for anyone concerned they may have burnt something out before you manually changed profiles its possible you weren't effected either.

 

[tential]

FWIW, I couldn't reproduce it on my own setup. Tri-X 290X. I tried a number of different things to see if I can get the fans to lock at 20% but nope. My fan would always ramp up and GPU core never got warmer than 75F.

So bummer for the people who ran into this, but for anyone concerned they may have burnt something out before you manually changed profiles its possible you weren't effected either.

It's not everyone it just seems it happened to some people.

 

[crisium]

My fury x clocks fluctuate like crazy with crimson. before it was always locked @ 1050 in any 3d app. now all over the place causing stutters and drops.

This is the problem I get. It's the opposite of the OP when you think about it since my fan is working perfectly yet I get throttling.

I just use the 2D Clock settings in ASUS GPU Tweak and it fixes the issue.

Just create a second profile where your 2D clocks are as close to your 3D clocks as you can get. Of course make sure to remember to switch back after gaming.

 

[n0x1ous]

This is the problem I get. It's the opposite of the OP when you think about it since my fan is working perfectly yet I get throttling.

I just use the 2D Clock settings in ASUS GPU Tweak and it fixes the issue.

Just create a second profile where your 2D clocks are as close to your 3D clocks as you can get. Of course make sure to remember to switch back after gaming.

yeah its really bizaree especially on fury x since the fan never goes higher than 15% ever anyway. typically would top out at 50C now with all this clock fluctuation its never over 32C in game.

thanks for the tip - will give that try tonight. for ****s sake AMD i shouldn't have to have all these 3rd party tools installed just to make your d***flagship part work right.

 

[tential]

yeah its really bizaree especially on fury x since the fan never goes higher than 15% ever anyway. typically would top out at 50C now with all this clock fluctuation its never over 32C in game.

thanks for the tip - will give that try tonight. for ****s sake AMD i shouldn't have to have all these 3rd party tools installed just to make your d***flagship part work right.

Honestly what tools within AMD drivers am I supposed to use? Pretty much, anything I've EVER needed to change, I needed a third party tool to do....

 

[Final8ty]

I personally have not run into a single issue with Crimson, i have never touched the fan speed in Overdrive and AB has never been on my Windows 10 install and my fans ramp up and down like they should.

 

[RussianSensation]

Good thing they noticed the problem very quickly.

There is a temporary fix in place
http://imgur.com/a/o04Gl

Step 1 - Press Global Settings

Step 2 - Press Global Overdrive Settings

Step 3 - Scroll down and press the button next to the fan speeds, if it's set to ON that means it'll be locked at the standard 20% speed

Step 4 - Make sure it states OFF if you want your fan speeds to be automatic. Alternatively, you can set a base right to the right if you don't want automatic speeds. Just leave it set to ON.

 

[3DVagabond]

Well, throttle kicks in on chip temp, if VRM's or something else hit their failure temp before the chip hits its throttle temp, then bye bye card.

I knew I should have waited before installing these, but luckily I confirmed my fan is still working properly. Way to work on that driver rep guys. :thumbsup:

Source that this is what happened?

 

[stahlhart]

Nvidia is not on topic either in this thread or in this subforum. Last warning.
-- stahlhart

 

[Despoiler]

Source that this is what happened?

At least on the 290(x) and newer cards the VRMs are good to 150C. The chip thermal protection therefore kicks in well before the VRMs would pop.

 

[3DVagabond]

At least on the 290(x) and newer cards the VRMs are good to 150C. The chip thermal protection therefore kicks in well before the VRMs would pop.

This is my understanding too that the GPU would heat up and throttle before the VRM's were damaged. I know people like to point at VRM temps as an issue (well at least with AMD because they report the temps in GPUz), but the reality is they have a lot of headroom as far as temps go.

AFAIK the only card that had issues with VRM's popping was the GTX 590 when over volt and over clocked and that was fixed with a new bios. Even cards with notoriously high VRM temps haven't shown any reliability issues.

This is the 690 under load stock clocks and voltage. People even O/C these cards and I've never seen reports of blown VRM's.

 

[3DVagabond]

http://support.amd.com/en-us/download/desktop?os=Windows+10+-+64

Link for the fixed drivers.

 

[VirtualLarry]

Nope, you can already here the meme ramp up. :/ Definitely not a good thing for a new software suite.

I LOLed!

 

[omek]

Good thing they noticed the problem very quickly.

There is a temporary fix in place
http://imgur.com/a/o04Gl

Ah, so it's probably only happening when Overdrive is enabled. I never use OD, straight to Afterburner.

i mean, am i they only who uses his own fan profile with msi afterburner?

nvidia, amd i don't care.

i am the one who chooses my fan speeds.

my 980's have never once overheated.

nor have my 280x's

Definitely not. I don't think I've ever let any of my cards use their own fan profile unless it's a media PC. Been methodical about that since the RivaTuner days.

 

[biostud]

After trying crimson drivers I started getting bsods in world of warships, then reverted back to catalyst and now I get bsods with these drivers as well. Also happens when everything runs stock, so I'm wondering what happened...

 

[n0x1ous]

I clean installed the hotfix tonight with DDU clean install. never had the fan issue (not that it would matter on Fury X anyway) but just wanted to report that the clock fluctuations are still present. It seems like its some new power algorithm to lower the clock to what is needed to hit vsync. it runs full clocks in 3d marks but I've mostly been playing Fallout 4 with its locked 60hz. i have not edited the ini to remove that limit, but it still seems like there should be a driver option to run full clocks regardless. people dont buy huge discreet gpu's for their power efficiency.....

 

[Azix]

After trying crimson drivers I started getting bsods in world of warships, then reverted back to catalyst and now I get bsods with these drivers as well. Also happens when everything runs stock, so I'm wondering what happened...

if they updated the game that would potentially cause problems across drivers. I'd use DDU to be sure but maybe something got broken besides drivers/game.

 

[biostud]

if they updated the game that would potentially cause problems across drivers. I'd use DDU to be sure but maybe something got broken besides drivers/game.

I've used DDU, when going back to Catalyst and there has been no update of the game client.