Monday, November 30th 2015

AMD Radeon Software Crimson Edition Incorrect Fan Speed Issue Being Fixed

AMD's ambitious Radeon Sofware Crimson Edition drivers are seeing its first user experience issue in the form of a fan-speed bug. The driver, in some cases, spins graphics card fans up to 100%, and in others, the fan-speed is locked at 30% regardless of load. Over the past weekend, AMD acknowledged the issue and is tasked with a hotfix driver scheduled for release later today.
Add your own comment

47 Comments on AMD Radeon Software Crimson Edition Incorrect Fan Speed Issue Being Fixed

#26
Bansaku
64KThere's been some more news on this

arstechnica.com/gadgets/2015/11/amds-new-crimson-drivers-accused-of-burning-up-video-cards/

Apparently the GPUs do throttle when they climb to more than 90 degrees but there is some concern that other components on the cards like VRMs are getting damaged. This reminds me of a couple of years ago when certain Nvidia drivers were blamed for damaging cards the same way.
Thankfully both my 4 case fans blowing air across the cards, and the massive heatsink and PCB, my HIS IceX 2 cooler does an excellent job keeping everything cool. My GPUs did throttle, but I assumed that was due to the new Frame-rate Cap feature I had set for 59fps as it throttles the same when temps are at 61'C. In fact, I noticed that 99.9% of new AAA games run at a steady 60fps with GPU throttling @ 59fps when I run at 1600P upscaling at maxed settings. Sadly the only game that doesn't is the Witcher 3, which hovers in the low 50s.

:toast:
Posted on Reply
#28
Divide Overflow
A horrible oversight to be sure, but I guess I'm not affected like so many others claim to be. I can run benches and stress test my 290X on the Crimson drivers without so much as making my card break a sweat. Based on my own observations, I'm somewhat skeptical of *all* these "dead card" claims.
Posted on Reply
#29
Bansaku
Static~ChargeThere is a workaround for the locked fan speed problem:

imgur.com/a/o04Gl
Doesn't work for me, even after a restart.

Guess I have to keep using Afterburner and set the speed to manual until AMD fixes this.

Not sure if it's related, but I tried running Firestrike and my second monitor connected to the same card went all garbled and wonky. I normally have that one off when in Windows (and gaming), now I am going to see of running games causes this as well. Sigh...
Posted on Reply
#30
eidairaman1
The Exiled Airman
no issues here (on a 290), Had issues with the 15.7.1 series preventing checkdisk from running
Posted on Reply
#31
Aquinus
Resident Wat-man
eidairaman1no issues here (on a 290), Had issues with the 15.7.1 series preventing checkdisk from running
My 390 seems to have not been impacted either. There is a point though when the GPU itself throttles back clocks and voltage despite the driver. When current drops, so does VRM temps, so I think that sounds kind of weird. I think if some cards failed, it's probably because they were running on the edge to begin with because it shouldn't just simply die because it runs hot but, not any hotter than when it starts throttling otherwise. Correlation doesn't always imply causation people, just because it failed when it ran a little hotter than normal doesn't mean that it wouldn't have done that even if the driver wasn't responsible.

Either way, this was a huge slip up, don't get me wrong. AMD screwed up hardcore on this one but, to blame drivers for GPUs failing for running hotter than normal doesn't mean that the card wouldn't have failed if something other than the driver made it run hot enough to throttle. Lemons are lemons, the fact that the driver made the conditions right changes nothing. RMA the sucker, end of story, because I would call it a hardware defect if safeguards didn't kick in or if something was already starting to fail.
64KApparently the GPUs do throttle when they climb to more than 90 degrees but there is some concern that other components on the cards like VRMs are getting damaged. This reminds me of a couple of years ago when certain Nvidia drivers were blamed for damaging cards the same way.
At least they're not bursting into flames. :laugh:
Posted on Reply
#32
ThE_MaD_ShOt
No issues here but I use Afterburner to control the fan curve.
Posted on Reply
#33
HumanSmoke
BansakuThanks AMD! If my cards die, YOU WILL be hearing from me, and possibly hundreds of others.

:mad:
Good luck with that. I think you'll find you had to accept the Catalyst EULA before installation, which should read some like:
THE SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. AMD DISCLAIMS ALL WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, THAT THE SOFTWARE WILL RUN UNINTERRUPTED OR ERROR-FREE OR WARRANTIES ARISING FROM CUSTOM OF TRADE OR COURSE OF USAGE. THE ENTIRE RISK ASSOCIATED WITH THE USE OF THE SOFTWARE IS ASSUMED BY YOU. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to You.
Posted on Reply
#34
Pill Monster
64KThere's been some more news on this

arstechnica.com/gadgets/2015/11/amds-new-crimson-drivers-accused-of-burning-up-video-cards/

Apparently the GPUs do throttle when they climb to more than 90 degrees but there is some concern that other components on the cards like VRMs are getting damaged. This reminds me of a couple of years ago when certain Nvidia drivers were blamed for damaging cards the same way.
That's unlikely since thermal throttling is hardware controlled on both GPU and VRM.
Although the GPU itself throttles when it overheats, there's speculation that other components on the cards, such as the VRMs, can still be damaged.
arstechnica.com/gadgets/2015/11/amds-new-crimson-drivers-accused-of-burning-up-video-cards/
Speculation.....
Posted on Reply
#35
Divide Overflow
Looks like there is a fix posted on their driver site.
I wonder if 15.11.1 Beta is a rollback or if there is there something new from the previous beta's posted.
Posted on Reply
#36
Aquinus
Resident Wat-man
support.amd.com/en-us/kb-articles/Pages/November-30-hotfix.aspx
AMDResolved Issues with AMD Radeon Software Crimson Edition 15.11.1 Update
  • [82050] Star Wars™: Battlefront - Snow flickers in a few locations in the game
  • [82240] Star Wars™: Battlefront - Sky rendering may be broken in some game locations
  • [82645] Fallout 4 - The compass may flicker during gameplay on AMD Radeon R9 390 series products. We continue to investigate the issue with AMD Radeon R9 290 and AMD Radeon R9 295X2 series products
  • [82667] Star Wars™: Battlefront - Shadowy textures are visible around hills/structures/caves
  • [81890] Just Cause 3 - Texture corruption may be experienced during gameplay
  • [54874] Call of Duty: Black Ops 3 - Poor AMD Crossfire™ performance may be experienced
  • [82338] The driver installation may fail while installing the ACP component
  • [82426] The font size in Chinese language installations may be too small
  • [82438] The label range values in some AMD Freesync™ installations may be incorrect
  • [82536] The Radeon Settings dropbox does not close when it is clicked on a second time
  • [82603] The AMD Overdrive™ fan settings is always set to ON after first edit on reboot
  • [82586] Language shows up as Chinese Simplified when Chinese Traditional is selected in Windows® 7
  • [82656] Radeon Settings crashes on the Display tab when cloning a display via HDMI on some notebooks
  • [82671] Overdrive™ fan speed is reset to Manual on exiting from a 3D game or application
  • [82766] Radeon Settings does not get upgraded in some install scenarios
  • [82691] AMD Overdrive™ cannot revert to default settings in some situations
Sounds like I didn't have an issue because I never touch "Overdrive™".
Posted on Reply
#37
arbiter
Prima.VeraA lot of dead cards complains on AMD forums and others. Hilarious readings, lol.
AMD shoot itself in the balls. Again.
This will be forgotten in 2 months or so but same people forgot about this will have no problem recalling same issue on nvidia side.
Posted on Reply
#38
eidairaman1
The Exiled Airman
Aquinussupport.amd.com/en-us/kb-articles/Pages/November-30-hotfix.aspx


Sounds like I didn't have an issue because I never touch "Overdrive™".
I dont fuss with it either. I oc my cpu the old fashioned way- 4.8GHz gaming stable. If I ever intend on ocing the GPU (Probably in 5 years) Ill use Trixx or Afterburner... from what you said it sounds like a glitch in overdrive
Posted on Reply
#39
de.das.dude
Pro Indian Modder
this wasnt there the first time i used it but i was tweaking with the fan settings and it always stays stuck at 100% on boot.
Posted on Reply
#40
eidairaman1
The Exiled Airman
de.das.dudethis wasnt there the first time i used it but i was tweaking with the fan settings and it always stays stuck at 100% on boot.
The fix is out if you need it lol. My card before crimson would do a fan self test every so often where it would rev to 100% at Post and then drop lower after windows started. So to me it was a firmware safeguard lol

Heck I dont even remove the old drivers anymore. I just update on top of the old ones, unlike the W98-Vista Days. I always set a restore point incase the chipset driver or Gpu drivers are screwy.
Posted on Reply
#41
H82LUZ73
BansakuDoesn't work for me, even after a restart.

Guess I have to keep using Afterburner and set the speed to manual until AMD fixes this.

Not sure if it's related, but I tried running Firestrike and my second monitor connected to the same card went all garbled and wonky. I normally have that one off when in Windows (and gaming), now I am going to see of running games causes this as well. Sigh...
quick question ,Did you have Afterburner installed before the new drivers?It is well known to not have After-burner installed while installing Amd drivers ,It mucks up the fan profile settings in the drivers.
Posted on Reply
#42
de.das.dude
Pro Indian Modder
eidairaman1The fix is out if you need it lol. My card before crimson would do a fan self test every so often where it would rev to 100% at Post and then drop lower after windows started. So to me it was a firmware safeguard lol

Heck I dont even remove the old drivers anymore. I just update on top of the old ones, unlike the W98-Vista Days. I always set a restore point incase the chipset driver or Gpu drivers are screwy.
i never remove completely. AINT NOBODY GOT TIME FO DAT.

ill try to find the f ix.


EDIT: Goddamn! 330MB!
Posted on Reply
#43
HumanSmoke
de.das.dudeEDIT: Goddamn! 330MB!
Might want to save the bandwidth just in case. The hotfix seems to be dropping GPU usage (and thus clocks) in a fairly arbitrary manner.
Posted on Reply
#44
Aquinus
Resident Wat-man
HumanSmokeMight want to save the bandwidth just in case. The hotfix seems to be dropping GPU usage (and thus clocks) in a fairly arbitrary manner.
Strange. When I have v-sync off and CPU isn't a bottleneck, I get full clocks. When I turn v-sync on (rightfully so,) it runs at lower clocks. I can't say I've experienced this issue other than the issue with Elite: Dangerous which I think is unrelated.
Posted on Reply
#45
HumanSmoke
AquinusStrange. When I have v-sync off and CPU isn't a bottleneck, I get full clocks. When I turn v-sync on (rightfully so,) it runs at lower clocks. I can't say I've experienced this issue other than the issue with Elite: Dangerous which I think is unrelated.
Well, I did say it was arbitrary. I just mentioned it because some of the less sensationalist forums I frequent have been making reference to the issue. Glad to hear you are unaffected.
Posted on Reply
#46
eidairaman1
The Exiled Airman
de.das.dudei never remove completely. AINT NOBODY GOT TIME FO DAT.

ill try to find the f ix.


EDIT: Goddamn! 330MB!
i put those betas, in seem ok.
Posted on Reply
#47
Filip Georgievski
My 2 6770s are glad I installed Crimson.
Temps dropped and I'm happy.
Only thing I had to do is use Trixx for gaming as I use my own custom setup on cards ( clocks and fans).
I tried gaming on auto fans and it seams to work well, since my fans got up to 70% in BF3, Far Cry 3, and other games.
Posted on Reply
Add your own comment
Nov 22nd, 2024 17:10 EST change timezone

New Forum Posts

Popular Reviews

Controversial News Posts