Rem0o/FanControl.HWInfo

HWInfo sensor value went missing from registry

zurlox opened this issue · 4 comments

Really liking 'Fan Control' and the plugins that are available. But seem to be having issues with the HWInfo plugin.
Plugin loads and sensors appear in the app briefly then Fan Control throws an error, all HWInfo sensor values disappear and the below log entries are recorded:

23/10/2022 6:07:05 PM: Unhandled exception in FanControl v1.0.0.0
23/10/2022 6:07:05 PM: System.Exception: HWInfo sensor value went missing from registry

I've tried reloading the sensors, replaced the .dll file from the one available on AppVeyor, however still getting the unhandled exception
Any thoughts on what I can try to fix this?
Thank you very much and keep up the awesome work!

Rem0o commented

Few things to keep in mind.

  1. limit the quantity of sensors you export from HWInfo to the ones you use.
  2. this setting will remove 0 rpm fans if left unchecked and may cause this issue.
    image

Thank you for your prompt reply.
I've made sure that 'show all fans' options is enabled, and I've reduced the sensor quantity considerably.
The error message is still displayed in FanControl when the plugin is enabled.
Is there maybe anything else I can try to resolve?
Thank you again,

I seem to have the same issue, also none of the fixes work. I had to revert back to the custom version that still uses shared memory to get it working again.

01.12.2022 20:42:24: System.Exception: Could not create instance of FanControl.Plugins.IPlugin
at FanControl.Domain.PluginService.CreateInstance[T](Type type)
at FanControl.Domain.PluginService.LoadTypes[T](Assembly assembly)
01.12.2022 20:42:24: System.Exception: Could not create instance of FanControl.Plugins.IPlugin2
at FanControl.Domain.PluginService.CreateInstance[T](Type type)
at FanControl.Domain.PluginService.LoadTypes[T](Assembly assembly)
01.12.2022 20:42:24: HWInfo sensor value went missing from registry: HWInfo/Corsair Platinum/CPU Cooler Coolant Temperature/°C
01.12.2022 20:42:27: HWInfo sensor value went missing from registry: HWInfo/Corsair Platinum/CPU Cooler Coolant Temperature/°C
01.12.2022 20:42:28: HWInfo sensor value went missing from registry: HWInfo/Corsair Platinum/CPU Cooler Coolant Temperature/°C
01.12.2022 20:42:30: HWInfo sensor value went missing from registry: HWInfo/Corsair Platinum/CPU Cooler Coolant Temperature/°C
01.12.2022 20:42:31: HWInfo sensor value went missing from registry: HWInfo/Corsair Platinum/CPU Cooler Coolant Temperature/°C
01.12.2022 20:42:32: HWInfo sensor value went missing from registry: HWInfo/Corsair Platinum/CPU Cooler Coolant Temperature/°C
01.12.2022 20:42:33: HWInfo sensor value went missing from registry: HWInfo/Corsair Platinum/CPU Cooler Coolant Temperature/°C
01.12.2022 20:42:34: HWInfo sensor value went missing from registry: HWInfo/Corsair Platinum/CPU Cooler Coolant Temperature/°C
01.12.2022 20:42:35: HWInfo sensor value went missing from registry: HWInfo/Corsair Platinum/CPU Cooler Coolant Temperature/°C
01.12.2022 20:42:36: Unhandled exception in FanControl v1.0.0.0
01.12.2022 20:42:36: System.Exception: HWInfo sensor value went missing from registry: HWInfo/Corsair Platinum/CPU Cooler Coolant Temperature/°C
at FanControl.HWInfo.HWInfoPlugin.Update()
at FanControl.Domain.BackendProviders.Plugin.PluginBackendProvider.Update()
at System.Collections.Generic.List1.ForEach(Action1 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)

Rem0o commented

HWInfo sensor value went missing from registry: HWInfo/Corsair Platinum/CPU Cooler Coolant Temperature/

Seems like at some point HWInfo stopped reporting that value for more than 10 seconds. Is that expected?