NaN with HWiNFO plugin
lgraak opened this issue · 9 comments
Having an issue where win using the HWiNFO plugin, just getting NaN as the data from HWiNFO. FanControl itself isn't seeing the temp sensor that's connecting to my water temp. Would like to run my radiator fans off what the water temp is, not cpu or gpu temp.
Made sure HWiNFO gadget settings are correct.
HWInfo, while running, exports these sensors values into the registry at this address:
Computer\HKEY_CURRENT_USER\Software\HWiNFO64\VSB
Like so:
What do you get?
I exported it out and saved as a txt file.
You exported basically everything? Try and only export the temperature sensors you need like t_sensor.
"Sensor502"="ASUS EC: ASUS "
"Label502"="T_Sensor"
"Value502"="84.2 °F"
"ValueRaw502"="84.2"
"Color502"="004080"
Looks like it's an issue with gpu items. Removed those items from the gadget and it seems to fix the issue
4/15/2023 7:31:00 PM: System.Exception: HWInfo sensors failed: HWInfo/GPU [#0]: NVIDIA GeForce RTX 4080: /GPU Performance Limiters/, HWInfo/GPU [#0]: NVIDIA GeForce RTX 4080: /Performance Limit - Power/, HWInfo/GPU [#0]: NVIDIA GeForce RTX 4080: /Performance Limit - Thermal/, HWInfo/GPU [#0]: NVIDIA GeForce RTX 4080: /Performance Limit - Reliability Voltage/, HWInfo/GPU [#0]: NVIDIA GeForce RTX 4080: /Performance Limit - Max Operating Voltage/, HWInfo/GPU [#0]: NVIDIA GeForce RTX 4080: /Performance Limit - Utilization/, HWInfo/GPU [#0]: NVIDIA GeForce RTX 4080: /Performance Limit - SLI GPUBoost Sync/ at FanControl.HWInfo.HWInfoPlugin.Update() at FanControl.Domain.BackendProviders.Plugin.PluginBackendProvider.Update() at FanControl.Domain.ComputerAccessLayer.<>c.<Update>b__33_0(IBackendProvider x) 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 --- at FanControl.Domain.ApplicationClock.<>c__DisplayClass10_0.<DoActions>b__0() 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)
I had a similar issue when swapping out a hard drive (usually requires me to re-select sensors) but this time it got stuck in a loop when I removed the old and new hard drives (leaving just my M.2s; new hard drive wasn't compatible & old wasn't worth the hassle to back put in at the moment). I could interact with most of the interface, but the actions (new configuration, refresh sensor, etc.) didn't seem to do anything.
I managed to resolve it by 1) stopping the process, 2) renaming the active configuration file, 3) starting the program again, and 4) manually "loading" the renamed configuration file. I was then able to re-select the sensors like before.