Search results

Well, it actually was aquasuite. I thought that I had disabled its internal hardware monitoring, but after everything else was killed off, I took at look at aquasuite's config and its hw-monitoring was enabled. So unless another bug comes up, seems to be a mistake on my part, sorry for that.

Irregularly, the onboard sensors spit out wrong values for just 1 cycle, e.g. CPU/MB/MOS-temp jumps from normal to zero, negative or 100+ and then back to normal on the next polling. Also, the longer HWiNFO runs, the more nonsense-sensors appear (like "AMD TSI 0", also like multiple times)...

Nothing that would really stand out, only software I've been using for quite some time without any problems regarding HWiNFO. MSI Afterburner, RTSS, ThrottleStop, VMware, some gaming clients

No, they don't, LHW-service has been running for ~5 minutes now.

As expected the values are normal again, but that's always the case after a reboot. What I noticed is that the LHW service seems to read at least one of the values in question (the MOS one) properly. I'll leave the system at this state (LHW-service stopped) for a couple of hours and see if...

Hello, since a couple of days, maybe for two weeks now, some mainboard temperatures are misreported as being negative. Only certain temperatures are affected, e.g. mainboard/CPU and, curiously, only one of two MOS values. I observed this bug on Windows 11 first and, after a new installation...

Hey, I changed my PC's hard drives today and noticed that for one of my SSDs (Samsung SSD 850 Pro 256GB) the informations in the "Main"-window and the S.M.A.R.T. sensor values are missing. CrystalDiskInfo and smartctl can read the drive without problems, just HWiNFO64 doesn't. If you have use...

Just noticed HWiNFO used quite much memory on my machine too (~750 MB after 12 hours of running), Hyper-V is disabled, disabling GPU monitoring seems to fix the memory leak.

Interesting, every board review says its using an ISL69269, like here on AnandTech (https://www.anandtech.com/show/15781/the-asrock-z490-taichi-motherboard-review/9) and TechPowerUp (https://www.techpowerup.com/review/asrock-z490-taichi/4.html) Not that I care much about these small details...

Works far better now, the values seem good (although they don't really add up, but I assume it's how the sensor reports it), don't need to reboot anymore, only that it says ISL69138 now and there's a second VRM with only temperatures and input voltage showing.

Here are both debug logs (with and without the ISL69269 showing up) with the new version you just sent.

After a reboot both ISL69269 show up again, only to disappear on every startup afterwards, plus I noticed the sensor detection takes a few moments longer than on the first startup after the reboot.

Now the ISL69269 isn't showing up at all, just on first start of your provided version it showed up twice, but the values were still incorrect.

No, no monitoring tools running besides HWiNFO, I also already tried closing every running program possible (and restarting HWiNFO afterwards), didn't fix the readings.

Hey, I recently noticed that the VRM sensor readings of the ISL69269 on my board are finally showing up, but, as the title says, are of no use. I attached the debug file and to screenshots to show what's going on. Thanks in advance

I don't really think that they want to hide higher MOS temperatures, but as the name M2_1_TEMP hints it seems to be have been intended to be used for M.2 temperature measuring, but I agree, it looks quite suspicious as any other sensors reports the values straight without any further...

I found it when I decompiled A-Tuning's main executable and looked for the references to M2_1_TEMP. At one of those references it multiplied the sensor value by 0.8, which I then tried out with various MOS temperatures and compared with A-Tuning's displayed values.

It seems like ASRock multiplicates a few temperatures by 0.8, which seems to be correctly as when I apply that to the values shown by HWiNFO they always are equal to the values shown by A-Tuning. This applys to three sensors as far as I know (internally called M2_1_TEMP, M2_2_TEMP and...

Do you maybe have any other monitoring tools running? You could try to download Process Hacker (https://processhacker.sourceforge.io/downloads.php), run it as admin, open "Find handles or DLLs" in the "Hacker"-Menu and search for "Access_ISABUS.HTP.Method" and see if outputs any process besides...

The Vcore voltage is now correct and the fan is named correcly, but the MOS2 temperature is now off A-Tuning's value by 8 to to 9°C. The second NCT6796D disappeared and shows an NCT5585D instead with some values A-Tuning also reports like CPU Standby 1 voltage and VCC PLL voltage, but those...