Temp sensor oddity with v160

[m1k3g3tz]

MSI MPG x570 gamin pro carbon wifi sensor #1 (motherboard temp)

after updating to v160 this morning, seeing odd behavior where this sensor will randomly read -1c and fans tied to that sensor will stop other software - msi center, BIOS, and Goverlay (via openhardwaremonitor) show temps correctly - only seems to be affecting fancontrol

reverted to v159, issue not recurring.

if you need any configs, screenshots, or other pertinent information, please let me know.

[rameel]

I have encountered the exact same problem, which involves the temperature sensor displaying a reading of -1 degree on the MSI MEG X570 motherboard, starting from version 160, despite the correct data being shown on the graph.

[Rem0o]

@rameel does anything updates at all or does the software is "stuck" with nothing updating?

[rameel]

From time to time, the actual temperature is displayed, for example, 49 for 1-2 seconds, then again -1. Sometimes, it shows the correct temperature for quite a long time.

[rameel]

Mostly, this is observed with the chipset sensor, and occasionally with the VRM sensor.

[rameel]

Today I noticed that even on the graph, the value jumps according to what is displayed in numbers.

[Rem0o]

The problem seems to be with the sensor reading itself. It should not randomly read -1.

Are you getting the same thing in https://github.com/LibreHardwareMonitor/LibreHardwareMonitor ?

[rameel]

I checked, LibreHardwareMonitor displays correctly.

[Rem0o]

Put the LibreHardwareMonitorLib.dll from LHM into FanControl (overwrite it). I'm (FanControl) using the latest commit, whereas the release (LHM) uses a much older build.

[rameel]

Thanks! It's working now!

[Rem0o]

@rameel which means some update in LHM somehow broke your sensor reading.

[rameel]

It seems like that

[TheMightyJonez]

@Rem0o this is very similar to the issue I emailed you about a couple months ago with my X570-E. I tried this fix but my T Sensor values are also jumping in Libre Hardware Monitor... I do not observe this fluctuation. in HWinfo64 or Armory Crate.

Any suggestions? Do you have old .dlls I could use?

[Rem0o]

@TheMightyJonez you can do the same thing as @rameel and use the LHMLib dll from the release of LHM here: https://github.com/LibreHardwareMonitor/LibreHardwareMonitor/releases/tag/v0.9.2

[TheMightyJonez]

That’s what I did but the problem still persists. Like I said, my values fluctuate in LHM but not HWinfo64.

On Wed, Sep 6, 2023 at 5:40 PM Rem0o @.***> wrote:

@TheMightyJonez https://github.com/TheMightyJonez you can do the same thing as @rameel https://github.com/rameel and use the LHMLib dll from the release of LHM here: https://github.com/LibreHardwareMonitor/LibreHardwareMonitor/releases/tag/v0.9.2

— Reply to this email directly, view it on GitHub https://github.com/Rem0o/FanControl.Releases/issues/1834#issuecomment-1709219242, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARD7G2M7XXD3Y2D6LAGO7YDXZD3UZANCNFSM6AAAAAAZJXJ7OQ . You are receiving this because you were mentioned.Message ID: @.***>

[TheMightyJonez]

@TheMightyJonez you can do the same thing as @rameel and use the LHMLib dll from the release of LHM here: https://github.com/LibreHardwareMonitor/LibreHardwareMonitor/releases/tag/v0.9.2

Both Fan Control and LibreHardwareMonitor are unstable whereas any other tool I use, HWinfo64 or Asus Armory Crate, are completely stable. Any suggestions? @Rem0o

[DoctorEw]

Latest Fan Control v172 still has the erroneous temp sensor readings, the LibreHardwareMonitorLib.dll from v0.9.2 is still fixing the issue. Adding for posterity in case others are running across the issue.

[m1k3g3tz]

Yes, I have had to do the dll swap as well.

On Tue, Oct 17, 2023, 9:14 AM DoctorEw @.***> wrote:

Latest Fan Control v172 still has the erroneous temp sensor readings, the LibreHardwareMonitorLib.dll from v0.9.2 is still fixing the issue. Adding for posterity in case others are running across the issue.

— Reply to this email directly, view it on GitHub https://github.com/Rem0o/FanControl.Releases/issues/1834#issuecomment-1766395514, or unsubscribe https://github.com/notifications/unsubscribe-auth/BAUELUNVSFM3YBYEJQZT5IDX72AC7AVCNFSM6AAAAAAZJXJ7OSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRWGM4TKNJRGQ . You are receiving this because you authored the thread.Message ID: @.***>