I checked the LHM code and (besides finding some areas not not protected by the mutex) I also see that it performs some sort of initialization of the eSIO hardware monitor by enabling additional voltage monitors. Your comment about appearing of new garbled sensors in HWiNFO when starting it after FanControl might point to some issue in LHM. As such, please be patient and as descriptive as possible if you want any chance of this getting resolved.

Please note that all of them provide voluntary support for software you can use for free, and the issue you're having is most likely very difficult to debug / determine its origin unless it was clearly reproducible by everyone (which it sadly is not). HWInfo64 would then also start displaying a lot of new sensors on my NCT6687D which were garbled/incorrect (have readings of 0).Īlso to address PP2012/resudroid: I have noticed that you seem to be a bit pushy in terms of communication with developers of both FanControl and HWI. When HWInfo64 was started after FanControl, it would cause issues with FanControl's ability to, well, control fans. When I had the issue, yes, the start order of FanControl and HWInfo64 did matter in my case. So from my perspective the issue is not clear-cut. The problem PP2012 describes is something that I was able to observe on my system as well (but was fixed for me by updating both HWInfo64 and FanControl, or by magic I don't understand). I have observed LHM clashing with other hardware monitoring tools in the past intermittently, but I never observed HWInfo clashing with others.

To clarify: I'm not affiliated with FanControl but am following the issue thread on github. First of all: Thanks Martin for responding and even showing interest in this issue at all, because it is quite obscure and only shows up for a small portion of users.

FanControl v160 free