View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002620||SpeedFan||Fan control||public||2016-12-21 20:01||2016-12-21 20:01|
|Platform||OS||Windows 7 64bit||OS Version||SP1|
|Product Version||4.45 beta|
|Target Version||Fixed in Version||4.45 beta|
|Summary||0002620: ATI fan speed stuck at 35%|
|Description||Attempting to adjust the speed of my GPU fan to anything less than 35% results in the following error message:|
ATI Video Card at $00 msg : error in SETPWMINTERNAL
Thereafter, the fan will be locked at 35% until SpeedFan is restarted. This could result in the GPU overheating later.
|Steps To Reproduce||1) Start SpeedFan.|
2) Set GPU fan speed to 34% or lower.
|Additional Information||I submitted a report earlier too.|
P.S. Thanks for implementing ATI GPU support. I've been hoping for it for a long time.
|Tags||No tags attached.|
|Motherboard Model||Asus M4A785TD-M EVO|
|Video Card Model||Sapphire Radeon HD4770|
I never experienced this myself, nor was ever reported by any other user. In order to investigate what's causing the issue on your configuration, please, send me a SEND REPORT (INFO tab) after the error has been shown.
P.S.: don't worry about the video card overheating. It will never overheat because the ATI driver will speed up the fan if needed :-)
I did send a report before, but I sent another one, with the ID of this bug in the notes.
I wouldn't be surprised if this problem is specific to my model of graphics card. I bought it because it has a better heatsink than the other designs that were available at the time, but the fan control has never worked right (it spins up and down with little apparent relationship to temperature when left to control itself).
||Thank you for the report. I just sent you a new beta. Please, send me a new SEND REPORT from every new beta, trying to reproduce the issue.|
||You have a new beta. I was wondering if setting the current fan speed higher than 35% is working.|
||As long as the speed remains above 35% then it works perfectly.|
||I think I found the reason. The driver is returning an odd answer to a command. I will send you a new beta that should fix this issue.|
||You have a new beta :-)|
||This issue is fixed.|