Wrong Vcore, IVR, VRM (VOUT), POUT, IOUT values on idle/light load

simon64

New Member
Version Beta v8.01-5430 and 8.00 (no difference)

On an ASUS Z790-i board + 14900K (stock auto turbo clocks / SVID best case, icc 307) these values are wrong / very low or 0 on very light load or no load. Sometimes Vcore/ VOUT goes to 0.000v (while it should be at minimum 0.72v). IVR also goes near 0v. POUT/IOUT are also wrong or 0w.

OCtools RAW VRM is always displaying the correct VOUT / POUT values.

On load though these values on hwinfo are correct and the same as OCtools RAW VRM. For example, while running cinebench these values are correct.
I'm not running any other monitoring application at the same time.

I have noticed this is also happening on other ASUS boards (not sure on other brands/models).

This is not happening if I manually increase the Vcore (by svid offset or manual or higher acll value) or All Core multi.


hwinfo vcorepowerbug.jpg
 

Attachments

This is unfortunately the way how ASUS boards report it. For example IOUT is reported as an integer number, so it can't properly reflect <1 A values and reports 0 A in such case. Same for POUT.
 
Martin,

Didn't want to start a new thread for something that might be tied together from Asus. The other day when my system (Asus Prime Z790-P Wifi) came out of sleep my VR Vout (Vcore) voltage showed it was at 5volt and HWinfo 64 Pro v.8.10-5520 wouldn't reset. Did a restart and all was ok the sensor seems to read from (OnSemi NCP81530) I didn't get a Debug because it only happened that one time.
 

Attachments

  • Screenshot 2024-09-04 100010.png
    Screenshot 2024-09-04 100010.png
    12.9 KB · Views: 5
Martin,

Had another one of the spikes but this time I was able to take a better screen shot. It looks like the whole controller flaked out for second, I say this because it's showing a 255c for temps. I don't see this as a issue with HWinfo. I turned off the Alert I had set up for it and when the controller flaked this time it didn't cause HQinfo to lock up.
 

Attachments

  • Screenshot 2024-09-09 160120.png
    Screenshot 2024-09-09 160120.png
    10.7 KB · Views: 4
This is certainly a glitch in the readout. It can also happen when running some other incompatible monitoring/tweaking/RGB control tool along with HWiNFO.
 
Back
Top