"Users Claim That Crimson Software Killed Their AMD GPUs, AMD Acknowledges.."

I had this problem with 15.11 drivers on one of my 290 cards (XFX with stock cooler (second card),main one is Powercolor 290x PCS+ was fine). The fan was stuck on 20%. But i have not noticed in the Crimson drivers the situation as I installed water cooling on that card two weeks ago. Need to check.

 

They keep making themselves look more and more incompetent. I've never seen anything like it. AMD........ bad one.

 

I had this since 15.7!

I had this issue since 15.7! -_-


Story:
My R290X started overheating and tripping the whole system in September after I upgraded to Catalyst 15.7.1.
Initially I thought it was a power supply as the error I was getting was related to power surges and I was not monitoring GPU temperatures before then.

The fan speed in default mode would not go further than 20%. The maximum temp in automatic mode is 95C. The system cuts out if the GPU temp will go over 90C so I have to run it in Override mode now which sucks as it was fine before.
I upgraded the drivers to 15.9 and later to the first Crimson and it's still the same.

 

AMD sucks

Now, where have I heard something like this before???

http://forums.guru3d.com/showthread.php?t=316831

 

Death To Nvidia 99999$ Cards!
Death To AMD 99999°C Cards!

All Hail Intel Graphics!

 

Yeah the only difference is that Nvidia immediately pulled that driver down. Where as AMD is not doing that for whatever reason.

 

Well.. Glad I noticed this issue the same day where I installed the new "Crimson" software. It wasn't the biggest issue for me, since I go into the "Overdrive" section quite often and saw the fan speed being locked to 21%.. Though, my sympathies to the "casual" user who might not have noticed. Or even worse, lost their card because of this bug.

 

No probs here with my Asus Strix R9-285 OC I sit right next to my case so I hear the fans spin up when things get a little toasty

I do wish AMD had given us a proper fan profile setup like that of AfterBurner and Trixx the one speed fits all is not a good way to go

 

The reason the Crimsons got through is because somebody at AMD pushed them to get through--they were not ready for release--not even close--but somebody was pushing it to meet AMD's self-imposed annual deadline that they started last year with the "Omega" drivers (which were just another Catalyst release with a sporty new name for marketing purposes.) The Crimson interface as it now sits is feature deficient and buggy, and that's putting it mildly. Fortunately, the 15.11.1 Catalysts are still available from the main driver page and retain 100% functionality, and are terrific Win10 drivers. (I don't have any Win10 driver crashes--the opposite of what I hear said of the green team's Win10 driver efforts *cough*)

The actual Crimson driver set, which runs fine inside the CCC and retains 100% of its function when installed into the CCC shell through the device manager, is a very good driver. It's the Crimson interface that, in a word, stinks. The Crimson interface is the kind of thing you'd expect to see in a mere game console--not in a PC--imho.

I always run Afterburner alongside the Catalysts and have never seen a problem--what I set in AB is mirrored in the Catalysts. And, btw, when you set the fan profile to automatic in AB, in the CCC the fan setting reverts to "manual fan, 50%"--but that is only because the CCC is now taking its fan marching orders from AB--the fan will still follow the AB profile, whatever that may be. It's only when you disable the AB fan profile or uninstall AB that the CCC once again controls the fan according to the CCC fan settings you configured.

In the Crimson interface, fan speed and GPU overclocking are now set individually within each game profile. Supposedly. But the Crimson interface has ripped out resolution switching...! Imagine buying a $600 GPU and being unable to switch screen resolutions through its driver interface! (I can't imagine buying a $100 GPU and not having that level of control in the drivers.) Lots of other functionality has been removed, too. It's just too sad.

"If you can't do it right AMD then don't do it at all!" (Reminds me of Win8 & Metro!)

 

https://twitter.com/AMD_UK/status/671322269461909505

 

lol i reported this as soon as the crimson came out... sad that you guys are so late... im curious howmany have burned their GPU

 

And its been that way since the ATI Radeon days. Thats 15+ years! Nothing has changed.

 

Easily the best post in that matter

 

I doubt I would want that car when it comes out the rear end.

 

I clicked the button with windows icon in msi-ab now it keeps auto fan profiles.

 

I read through this thread and I still don't get it, can someone either confirm what I think or correct me please, because from what I understand this happens only when you want to OC the card and create custom profiles in the Overdrive section.

So it goes something like this, when you install the drivers and just leave everything as is then things will be fine, but if you go into the Overdrive Overclock section and mess around in there then just ignore the 20% fan speed limit leave it untouched, THEN **** hits the fan (ooh, there's a pun there I do believe)


I mean there's a whole big warning where you literally have to accept, that says you risk some things when you do this.... so then you go on and do it and forget to move the fan slider up from 20% ??
Is that how it's going down, or am I not understanding how it works

 

This is exactly why us Nvidia/MS users don't want forced driver updates through MS or GFE.

Although the likelihood of actual real damage is very low it has happened before and will no doubt happen again.

It's the reason most enthusiasts only do Manual Updates, as we like to read change logs and view other enthusiastic peoples opinions first before doing anything.

We all know AMD drivers aren't the best but missing bugs like this is inexcusable, whether it really did break anyone's card or not is questionable but possible none the less.

 

Oh wow AMD actually acknowledged an issue! KIND support, even if this oversight causes dead cards.

I'm still waiting for nVIDIA to acknowledge EEPROM corruption causing dead displays. I see a comment was deleted on the first page.

https://forums.geforce.com/default/...g-samsung-and-lg-notebook-lcd-display-panels/

Maybe I'll use my dead display as a mirror this winter!

 

AMD keeps shooting themselves in the foot.

 

Actually this is probably a reason supportive of controlled updates. I mean first of all Experience doesn't enforce you to update immediately, you can choose not to install the latest update. But if there is an issue, Nvidia can pull the only source of the driver off the internet. Where as with the current fashion, people may come across this crimson driver on Guru3D (Hilbert actually already pulled it -- cudos on him for doing that) or whatever site, download it and never read anything about the fan control issues -- AMD is left powerless to completely pull it.

Not that I support controlled updates entirely, but I think in this particular situation it would be better.