On my Asus Rampage V, I use the ASUS EC chip to report temperature value on my liquid coolant (its a wired temperature sensor that you can place anywhere. I simply taped it to the outside of the tubing and insulated it, works well).
I'm not concerned about lag or CPU usage as I put it on a conservative 20 second interval on sensor refreshes. Periodically, sometimes the sensor bugs and returns a -115C or 116C value but returns to normal on the next read. But eventually, within a couple days, it gets stuck at -115C. There are 3 T_Sensor values. Hot-plugging in the wired sensor to a different header doesn't fix the issue, and neither does using a different wired sensor.
AI Suite, Asus's program for doing some motherboard specific stuff (fans, sensors, volt setting, clock setting, etc) also reports the T_Sensor values, but when its bugged in hwinfo, its bugged in AI Suite as well, simply reporting the last known valid value, or nothing at all.
I wanted to know if this could be a hwinfo-related issue that triggers the bug, and if it could be fixed.
I'll update to the newest 5.xx version, currently on 4.64-2530. I'm on 5.02 now.
https://dl.dropboxusercontent.com/u/9768004/temp/HWiNFO64.DBG
https://dl.dropboxusercontent.com/u/9768004/temp/SSATENETH-PC.HTM
I'm not concerned about lag or CPU usage as I put it on a conservative 20 second interval on sensor refreshes. Periodically, sometimes the sensor bugs and returns a -115C or 116C value but returns to normal on the next read. But eventually, within a couple days, it gets stuck at -115C. There are 3 T_Sensor values. Hot-plugging in the wired sensor to a different header doesn't fix the issue, and neither does using a different wired sensor.
AI Suite, Asus's program for doing some motherboard specific stuff (fans, sensors, volt setting, clock setting, etc) also reports the T_Sensor values, but when its bugged in hwinfo, its bugged in AI Suite as well, simply reporting the last known valid value, or nothing at all.
I wanted to know if this could be a hwinfo-related issue that triggers the bug, and if it could be fixed.
https://dl.dropboxusercontent.com/u/9768004/temp/HWiNFO64.DBG
https://dl.dropboxusercontent.com/u/9768004/temp/SSATENETH-PC.HTM