Search results

It could cause excessive disk activity. Might be better to write less frequent. Default HWiNFO polling period is 2000 ms.

Please attach the HWiNFO Debug File capturing that situation: https://www.hwinfo.com/forum/threads/read-this-before-submitting-a-report.241/

Aquasuite should be able to read all HWiNFO sensor data exported via Shared Memory.

Thanks! I have no idea why it flags it as positive and the details are certainly secret. Their Defender policy is really weird, for example they flagged the vulnerable WinRing0 driver (even though they knew for years very well how dangerous it is), but 1 day later pulled the block. They never...

This happens from time to time with Defender. Several other software occasionally becomes flagged.

https://www.virustotal.com/gui/file/4ccdd0a95ada77d6d84d1a6c7b732857350f53d04ca2f4a78d61a067e544ad50/detection

That's certainly a false positive. I'm wondering why it flags it only for you, otherwise would already have thousands of reports. Try to update the Defender database via Windows Update.

You can write some simple tool or script that would export the data read in required format into registry as specified here and it will show in HWiNFO.

Only ASUS ASTRAL are capable of this.

That's certainly a false positive. Maybe that's the reason why also automatic update fails. I have tried now to download via Edge and it didn't report any problem. What exact virus does it report? Can you try to download from alternate site, e.g. SourceForge?

Please try a manual update if that will work.

Do you maybe use MSI Afterburner with the HWiNFO plugin? In such case, MSI AB might prevent HWiNFO from terminating and finalizing the update. Can you try a manual update - download v8.25 and start manually or overwrite the file.

So does version 8.24 work for you and only v8.25 Beta throws that error? Try to disable the "Persistent Driver" option in HWiNFO settings - Driver Management Also, are you maybe using some antivirus that might be blocking HWiNFO?

Older AMD CPUs (before Zen) don't have a reliable internal temperature sensor. In many cases the sensor returns nonsense values and cannot be trusted. So it's better to rely on the external mainboard sensors (ITE in your case).

Thanks, you too!

Well, honestly I don't know. Both values are provided by proprietary interfaces about which we don't have any further details.

https://www.hwinfo.com/forum/threads/read-this-before-submitting-a-report.241/

First try to do a "Reset GPU I2C Cache" from main HWiNFO settings. If that won't help, please attach the HWiNFO Debug File for analysis.

Thanks for reporting. This shall be fixed in the next Beta build.

Identification of DIMM slot isn't always reliable and requires certain criteria to be met. If modules don't contain a valid serial number, HWiNFO might be unable to properly report the slot. That's what happened here, it's not a BIOS bug.