Search results

I will need to see the HWiNFO Debug File capturing this erratic situation. Can you please create such and post here?

It is expected to be fixed in the next Beta release scheduled for today.

Maybe because the rendering was done by the dGPU (MX450)?

That's certainly an erratic readout, nothing to worry. Does it maybe happen during sleep/resume or driver update?

:D

Thanks. I found the bug and it shall be fixed in the next Beta build of HWiNFO.

Thanks but the file needs to also contain the startup phase of HWiNFO. Please enable Debug Mode, start HWiNFO with sensors and close. Then attach the resulting DBG file.

HWiNFO should be showing correct sensor data for this mainboard including Vcore. Are you using the latest version of HWiNFO? If yes, please attach the HWiNFO Debug File with sensor data for analysis.

Still OK. Also FurMark is a very heavy load which you usually won't experience in common scenarios.

Test it under load.

Yes, it's normal, especially under load. 11.8-11.9 V is still within the acceptable range. Below ~11.6 V it would be a problem.

Build 5745 had a problem with monitoring of DIMM modules, so that could explain (probably some of) your issues. That's why 5746 was immediately released and I'd be curious if that build works with SMBus enabled. Another problem might be a conflict with other tools that access SMBus too. If you...

Do you have the latest version of HWiNFO?

Thanks for your feedback.

Released build 5746 to fix a problem with DDR5 sensors in build 5745.

Build 5746 was just released to fix this problem.

Thanks! Bug was identified and will be fixed in the next build.

Can you switch back to the latest Beta to check if the problem is certainly related to that?

Sorry, from software point of view it's not possible to tell what exactly happened. It only shows the I2C interface or the VRM isn't responding.

Not sure what happened by the entire interface used to access VRMs became stuck, so it's impossible to read that data.