HWInfo sensors were changed during operation
See original GitHub issueI’m getting a recurring issue where I receive the following error in Fan Control (v120). Of note I’m reading from an ASUS Z690 EC module and HWinfo does warn that there might be issues. Refreshing sensor detection in Fan Control fixes the issue so maybe a refresh-on-error could workaround it?
16-Jul-22 19:48:39: Unhandled exception in FanControl v1.0.0.0
16-Jul-22 19:48:39: System.Exception: HWInfo sensors were changed during operation
at FanControl.HWInfo.HWInfoPlugin.Update() in C:\projects\fancontrol-hwinfo\HWInfoPlugin.cs:line 68
at FanControl.Domain.BackendProviders.Plugin.PluginBackendProvider.Update()
at System.Collections.Generic.List1.ForEach(Action
1 action)
at FanControl.Domain.ComputerAccessLayer.Update()
at FanControl.Domain.ApplicationClock.DoActions()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
Issue Analytics
- State:
- Created a year ago
- Comments:6 (2 by maintainers)
Top GitHub Comments
I too was experiencing the same issue. But i think i’ve found out the solution. In HWinfo Sensors settings, i enabled “show all fans (includding stopped or not present)” and “accept negative temperatures”. I’ts been 16 hours now without the error popping up. My guess is that the hwinfo widget somehow glitches momentarely not showing the sensors and Fancontrol gets triggered by that.
Thank you for the explanation, It makes so much sense now. It was driving me crazy until i stumbled upon that setting in hwinfo.
In my case, the fans do not stop. I monitor NZXT Kraken Z73’s Liquid temp, fan and pump speeds. Yet somehow, hwinfo was randomly removing the sensor from the registry for just a moment, making FanCntrol to trigger the error. I suspect that this could be due to a communication error between hwinfo and the AIO’s usb controller (but that’s irrelevant to fancontrol).