gupsterg

UEFI 1403 in this post. UEFI 1403-SP42M by The Stilt in this post.

Thank you all for help. Just to make sure I was not nuts I tried just a straight up CPU Frequency sub on HWBot. Copy and paste of address of sub then equals fail on submit. This included https://, I then changed only url from https://valid.x86.fr/chln2e to http://valid.canardpc.com/chln2e it worked. So did sub here same way and all AOK. It was more hard work getting the sub done then gaining the OC .

jab383 I tried that and I tried Chino's suggestion on ROG forum of using: valid.canardpc.com/975tx1 This is the error I get again same as before the night I ran the bench, then same following morning when trying again. I did have the screenie/system rig images in sub but those get removed after the error. Done subs before on OC-Esports / HWBot never had this issue . I'll try another run and get another validation and report back.

https://valid.x86.fr/975tx1 Tried submission several times but the CPU validation link not accepted. Any help/insight be welcome, thanks.

When I use submit button and enter HWBot username/pwd I get this, then once click OK I get this. So the way I did the sub is just by uploading data file and screenie using PRTSCRN. Now is this breaking rule:- Cheers. *** edit *** I see data file has the screenie , so guess I'm all good?

1106 did not allow voltage change for several of us on OCN. The UEFI is supposed be removed from Asus site but delay AFAIK. 1107 is working AOK so far for several of us, in this post by Elmor.

The Stilt posted this info on OCN regarding LLC on C6H, this one is also good information. Then Raja@Asus also did some oscilloscope tests, see this post, then in this post he states the same thing as The Stilt on "voltage point". Then a member did some testing of ProbeIt point vs Socket using DMM (which will not show under/overshoot like oscilloscope). The conclusion was drawn that CPU Core Voltage (SVI2 TFN) in HWiNFO is ~ what CPU get, but again as SW and slow read, accuracy is a factor IMO. So I use as "ballpark".

Wow stonking mate

Thank you for this elmor, hopefully I receive my R7 1700 + CH6 tomorrow when I Ryzen! .

Sweet share , thanks .

Added you access , I think I have found OTP , VR_Hot is evading me .

WIP .

I've had no issues sending i2c commands to Fury X via MSI AB . I've done voltage offset loop 1 & 2 (ie registers 8D and 8E), I've also played with the dual voltage offset (register 26). Why I think HWiNFO had issue with using i2c bus for monitoring is that the SMC keeps bus busy between it and IR3567B, sending one off command is different than constantly communicating with IR3567B IMO. If I do an i2cdump via MSI AB it takes ages compared with a Hawaii card, again as the dump process is constantly trying to use the i2c bus. If I use the read command for specific registers via MSI AB command line it is instantaneous read back. Only Unwinder on Guru3D has warned me against using i2c on Fury X due to SMC, but on The Stilt's instructions for a query I had on register 26 I used it, as he gave no warning I would think it's ok. I only send i2c commands when no monitoring in background/idling @ desktop.

Buildzoid, MSI AB has an inbuilt i2c tool, via command line you can send register/data value you wish to set.

deeper-blue Thanks for app creation . I would like to share some register data which I have collected:- i) some from testing myself. ii) some from ROM (VoltageObjectInfo) / i2cdump compares of various cards. iii) some from posts by The Stilt, Unwinder (author of MSI AB) and elmor/der8auer RX 480 ROM. Do you have any registers information besides ones in your app/my image? Cheers .