falkentyne
Active Member
Hi Martin!
On my Z390 Aorus Master, when I use HWinfo to monitor voltages and current, when I am running a direct3D/game, some readings get thrown off and become inaccurate.
Notably, GPU mhz (speed), GPU voltage, GPU power (Watts) (AMD Vega 64),
and
Current IOUT, Power POUT, VR VIN (CPU IR 35201)
Are the ones I notice.
the ITE 8792E sensors seem to be fine as well as the Super IO (ITE 8688E).
Oddly enough, VR VOUT on the IR 35201 seems to be unaffected and "seems" to read fine.
For example, VR VIN is the CPU +12V sensor.
Usually this is 11.906-11.938 maximum, and 11.875v during prime95 AVX load, and 11.813v worst case (talking about some 200 amp shenanigans here).
However when running a 3D game, the VR VIN goes up to 12.000v. Even in something as weak as Overwatch.
This doesn't happen at all in Realbench 2.56, Cinebench, etc. *ONLY* if a fullscreen D3D game is running.
Power POUT (IR 35201 power register) gets wild swings too. However "CPU Package Power" remains nice and steady and expected.
Current IOUT has wild swings, sometimes jumping to 125 Amps (No way overwatch even comes close to pulling this much) then back down to 40 amps.
And the above GPU readouts.
However, MSI Afterburner reads the GPU speed, voltage and power perfectly accurately. You can see this with both MSI afterburner and HWinfo running at the same time...HWinfo is allover the place randomly with the GPU speed (usually 25-50 mhz difference but sometimes dropping even down to 1000-1000 mhz then back up to 1600), and voltage/power readings fluctuating. While MSI Afterburner is on target.
Is this some sort of bug or issue that might be addressable?
(again this only happens in games).
There is no problem in normal windows benchmarks or stress tests, where everything is dead accurate.
On my Z390 Aorus Master, when I use HWinfo to monitor voltages and current, when I am running a direct3D/game, some readings get thrown off and become inaccurate.
Notably, GPU mhz (speed), GPU voltage, GPU power (Watts) (AMD Vega 64),
and
Current IOUT, Power POUT, VR VIN (CPU IR 35201)
Are the ones I notice.
the ITE 8792E sensors seem to be fine as well as the Super IO (ITE 8688E).
Oddly enough, VR VOUT on the IR 35201 seems to be unaffected and "seems" to read fine.
For example, VR VIN is the CPU +12V sensor.
Usually this is 11.906-11.938 maximum, and 11.875v during prime95 AVX load, and 11.813v worst case (talking about some 200 amp shenanigans here).
However when running a 3D game, the VR VIN goes up to 12.000v. Even in something as weak as Overwatch.
This doesn't happen at all in Realbench 2.56, Cinebench, etc. *ONLY* if a fullscreen D3D game is running.
Power POUT (IR 35201 power register) gets wild swings too. However "CPU Package Power" remains nice and steady and expected.
Current IOUT has wild swings, sometimes jumping to 125 Amps (No way overwatch even comes close to pulling this much) then back down to 40 amps.
And the above GPU readouts.
However, MSI Afterburner reads the GPU speed, voltage and power perfectly accurately. You can see this with both MSI afterburner and HWinfo running at the same time...HWinfo is allover the place randomly with the GPU speed (usually 25-50 mhz difference but sometimes dropping even down to 1000-1000 mhz then back up to 1600), and voltage/power readings fluctuating. While MSI Afterburner is on target.
Is this some sort of bug or issue that might be addressable?
(again this only happens in games).
There is no problem in normal windows benchmarks or stress tests, where everything is dead accurate.