FanControl.Releases icon indicating copy to clipboard operation
FanControl.Releases copied to clipboard

FanControl (V227 / Net 4.8) crashes after coming back from sleep/hibernate Win 11

Open Otsomies opened this issue 4 months ago • 5 comments

When coming back from sleep mode FanControl is unresponsive and i have to force shutdown in using Task Manager. This behavior started a while a go and before that it has worked normally even after coming back from sleep.

Windows EventViewer has following logs when coming back from sleep: Error/Application Hang: The program FanControl.exe version 227.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

No logs in FanControl log.txt

Relevant hardware specs and setup Z790 msi tomahawk 13700k rtx 4090 win 11 Home (24H2)

I don't know if this is a duplicate of #2249

Otsomies avatar Aug 05 '25 06:08 Otsomies

Hi.

I have a similar problem: After waking up the PC, it is in a "frozen" state.

Windows 11 system is up to date. The FanControl window opens, in its frozen state. See screenshot. Through my fan names, there is some text that is very hard to see. Clicking on anything with the mouse does not work/respond. The FanControl window can only be completely minimized as an application. Closing the window with the cross also doesn't work/react. FanControl can only be "killed" as a process via the process manager.

In my opinion: The fans spin in this case as if controlled by the UEFI BIOS and are not controlled by FanControl in this case. Perhaps there could be a problem in this direction as well (taking control of the fans primarily by the UEFI BIOS and then after waking up Windows11 from sleep, FanControl no longer receives permission to control the fans).

MoBo name: Gigabyte B550 Gaming X V2 BIOS AMI UEFI: F19g OS: Windows 11 24H2 26100.4946 FanControl: V227 / .NET 4.8

Image

EDIT 1:

I wrote that V227 is up to date, but it wasn't. As of today, V231 is up to date. I'm currently testing V231 and will see - I'll let you know if updating to a newer version helped with my problem.

EDIT 2:

After update to V231, problem/bug was SOLVED !

EDIT 3:

Sorry, I was wrong 😎. After putting the PC to sleep, when I returned to the PC after a few hours and woke up the PC, the FanControl (V231) window was frozen again and the speed control from FanControl also didn't work, and the BIOS apparently took over the control of the fans again. The only difference is that in the FanControl window, two texts are no longer visible at the same time in one field (user-defined FAN name + something else), as it was before. There is only one text. Yesterday I also cleaned the "log.txt" file in the FanControl (portable) folder and after the freezing error occurred, there is only this:

8/16/2025 9:43:29 PM: Update - System.IO.IOException: Operation failed after some time. ---> System.ComponentModel.Win32Exception: A device attached to the system is not functioning
   --- End of inner exception stack trace ---
   at HidSharp.Platform.Windows.NativeMethods.OverlappedOperation(IntPtr ioHandle, IntPtr eventHandle, Int32 eventTimeout, IntPtr closeEventHandle, Boolean overlapResult, NativeOverlapped* overlapped, UInt32& bytesTransferred)
   at HidSharp.Platform.Windows.WinHidStream.Write(Byte[] buffer, Int32 offset, Int32 count)
   at LibreHardwareMonitor.Hardware.Psu.Corsair.UsbApi.SendCommand(HidStream stream, Byte length, Command cmd, Byte arg, Byte[]& replyData) in C:\Users\remme\Documents\Github\FanControl\LibreHardwareMonitor\LibreHardwareMonitorLib\Hardware\Psu\Corsair\CorsairPsu.cs:line 315
   at LibreHardwareMonitor.Hardware.Psu.Corsair.UsbApi.Request(HidStream stream, Command cmd, Byte rail, Byte[]& data) in C:\Users\remme\Documents\Github\FanControl\LibreHardwareMonitor\LibreHardwareMonitorLib\Hardware\Psu\Corsair\CorsairPsu.cs:line 367
   at LibreHardwareMonitor.Hardware.Psu.Corsair.UsbApi.GetValue(HidStream stream, Command cmd, Byte rail) in C:\Users\remme\Documents\Github\FanControl\LibreHardwareMonitor\LibreHardwareMonitorLib\Hardware\Psu\Corsair\CorsairPsu.cs:line 381
   at LibreHardwareMonitor.Hardware.Psu.Corsair.CorsairPsu.<>c__DisplayClass8_0.<Update>b__0(PsuSensor s) in C:\Users\remme\Documents\Github\FanControl\LibreHardwareMonitor\LibreHardwareMonitorLib\Hardware\Psu\Corsair\CorsairPsu.cs:line 76
   at System.Collections.Generic.List`1.ForEach(Action`1 action)
   at LibreHardwareMonitor.Hardware.Psu.Corsair.CorsairPsu.Update() in C:\Users\remme\Documents\Github\FanControl\LibreHardwareMonitor\LibreHardwareMonitorLib\Hardware\Psu\Corsair\CorsairPsu.cs:line 76
   at FanControl.Domain.BackendProviders.LHM.StorageOptimizedUpdateVisitor.VisitHardware(IHardware hardware)
   at LibreHardwareMonitor.Hardware.Computer.Traverse(IVisitor visitor) in C:\Users\remme\Documents\Github\FanControl\LibreHardwareMonitor\LibreHardwareMonitorLib\Hardware\Computer.cs:line 408
   at FanControl.Domain.BackendProviders.LHM.StorageOptimizedUpdateVisitor.VisitComputer(IComputer computer)
   at FanControl.Domain.BackendProviders.LHM.LHMBackendProvider.Update()
   at FanControl.Domain.ComputerAccessLayer.Update()

The error may only be related to the Corsair PSU. I added a plugin to FanControl for the Corsair PSU (RM750i). But even without this plugin, before, FanControl froze when the PC went into sleep mode.

s3n0 avatar Aug 14 '25 16:08 s3n0

I've started having issues waking from sleep. I have it installed via Scoop. I updated the other day and since then every time I wake from sleep the Fan Control interface it open and asking me to confirm changes to my config.

Now, for a few months, whenever I have opened the interface from the sys tray icon and then close the interface window, it has warned me my config has changed and to save, discard or cancel, but I have not changed any settings.

But now is a combination of the interface opening after sleep and asking me to confirm config changes when nothing has changed.

UtopiaOpera avatar Aug 19 '25 08:08 UtopiaOpera

@UtopiaOpera :

Your problem will probably depend on the permissions assigned (on your operating system).

It is also quite possible that you are using the wrong launcher. If you run FanControl non-standardly, it may have a problem finding or accessing the saved configuration file.

If you are using the Portable version and you as a user do not have administrator access to save files (and neither does your application), then this may be a problem. You can try setting FanControl to run with administrator rights. But I do not know if this will solve your problems.

If you are using the Portable version, you need to set the automatic launch of the Portable version in Settings - by activating the option "Start minimized" + also the option "Start at user log in...".

You can also delete the "log.txt" in the FanControl folder. Then raise an error. And after the error(s) are displayed, post this "log.txt" file here in the discussion. Or create your own ISSUE, since your problem is slightly different from the one described here.

s3n0 avatar Aug 19 '25 10:08 s3n0

All the settings suggested were already in place. In settings I noticed language symbol wasn't set - I don't believe it needs to be it just defaults to system lang - but I thought, I'll set it anyway, and I was prompted to save. Well now, when I open the interface and close, I don't get prompted to save zero changes to my profile. I think actually saving (writing) seems to have flushed the persistent nag to save all the time!

Cheers anyway.

UtopiaOpera avatar Aug 19 '25 11:08 UtopiaOpera

All the settings suggested were already in place. In settings I noticed language symbol wasn't set - I don't believe it needs to be it just defaults to system lang - but I thought, I'll set it anyway, and I was prompted to save. Well now, when I open the interface and close, I don't get prompted to save zero changes to my profile. I think actually saving (writing) seems to have flushed the persistent nag to save all the time!

Cheers anyway.

I can confirm that this also works for me. For whatever reason, the language symbol was causing issues for me too. Kudos @UtopiaOpera

Gajotres avatar Sep 16 '25 18:09 Gajotres