ASUS R7 260X DirectCU II OC - Missing sensors

[Martin]

Thanks! That explains even more It seems that what HWiNFO currently reports is the voltage SET (except lower values, which are not properly reported).
I think I also found now how to read values back
What's the default voltage SET reported by ASUS, 1.225 V ?
Stay tuned for a new HWiNFO build

 

[Szb84]

Yes 1.225V is the default.
Great! Thank you for your time.

 

[Martin]

OK, here's the new build: www.hwinfo.com/beta/hw64_443_2291.zip
You should now see 2 values - Set (which should correlate with the voltage set) and Current (~ current voltage read).
I'm still not sure if it's all right. Please test and let me know the results...

 

[Szb84]

Current seems to display the current voltage so that's okay
The Voltage set however displays 2.025 at startup when the voltage is set to 1.225 V.
If I set to 1.194 or 1.188 it displays correctly, if I set to 1.275 displays 1.975, 1.3 V -> 1.950 V.
So it seems lower voltages are fine, but default (1.225) and default+ is incorrect.

 

[Martin]

OK, I see.. Just a minor issue that I'll fix right now.
What about the Current value, is that OK ? Sorry, I missed, that you already told it's OK Too much work..

 

[Martin]

Try this: http://www.hwinfo.com/beta/hw64_443_2292.zip

 

[Szb84]

This last build works for me: both set & current with lower,default and higher voltages!
I hope there will not be more issues.

Thank you!

 

[Martin]

That's great
Thanks for your testing too !

 

[Szb84]

Noticed a minor issue: When the monitor goes to sleep the GPU turns off thanks to AMD ZeroCore technology.
After waking up the current voltage keeps showing correctly but Voltage Set stays 0 V. If I restart HWiNFO the sensor disappears, the only way to bring it back to change something with ASUS GPU tweak (load default/custom profile, changing voltage etc).

Not a big deal though, since Current Voltage monitoring works and that's more important.

Also previously I had ADL detection enabled because ATI sensor #29,30,31 are slowed down HWiNFO start. But now I have to disable ADL to show the correct voltages and the slow startup came back.
I think those are belong to the AMD APU's IGP which is disabled due to the VGA. I've seen there is a possible sollution to exclude SMBus devices I tried some combinations but the still happens.

Edit: Seems ADL works fine with voltage monitoring so I don't have to exclude the SMBus devices

 

[Martin]

So after sleep the issue occurs when I2C via ADL is enabled and is OK if it's disabled ?

 

[Szb84]

No the 0 V / sensor disappear bug after sleep happens anyway doesn't matter if ADL is enabled/disabled.

 

[Martin]

Please attach a new Debug File which captures the situation after wake-up.

 

[Szb84]

With ADL Enabled the voltage sometimes drops to 0 V I can see it in minimum column, withoud ADL works fine here is the sleep dump:

 

[Martin]

Hm, indeed, it keeps reporting 0, which I thought is an invalid value and means the GPU is off.
I can change it, so that it will display the default 1.225V in such case, but this would then be reported when the GPU is off too.

 

[Szb84]

Sometimes minimum voltage column shows 0 V even without sleep mode.
I was able to capture Voltage Set but happens with current too.

 

[Martin]

I don't see any issues in that dump file.
Maybe try to close the ASUS tool, it might be a collision between them both when trying to access the GPU.

 

[Szb84]

It happens even when GPU Tweak is not running. Just for 1 sec drops to 0 V.

Also I noticed that if I shutdown the computer next boot the SET sensor disappears and won't show until I start GPU Tweak and load default settings or set the voltage.

Made a debug file with HWiNFO and also with AIDA:

------[ ATI I2C Device GPU #1 / B06-D20 ]------

0000 0211 0001 0000 5400 002A 5400 002A 5400 782A 003C 1C00 060E 4003 0020 8800 8844
0010 0044 0000 B000 0058 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 2200
0020 0211 0001 0000 5400 002A 5400 002A 5400 202A 0010 1C00 060E 4003 0020 8800 0044
0030 0000 B000 0058 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0400
0040 0A03 7005 68B8 00B4 0A00 0205 0201 0A01 0005 0000 0000 0000 0000 0000 0000 1E00
0050 0E0F AA07 FE55 00FF 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 6C00
0060 4836 0024 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0070 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0080 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0090 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
00A0 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
00B0 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
00C0 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
00D0 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
00E0 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
00F0 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 2200

 

[Martin]

I'll fix that in the next build - it will display the default 1.225V.

 

[Martin]

You might check this build if it fixes it: http://www.hwinfo.com/beta/hw64_443_2294.zip

 

[Szb84]

Works fine, now shows the sensors default value, and appears even after shutdown. Thx.