-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fan Control breaking some HWiNFO64 sensor readings #64
Comments
Hi, Send a screenshot of the sources you got enabled in FanControl. There may be a lock issue for the ITE chip access. If you untick the motherboard source in FanControl, same issue? I don't think this has something to do with the plugin. The plugin reads the Windows Registry to get the HWInfo data. There is no direct contact between the two. HWInfo writes its data to the registry, FanControl reads the registry. I don't see how the plugin/fancontrol could "break" HWInfo this way. |
PSA to anyone reading: DO NOT untick the mobo source if you don't want to break your Fan Control config! Otherwise, make sure you have a current backup of your Fan Control folder before editing the sources so you can drop the backup in once you break the current config. |
Disabling the MB sensor was a troubleshooting step, not a proposed solution. You should run LibraHardwareMonitor without FC. The issue might be, as Rémi posted, an ITE chip access clash between LHM and HWinfo64. If it happens with LHM, then it should be reported there. It could be due to a change they introduced in a recent build. FC does not interact directly with the hardware. This is done thru LHM dll (or some of the plugins), which gets updated in FC thru the updates. https://github.com/LibreHardwareMonitor/LibreHardwareMonitor It has nothing to do with HWinfo plugin. |
Thanks for your insights. However, this does seem like a FC issue because FC is the software packaging LHM. So while I agree it's wise to test LHM directly to see if it's the problem, which I will do tomorrow, the primary issue, if LHM is the problem, is that FC is shipping something breaking HWiNFO64 sensors only when FC starts (calls LHM I guess). If it's LHM, then it seems LHM was probably updated in FC v2.09, which then started this issue on my system. Otherwise, I wouldn't have seen this issue because it only recently started and I recently updated to v2.09. I am aware Rem0o didn't intend disabling the mobo as a fix. But Rem0o, and to be frank, you, seem to be incorrectly dismissing this issue without much consideration. I didn't create this report in the HWinfo plugin git, I created it in the FC one, and Rem0o moved it here last night. |
If LHM is the problem:
|
Did you use a prior version of FanControl with your build before with this same motherboard/setup without an issue? |
The only recent change I can spot which involve IT87952E is the change from reading 6 to 10 voltage registers. However the motherboards added to require this change only read "9" registers, so I don't know why 10 was set Looking at https://github.com/torvalds/linux/blob/aef25be35d23ec768eed08bfcf7ca3cf9685bc28/drivers/hwmon/it87.c#L255, it seems like the 10th register isn't 0x20 + 10, but there is an offset from 0x28 to 0x2F, which LHM blindly +1 his way through the registers from 0x20. |
I compiled a quick version of LHM that uses the proper voltage registers. Use either the .NET 8 or normal (4.8) version depending on your version of FanControl. Make sure to rename the dll to only "LibrehardwareMonitorLib.dll" depending on which one you take from the zip. Copy it over your fancontrol installation folder. |
Yes:
Thanks! But this breaks Fan Control and conflicts with HWiNFO64. Please take a look at the screenshots and FC log file below. I tested many different configurations:
FC v2.09
FC v2.08
For now, until a fix is pushed by LHM/FC:
If users experiencing this problem must run FC v2.09:
Error message and log.txt when running FC v2.09 with LHM v0.9.4.0 voltage registers fix build you shared: LOG.TXT
|
I will create a bug report at LHM in the coming days unless you can better describe the issue and would prefer to create it yourself. In either case, I will note your comments about IT87952E and the voltage registers. |
The current nightly LHM v0.9.5.0 has the same problem as v0.9.4.0 (the shipped version, not what you shared above).
|
@321MBT Try the .net 4.8 ( non-net8) LHMLib I compiled with FanControl V209 .NET4.8 |
Thanks. I tried what you suggested and used V209 .NET4.8 with LHMLib v0.9.4.0 .NET4.8 that you complied for me. It breaks in the same way as using V209 .NET8 with the shipped LHMLib v0.9.4.0 .NET8 So, for now, I am using FC V208 .NET8 with the standard shipped LHMLib v0.9.3.0 .NET8. It's the most recent combo that works for me without restarting HWiNFO64 and FC after the first start. Let me know if I can help by testing other builds. |
Is it only the readings under the ITE8689 in HWInfo that break? Or both ITE chips. My only other idea would be arround this change:: |
Just the first chip (ITE IT8689E) reading breaks, while ITE IT87952E isn't affected. Here are both chips reading correctly with FC V208 and the standard shipped LHMLib 0.9.3.0: Here's an example of both chips with either:
Feel free to let me know if I can help in any way. I love Fan Control, so I'm happy to help. |
Hi,
Over the past week or so, I have been experiencing an issue where Fan Control breaks some HWiNFO64 sensor readings. I'm unsure if I should report this issue to HWiNFO64 or Fan Control, so I posted this at HWiNFO64 forum because it's the affected software (link), and I'm CC'ing the report here.
Please let me know if this has been reported previously, if I can provide assistance, and whether a fix is in the works.
Issue:
Fan Control setup:
My System Specs:
Temp Fix:
Detailed Explanation:
This script silently calls ReStarting_HWiNFO64_FanControl.bat, which:
[*] This must occur after killing Fan Control if the HWiNFO64 Gadget and HWiNFO64 plugin are used for Fan Control's sensor readings. Otherwise, Fan Control will get stuck in a loop, and you'll have to kill the Fan Control process manually.
Alternate Solution:
If you're experiencing this issue upon login and don't want to use these scripts:
Running the batch files:
CODE:
ReLaunch_HWiNFO64_FanControl.bat
ReStarting_HWiNFO64_FanControl.bat
The text was updated successfully, but these errors were encountered: