FanControl.Releases
FanControl.Releases copied to clipboard
Rem0o
Frequently on system boot, I will get a "Failed to Initialize, expected x sensors, found x" message.
This does not happen every boot.
Not sure what causes it, error log has no recent entries. The only entries in there are when I upgraded my graphics card driver and I forgot to close it, so I got some errors but those were gone after I restarted the program.
I have tried refreshing sensors detection quite a number of times, also played around with the enabled sensors. This only started happening a few weeks ago as well. I can press cancel and then the program behaves as normal, except that I have to save my configuration again.
The only thing I can think of is that I did a few graphic card swaps since I started using the program, but those aren't that recent. I'm running the latest version. Any ideas?
This can happen if the app starts too soon and some sensors are not available still. Have you setup some kind of delay in the app in the settings page?
It's on 5 seconds, I will try to increase it to 10. Should it be higher than that still?
Today on boot, with a 30 second delay I am still getting the error. I can only get rid of this error by pressing cancel, saving the configuration and then restarting the program. Any idea?
Today it was 76 out of 77 (so 1 missing), but I think this number changes once in a while. I'll note it down if it's a different number next time.
Do you have something external like a hard drive or something that might change from one time to another?
This has been consistently happening to me on every version since i first installed (157 i think), same with MOBO sensors (had 1 - 5 sensors on first setup, now i sometimes get 1, sometimes get none), just seems arbitrary what fan control detects (or rather LHM). I check back every now and then to see if its any better but this app isnt usable for me currently.
I have the same issue after updating to the latest version. Mine says 62 out of 63 I'm not sure why this happens.
I found a reliable way to have it miss one sensor is starting Fan Control while Stable Diffusion (NMKD) is running and generating images. For what it's worth.
been having the same issue for a number of versions, thought it was something to do with my config after an update removed a sensor or something, so i wiped it and started a new one
worked for a couple reboots, then the issue started again. i think it happens more often after an update?
Hi everyone, I have the same issue. I've found a workaround : I lauch HWMonitor then I lauch FanControl and had no issues for two days. I'd really like FanControl to initialise correctly, if this get fix I will send a donation because it is the best piece of software I've ever used.
Same here. lhm, do shit, but I found this about two years ago. When I first launch hwmonitor, then fan control everything works. Yet im too lazy to do this every time, so for now fck it. My mobo asus b350, asus rx 580 and r5 1600.
I'm also very lazy, do you know if I can autolaunch HWMonitor ? Because it has admin privileges I don't think if it can be.
@echo off start "" C:\FanControl\HWMonitor_x64.exe timeout /t 7 taskkill /f /im HWMonitor_x64.exe exit
delete txt upload it to windows create script and voila
@echo off start "" C:\FanControl\HWMonitor_x64.exe timeout /t 7 taskkill /f /im HWMonitor_x64.exe exitdelete txt upload it to windows create script and voila
Hi, thank you for your response. I need some more informations please, do I have to put HWMonitor on the FanControl folder ? How can I "upload" the .xml file to windows ? I have set FanControl auto lauchning to 60s delay so I have time to log to Windows and open HWMonitor, is it going to work ?
- first import this file, hwinfo.xml into Task Scheduler, right click import
- i have my script and hwinfo in fancontrol folder
and it should be everything