Unable to adjust CPU fan

Lewis_20

Commendable
Oct 27, 2016
5
0
1,510
Hi,

Firstly here's my current setup

asus H170 Pro gaming motherboard
i5 6600k
Cooler Master 212 evo

My case fans aren't connected to the mobo and have their own fan controller so not fussed about these. The problem i'm having is my CPU cooler is constantly running at around 1600rpm regardless of load.

I've tried to adjust in the Bios, no effect unless I swith it to DC mode but from what i understand this is a legacy setting and best avoided?

Also attempted to use Ai Suite lll to adjust fan but no luck there either, firstly the CPU fan graph is greyed out. Followed instructions from this post http://www.tomshardware.co.uk/answers/id-1717544/asus-fan-xpert-control-cpu-fan-running-max-speed.html#14857554
to adjust settings and this fixes the graph in AI SUite, yet the changes i make still appear to have no effect on the rpm of the cpu fan.
I've updated the BIOS with no observable effect.

When running fan Xpert 3 in AI Suite I'll most of the time get an error part way through the bench marking or fan tuning process saying 'abnormal program termination' then it quits out.

This is currently what I'm seeing in fan Xpert 3
22b1e80a5c.png


despite what you can see on the graph, the fan is still running at 1600rpm

Mainly wanting to adjust this as my PC currently sounds like a monster and surely it shouldn't be running at almost full speed straight after startup and whilst idling?
 
Solution
This has already been mentioned but Asus boards have a smart fan control setting in BIOS , you should set this to auto .

However the ai suite & speed fan screens are puzzling.

Where have you heard DC control is a legacy setting & shouldn't be used??

That's absolute claptrap mate , its simply a way of controlling 2 & 3 pin fans that don't support pwm control.

There's nothing wrong with using it at all if it works for you..

The 212 evo fan is a 4 pin though & should support 600-1600rpm via pwm so there is some underlying issue here.

Use DC for the time being though if it solves your problem , there will be no ill effects


Something looks wrong here. It says controllable range of the fan is 101% to 100% which doesn't make any sense. I would go back to the BIOS, reset it and then calibrate the fans via the Q fan control settings. Also double check that the fan connector is seated properly just as a double check.
 


I restored the default values in the bios with no effect, do you mean clear CMOS too? the connector is seated as correctly as it could be.
 
I would clear everything just to be safe including CMOS. Did you calibrate the fans in the BIOS Q fan control? I know on mine if I didn't do the calibration the minimum rpm of the fans was much higher, after calibration I could lower them down. The strange thing is that the AI Suite software should override the BIOS settings when it loads yet it is still not affecting the fan speed. Maybe try installing speedfan and see if you can take control of it, if nothing is controlling it then it could be a faulty connector on the fan.
 
So i have cleared CMOS and had no change, downloaded SpeedFan and attempted to play around with that, haven't seen any change at all in CPU fan speed. Also as the screenshot below shows, it's got the CPU fan saying it's running at 0%, and increasing this makes no difference, even though it says above that, that its running at 1642rpm

23a6cc35a8.png
 
This has already been mentioned but Asus boards have a smart fan control setting in BIOS , you should set this to auto .

However the ai suite & speed fan screens are puzzling.

Where have you heard DC control is a legacy setting & shouldn't be used??

That's absolute claptrap mate , its simply a way of controlling 2 & 3 pin fans that don't support pwm control.

There's nothing wrong with using it at all if it works for you..

The 212 evo fan is a 4 pin though & should support 600-1600rpm via pwm so there is some underlying issue here.

Use DC for the time being though if it solves your problem , there will be no ill effects


 
Solution
Thanks for the info Matt, I've gone with using DC for now and will see how we get on. I feel like i've spent most of the day trying to get this to work using pwm so it must be a hardware issue that I'm coming up against.

I'll contact the seller and see what they can suggest