Rem0o / FanControl.Releases

This is the release repository for Fan Control, a highly customizable fan controlling software for Windows.
Other
14.54k stars 453 forks source link

Fan Sensor (it8613e) Detection Errors #2739

Open guifaloki11 opened 2 months ago

guifaloki11 commented 2 months ago

Describe the bug Everytime i put my PC to sleep my cooler sensors stop working and i get this error:

"These errors occurred while restoring the configuration:

  • Missing speed sensor: /lpc/it8613e/fan/0 - Fan#1
  • Missing speed sensor: /lpc/it8613e/fan/0 - Fan#2
  • Missing speed sensor: /lpc/it8613e/fan/0 - Fan#3

If this error occurs during startup, try increasing the startup delay."

Even after resetting through the software, the cooler sensors remain undetected. They only work again after restarting the PC.

Is there a log.txt file next to FanControl.exe with recent date entries? log.txt

alexeykorevin commented 2 months ago

Same problem. I have been using the program for about a year, there have never been such errors before.

Rem0o commented 2 months ago

Do you get the same behavior with https://github.com/LibreHardwareMonitor/LibreHardwareMonitor/actions/runs/11068128415 ?

If you go to sleep, does it stops detecting/monitoring your fan speeds?

alexeykorevin commented 2 months ago

Do you get the same behavior with https://github.com/LibreHardwareMonitor/LibreHardwareMonitor/actions/runs/11068128415 ?

If you go to sleep, does it stops detecting/monitoring your fan speeds?

This problem occurs when the PC starts up

Rem0o commented 2 months ago

@alexeykorevin you kinda hijacked @guifaloki11 's issue thread. I was asking him which mentioned happening out of sleep. However the same test applies to you. You should also try to increase the startup delay in the program.

alexeykorevin commented 2 months ago

@alexeykorevin you kinda hijacked @guifaloki11 's issue thread. I was asking him which mentioned happening out of sleep. However the same test applies to you. You should also try to increase the startup delay in the program.

The problem went away after upgrading to version 205