Fan control sensor works only if I start HW Monitor

[Kogakukan]

Hi all,

First of all huge thanks for your help. I have a B450 Asus gaming plus motherboard, and I have this issue since I reinstall Windows.

Right after boot or when waking the computer from boot, Fan Control will show my case fans spinning at 9000 rpm or some other ridiculous value and the speed control will be stuck at 0%. Manually changing the speed will do nothing.

Refreshing sensors will throw a detection error and either remove those fans or keep them while showing no values.

The only thing that works is, with Fan Control open, running HWMonitor. Once HWMonitor loads and starts showing values, Fan Control will start showing normal values for the case fans and I can control them again.

Do you hava any ideas why guys and how can I fix this ? THX

[vdub12]

I have this exact same issue with my Pump RPM.

Mines on an ASUS B450M.

The Pump RPM will be stuck at 20 and can't be controlled. Once I open HWMonitor I get a correct RPM reading and I can then control the pump. I have just gotten in the habit of opening HWMonitor when I first boot up.

My Pump runs off my CPU fan header on the motherboard. Everything else runs off a Commander Pro and works perfect. I am not using any of my other motherboard headers.

[WGOS]

Got the same issue with all of my fans on TUF GAMING B450-PLUS II

[XPFalcon]

I have a brand new ASUS B450M-A II with fresh install of Win10, I have a similar issue. Fan Control loads at startup but gives very high speed reading for fans which is definitely incorrect. Temp readings are correct. I noticed that if I start Armoury Crate before the delayed Fan Control loads, then Fan Control works correctly. I can close Armoury Crate and Fan Control continues to work correctly. I would prefer to get rid of Armoury crate altogether. Not sure how to investigate further.

[AndMJ]

Got same issue on TUF GAMING B450-PLUS II too

[Bender2k]

Same issue here with the ASUS B450M-K II

I have to start the ASUS Armoury Crate Software and switch to the Fan Control Tab once or - what i learned here - starting HWMonitor once also fixes it and i can control my Fans until the next reboot.

Disabling all ASUS services in msconfig did not fix it. Also the option "Embedded EC (ASUS)" makes no difference. (tbh i even dont know what this is)

I'm on 145. Would be nice if this can be fixed as apart from that your tool is awesome.

[telejoshi]

Same here! Can somebody help please? Without this thread I would've never guessed, because in the beginning it showed right speeds and I thought it happens randomly.

ASUS A320M board. As soon as I start HWMonitor it shows right speeds

/edit: trying to start and kill HWMonitor via batch now. Deinstalling HWMonitor didn't help, without it it never works

[Bender2k]

Same here! Can somebody help please? Without this thread I would've never guessed, because in the beginning it showed right speeds and I thought it happens randomly.

ASUS A320M board. As soon as I start HWMonitor it shows right speeds

/edit: trying to start and kill HWMonitor via batch now. Deinstalling HWMonitor didn't help, without it it never works

Unfortunately no one wants to fix that bug even if so much people are affected :(

[telejoshi]

I've found a workaround. I'm using Scheduled Tasks of Windows to start a batch file on user logon. FanControl is starting with a delay of 30 seconds. Works so far!

The batch file:

@echo off
start "" c:\hwmonitor\HWMonitor_x64.exe 
@ping -n 7 localhost> nul
taskkill /f /im HWMonitor_x64.exe 
EXIT

(It starts HWMonitor, sleeps 7 seconds and then kills it. The ping is being used for sleeping - didn't find a better working solution)

[Bender2k]

This wont help when the PC was in standby or hibernate. After that its broken again.

[telejoshi]

I think you can add a scheduled task for that too

[AltugOS]

Same issue here with ASUS TUF GAMING B450-PLUS II. Would love to have a solution rather than a workaround for this problem. I guess imma keep researching.

[vdub12]

I've found a workaround. I'm using Scheduled Tasks of Windows to start a batch file on user logon. FanControl is starting with a delay of 30 seconds. Works so far!

The batch file:

@echo off
start "" c:\hwmonitor\HWMonitor_x64.exe 
@ping -n 7 localhost> nul
taskkill /f /im HWMonitor_x64.exe 
EXIT

(It starts HWMonitor, sleeps 7 seconds and then kills it. The ping is being used for sleeping - didn't find a better working solution)

Do it this way.

@echo off
start "" c:\hwmonitor\HWMonitor_x64.exe 
timeout /t 7
taskkill /f /im HWMonitor_x64.exe 
exit

Great workaround.

[telejoshi]

Great workaround.

Thank you. Somehow, timeout didn't work, sleep neither. It's sure worth a try. Besides of that it's dirty, is there any downside with using ping?

[gustavomgama]

Im yet to use the solutions presented here. What I did was drag a shortcut of HWMonitor into shell::startup and added a startup delay on fancontrol, works fine.

[git0rhero]

You can also use CPU-Z with parameter "-txt=filename" instead of HWMonitor for this workaround, so you don't have close the GUI everytime after Autostart.