Search results

I don't know what it could be since I'm very careful about letting anything run in the background or as a service. Looking through my running processes and services I don't see anything that sounds like it would interfere. One other interesting note is that when I updated from the F3 bios to the...

0x60 was the right address, but disabling everything but that didn't help. I grabbed the latest INF from Intel, which did update to oem41.inf (from oem6.inf), but it didn't help either.

This doesn't seem right... lol

Is it possible to find out what SMBus addresses are associated with the ISL 69269 VR VOUT, IOUT, and POUT sensors? I'm wondering if disabling all other addresses except those would help.

Sometimes I am (e.g. OCCT and CPU-z) but it regularly happens when I'm not running anything else as well (assuming there's not some background application doing so w/o my knowledge). I don't understand how disabling monitoring the ISL sensor would help since those are the only sensor values that...

After playing with this some more, it's definitely related to however HWiNFO is querying the Intersil ISL69269's sensors. I've never had an issue w/o HWiNFO open. I've got the z590 Master and was hitting the BIOS reset reboot loop issue on the F3 bios, but now that I'm on the F5a BIOS it seems...

Thanks for the response! The sensors don't come back after stopping prime95 and restarting HWiNFO. Are there any other things I should try to reset the sensor reporting while Windows is running? Or is the only way to let the BIOS recover itself on reboot?

I just got a Gigabyte z590 Aorus Master and 10900k and have been in the process of overclocking, but sometimes under heavy load the Intersil ISL 69269 sensors stop reporting (VR VOUT, POUT, COUT, etc.). When I eventually reboot, the BIOS resets itself after a ~5x reboot loop (although it kindly...