Crosshair VII Hero Essential Info Thread

[gupsterg]

Moar Matisse ...

SMU FW in AGESA ComboPi-AM4 1.0.0.3AB/ABB is what is responsible for poorer boost than prior AGESA. Here are links to two of The Stilt's posts on this, link 1, link 2. Shamino has also stated the same on ROG, link.

AGESA ComboPi-AM4 1.0.0.3AB exposes 2 new settings in PMU menu (aka IMC), link. Some testing on changing MR6VrefDQ and some info on the web in this post.

Next I wanted to share an observation regarding AMD Overclocking menu. UEFI 2602 onwards seem to have "recovery" functioning. If I set a bad profile, board can Q-Code: F9, it will then repost and retry, if it still can't post then settings are reset and board will post. Any settings in AMD Overclocking menu are retained for reapplication, only AMD CBS settings will be defaulted and need to be setup again.

For example say I set SOC Voltage of 1056mV in AMD Overclocking menu and due to another setting I tinkered with, board went Q-Code: F9 on post, it will try again and then after upto ~3 retries it will reset settings and post. On entering UEFI you will see monitoring data for SOC voltage will be at defaults ie ~1.015V, the SOC voltage of 1056mV will still be in AMD Overclocking menu, when you save & exit and a successful post occurs you will see monitoring data relevant to SOC set value of 1056mV.

*** edit ***

See posts here and OCN in regard to VID being 1.1V when we manually OC, this post should help to explain reason, link.

*** edit 2 ***

A day or so ago when googling for DDR4 info I came across this PDF, page four has an interesting graph on margin of say DRAM/Package/Board/Chip/Data window. Noting the shrinking margin I thought this correlated well with how when I moved to 4x8GB I could only gain post on ProcODT of 34.3 when targetting 3800MHz.

At the time when I first used 4x8GB on my R5 3600 I used UEFI 2501 for ASUS ROG Crosshair VII Hero WiFi, default ProcODT on [Auto] was 60 for that one. System posted with 3600MHz and also 3666MHz, 3733MHz it wouldn't until I set ProODT 40. 3800MHz did not post until I set ProcODT as 34.3. I continued stability testing I had decent passes and all was fine.

Curiosity had been eating away at me on why was ProODT behaving this way, why on 4x8GB I'm using lower value, why is it only posting on a specific ProODT. In the past I had seen 1xxx/2xxx post on wider range of ProcODT and just lose stability if incorrect, only if ProODT was wildly out was post affected.

I decided to move the dimms around the slots.

I changed from:-

B1: #87 B2: #89 A1: #84 A2: #88

to

B1: #89 B2: #87 A1: #88 A2: #84

I could now gain post on 3800MHz with wider range of ProODT, 34.3, 40, 43.6 and 60, any others resulted in post failure.

I then moved dimms again.

B1: #84 B2: #87 A1: #89 A2: #88

I could gain post on 34.3 36.9 40 43.6 48, still testing others.

I do not know if this is specific to my HW and or targetted settings, but felt it maybe something that users of 4 dimms may wish to know.

*** edit 3 ***

Usually when I opened Ryzen Master on AGESA ComboPi-AM4 1.0.0.2 UEFI, I saw Q-Code: AA change to d3, this did not affect stability. On UEFIs with AGESA ComboPi-AM4 1.0.0.3AB/ABB I see Q-Code: AA change to d3 and then F8, again does not affect stability.

In this ZIP are 2x WMV, I open RM when take the screen capture of ~5000%, then close it and reopen at ~8000%.

[gupsterg]

Thanks to The Stilt's info I have managed to mod SMU FW 46.34.00 into C7H & C7HWIFI UEFI 2703 & 0002.

2703 is current "Official" and 0002 is one with ASUS WMI possibly fixed.

PBO+150MHz set on my R5 3600 on UEFI 2501, 2703 and modded 0002, can be seen in WMVs in this ZIP.

Disclaimer

Download & use UEFIs at your own risk, I experienced no adverse effects so far, but only limited testing done on one configuration.

I am just a user sharing my modded UEFI, I am not qualified and or employed in the field of computing.

Download link for mod UEFIs.

Use flashback method of flashing UEFI.

i) Change UEFI filename as C7H.CAP or C7HWIFI.CAP depending on your model.

ii) Copy to USB stick, it must be formatted to FAT32. File must not be in a directory.

iii) Load UEFI defaults prior to doing flashback and let mobo repost and shutdown.

iv) Make sure USB stick is in Flashback port (ie one which has marking BIOS)

v) Press and hold the Flashback button (blue box, above image) ~5secs. Blue LED on the button will flash slow for a few seconds and quicken as it starts update process. At the end of process it will extinguish, you are ready to boot up. If the blue LED stays constant the UEFI file was not found on USB stick, so check USB stick is correct format and filename is correct.

Additional info

Anyone thinking there is major defect with SMU FW 46.34.00 should read this post by The Stilt.

This is an interesting post on PBO if anyone wanna add it to their bookmarks.

Just as added info to anyone thinking I make changes to SMU FW 46.34.00, I don't. If I edited it, I have no means a) dissemble it b) reassemble it and make it pass PSP checks, it is just copied and pasted as is.

[sifusanders]

Thanks to The Stilt's info I have managed to mod SMU FW 46.34.00 into C7H & C7HWIFI UEFI 2703 & 0002.

2703 is current "Official" and 0002 is one with ASUS WMI possibly fixed.

PBO+150MHz set on my R5 3600 on UEFI 2501, 2703 and modded 0002, can be seen in WMVs in this ZIP.

Disclaimer

Download & use UEFIs at your own risk, I experienced no adverse effects so far, but only limited testing done on one configuration.

I am just a user sharing my modded UEFI, I am not qualified and or employed in the field of computing.

Download link for mod UEFIs.

Use flashback method of flashing UEFI.

i) Change UEFI filename as C7H.CAP or C7HWIFI.CAP depending on your model.

ii) Copy to USB stick, it must be formatted to FAT32. File must not be in a directory.

iii) Load UEFI defaults prior to doing flashback and let mobo repost and shutdown.

iv) Make sure USB stick is in Flashback port (ie one which has marking BIOS)

v) Press and hold the Flashback button (blue box, above image) ~5secs. Blue LED on the button will flash slow for a few seconds and quicken as it starts update process. At the end of process it will extinguish, you are ready to boot up. If the blue LED stays constant the UEFI file was not found on USB stick, so check USB stick is correct format and filename is correct.

any chance you could do that for the 0002 for c6h as well? thanks a lot!

[mikev190]

any chance you could do that for the 0002 for c6h as well? thanks a lot!

+1 that would be great

[xeizo]

Thanks to The Stilt's info I have managed to mod SMU FW 46.34.00 into C7H & C7HWIFI UEFI 2703 & 0002.

2703 is current "Official" and 0002 is one with ASUS WMI possibly fixed.

PBO+150MHz set on my R5 3600 on UEFI 2501, 2703 and modded 0002, can be seen in WMVs in this ZIP.

Disclaimer

Download & use UEFIs at your own risk, I experienced no adverse effects so far, but only limited testing done on one configuration.

I am just a user sharing my modded UEFI, I am not qualified and or employed in the field of computing.

Download link for mod UEFIs.

Use flashback method of flashing UEFI.

i) Change UEFI filename as C7H.CAP or C7HWIFI.CAP depending on your model.

ii) Copy to USB stick, it must be formatted to FAT32. File must not be in a directory.

iii) Load UEFI defaults prior to doing flashback and let mobo repost and shutdown.

iv) Make sure USB stick is in Flashback port (ie one which has marking BIOS)

v) Press and hold the Flashback button (blue box, above image) ~5secs. Blue LED on the button will flash slow for a few seconds and quicken as it starts update process. At the end of process it will extinguish, you are ready to boot up. If the blue LED stays constant the UEFI file was not found on USB stick, so check USB stick is correct format and filename is correct.

Many thanks! Super exciting, I will test as soon as I get the time for it, your work is really appreciated!

[Vali Pali]

Thanks to The Stilt's info I have managed to mod SMU FW 46.34.00 into C7H & C7HWIFI UEFI 2703 & 0002.

2703 is current "Official" and 0002 is one with ASUS WMI possibly fixed.

PBO+150MHz set on my R5 3600 on UEFI 2501, 2703 and modded 0002, can be seen in WMVs in this ZIP.

Disclaimer

Download & use UEFIs at your own risk, I experienced no adverse effects so far, but only limited testing done on one configuration.

I am just a user sharing my modded UEFI, I am not qualified and or employed in the field of computing.

Download link for mod UEFIs.

Use flashback method of flashing UEFI.

i) Change UEFI filename as C7H.CAP or C7HWIFI.CAP depending on your model.

ii) Copy to USB stick, it must be formatted to FAT32. File must not be in a directory.

iii) Load UEFI defaults prior to doing flashback and let mobo repost and shutdown.

iv) Make sure USB stick is in Flashback port (ie one which has marking BIOS)

v) Press and hold the Flashback button (blue box, above image) ~5secs. Blue LED on the button will flash slow for a few seconds and quicken as it starts update process. At the end of process it will extinguish, you are ready to boot up. If the blue LED stays constant the UEFI file was not found on USB stick, so check USB stick is correct format and filename is correct.

Is this suppose to fix the boost behaviour?

[gupsterg]

any chance you could do that for the 0002 for c6h as well? thanks a lot!

+1 that would be great

Working on it as someone on Reddit also asked.

Many thanks! Super exciting, I will test as soon as I get the time for it, your work is really appreciated!

NP, look forward to your experience share.

Is this suppose to fix the boost behaviour?

Reverts it to what you would see on an AGESA ComboPi-AM4 1.0.0.2 UEFI.

Someone used it with a 3900X on reddit, requested/shared experience only in my inbox so far.

[xeizo]

Is this suppose to fix the boost behaviour?

That would be the entire point of the mod AFAIK

[mikev190]

Working on it as someone on Reddit also asked.



NP, look forward to your experience share.



Reverts it to what you would see on an AGESA ComboPi-AM4 1.0.0.2 UEFI.

Someone used it with a 3900X on reddit, requested/shared experience only in my inbox so far.

You are a legend, thanks for all the hard work you put into our community

[xeizo]

Working on it as someone on Reddit also asked.
Someone used it with a 3900X on reddit, requested/shared experience only in my inbox so far.

Sounds legit, I get 4625MHz on two cores with 1.0.0.2.