Crosshair VI Hero: UEFI build update thread

[Raja]

Directly from Elmor:

Beta BIOS 3008 for C6H/C6HWIFI/C6E:

AGESA 1.0.7.1, temperature offset fixed after S3 resume, GPU Post function fixed, 0d with some GPUs fixed

http://www.mediafire.com/file/f95motjmh211e7h/CROSSHAIR-VI-HERO-ASUS-3008.zip
http://www.mediafire.com/file/ntn6i3jiub610ai/ROG-CROSSHAIR-VI-HERO-WIFI-AC-ASUS-3008.zip
http://www.mediafire.com/file/yj22ld2rmmedp01/ROG-CROSSHAIR-VI-EXTREME-ASUS-3008.zip





C6H Test BIOS 0020 with AGESA 1007 (405200c4e299c1eed9a0044edec9aba51f37cee1d70caabe40b9485b0604521a)

In order to get back to an older version after flashing, you have to use USB BIOS Flashback.

Let me know how it works for you, especially regarding cold boot issues. Any confirmed bugs in the bug report form please




Beta BIOS 1501

* Workaround for some CPUs stuck at 22x ratio if using override voltage
* Fixes PCIEX4 bandwidth setting getting lost after power is removed
* Same DRAM boot behavior as 1403 (no cold boot fix)
* Same DRAM profiles as in 9920
* Still has the Vcore value issue when booting with Offset Mode and switching to Manual Mode

Crosshair VI Hero 1501 SHA256 EDE223DC6897B7199C93D9985E28B7A2CD1B8A8DB2DCBF3D3555A521DB4F045D
Crosshair VI Hero Wifi AC 1501 SHA256 0D9F51F43AA3A56A4AC984B11A52F58451B76F8A7CCB9A04E1C3194231C9D4DA






UEFI build 9920 for the C6H:

* Improved DRAM cold boot, results in slightly longer POST time
* Fix for CPU Ratio stuck at 22x on some CPUs when using Vcore override/offset
* SenseMi Skew is now Disabled by default. If you want to return to previous behavior set SenseMi Skew = Enabled and Offset = 272.
* Added DRAM profiles for Samsung B-based DIMMs with tuned subtimings, including The Stilt's settings



C6H beta UEFI 1403

* Fixed W_PUMP and AIO_PUMP speeds during POST
* Fixed Fan tuning sometimes failing
* Fixed a few issues with AMD USB3.1 ports
* Some tuning on DRAM settings, let us know how they work for you. tRDRD_Sc is still at 5 above 3500 MHz as it helps with stability. For performance you want to force this to 1. We'll consider changing this in future releases as the performance impact can be quite noticeable in certain applications.

An update on DRAM Boot Voltage, currently it should be 1.35V by default if the DRAM Voltage is changed. So if you're setting DRAM Voltage to above 1.35V, you might want to sync this setting. Additionally there might be scenarios where you will have better luck by syncing DRAM Boot Voltage to DRAM Voltage even at lower values.




AGESA 1006 RC4 official UEFI 1401

Just tested quickly 3600 memory and cold booting, seems good but you guys are going to have to help me test this before we have a judgement. Seems CPU temp reading from SIO now has -20*C offset for XFR enabled CPUs.





UEFI build 1107





Older test builds:


Test BIOS 0079

Test BIOS with new AGESA 1004a, with a couple of bugfixes. Up to 5% performance increases in specific applications. Also has P-state overclocking working with BCLK increase. If you want to keep C-states, make sure to set Advanced\AMD CBS\Zen Common Options\Global C-state Control = Enabled. There are two new settings under AMD CBS\UMC Common Options\DDR4 Common Options\ you might want to take a look at, Fail_CNT and ProcODT. Fail_CNT decides how many times to retry when DRAM training fails (F9 -> 0d), default is now 1. ProcODT can help improve your DRAM overclocking. There's a setting available also on previous BIOSes under AMD CBS\UMC Common Options\DRAM Memory Mapping named BankGroupSwap. If you have 2x Single-Rank modules you can try setting this to Disabled and you might see some performance boost in certain applications.

Test BIOS 0081

Same as 0079 but has ProcODT default = 53.3 ohm

Test BIOS 0082

Same as 0081 but with a DRAM compability patch for the below part numbers

CMK16GX4M4A2133C13
AHU08GGB13CGT7G
PV416G240C5QK
F4-2400C15Q-32GRR
TCD44G2400C14BK
F4-2666C16Q2-64GRB
AVD4UZ126661504G
BLT8G4D26AFTA.16FAD
IMA41GU6MFR8N-C F0
MD16GK4D4266615AXR
HX430C15PB2K4/16
HX430C15PBK4/32
AX4U3333W4G16-QGZ
GAM4DBLBM2133D15IE041C
TC48G24S817
SP004GBLFU213N02
78.C1GM3.AF10B
F4-3200C16D-8GVKB

MTA4ATF51264AZ-2G6B1
MTA8ATF1G64AZ-2G3B1
MTA16ATF2G64AZ-2G6B1
HMA41GU7AFR8N-TF T0
HMA451U7AFR8N-TF T0
HMA41GU6AFR8N-UH N0
M378A2K43BB1-CTD
M378A1K43BB1-CRC
M378A1G43EB1-CRC

Test BIOS 0083

Same as 0081 but with "2T" DRAM Mode when using above 2666 DRAM Ratio.

[Theagg]

In the Windows 10 power plan settings, using 'High Performance', select the advanced settings option, the the 'processor management' selection, under this select 'minimum processor state' and set that to, say, 20%.

That will instruct the PC to clock down when using a P state, when using the 'High Performance' plan.

Either way, P states do work on this board. My CH6 clocks down when at idle and the vcore drops. Load the CPU and it rises to my full overclock setting and the vcore rises accordingly.

(I've managed this from the bios, not using the tool)

Perhaps something is not set right in your bios, exactly what are your settings etc ?

[brumylad2017]

Theagg wrote:
In the Windows 10 power plan settings, using 'High Performance', select the advanced settings option, the the 'processor management' selection, under this select 'minimum processor state' and set that to, say, 20%.

That will instruct the PC to clock down when using a P state, when using the 'High Performance' plan.

Either way, P states do work on this board. My CH6 clocks down when at idle and the vcore drops. Load the CPU and it rises to my full overclock setting and the vcore rises accordingly.

(I've managed this from the bios, not using the tool)

Perhaps something is not set right in your bios, exactly what are your settings etc ?

the minimum processor state option in processor management isnt available for me in the high performance power plan as u can see in the screenshot.

im running the Ryzen 1700X using bios 0902 with the following settings :
1. cpu core ratio changed to 39.00
2. changed CPU core voltage to offset mode with CPU offset mode sign set to - instead of +
3. CPU load line calibration set to level 2.

i have not applied any settings in the bios to the p State settings in the bios the only things i have changed in the bios is what listed above.

[entropic-remnan]

After considering the descriptions of the various BIOS test versions, I decided that 0081 seemed like a better fit tha 0082. Results are good so far.

On the plus side:

• With a 96 ohm ProcODT value, I'm much more solid.
  
• With a 150mhz Bclk I can hit 3200 mhz now on my Corsair Dominator memory which means it's doing what it says on the tin.
  
• I can still drop the timings to 14-16-16-16-32
  

On the minus side:

• Slight drop in CPU clock with available multipliers
  
• Using anything but a 2133 profile results in memory underclocks with the high multiplier (as seen in CPUZ), even though the BIOS says it's above 3200.
  
• The system will not post at all with Bclk above 150 regardless of memory speed selected (Promontory limitation maybe?)
  

However, this is definitely progress. The 100mhz I picked up on the memory may not be significant, but it bugged me "in principle" that my 3200mhz memory was running at 3100. Yes, a first-world problem I know, lol.

Very much enjoying having found this thread.

[cjrb007]

brumylad2017 wrote:
the minimum processor state option in processor management isnt available for me in the high performance power plan as u can see in the screenshot.

im running the Ryzen 1700X using bios 0902 with the following settings :
1. cpu core ratio changed to 39.00
2. changed CPU core voltage to offset mode with CPU offset mode sign set to - instead of +
3. CPU load line calibration set to level 2.

i have not applied any settings in the bios to the p State settings in the bios the only things i have changed in the bios is what listed above.

Enable "EPU Power Saving Mode" in BIOS under"Extreme Tweaker" Menu.

[Theagg]

brumylad2017 wrote:
the minimum processor state option in processor management isnt available for me in the high performance power plan as u can see in the screenshot.

im running the Ryzen 1700X using bios 0902 with the following settings :
1. cpu core ratio changed to 39.00
2. changed CPU core voltage to offset mode with CPU offset mode sign set to - instead of +
3. CPU load line calibration set to level 2.

i have not applied any settings in the bios to the p State settings in the bios the only things i have changed in the bios is what listed above.

Yes, as I found out, that power plan option in Windows won't be available if certain settings in the bios are enabled/disabled/auto

So, why have you set a minus offset ? And what value ? I also found out from experience that setting an offset without setting a P state leads to problems, instability etc.

Try this, go to the 'exit' menu in the bios, then select 'restore optimised defaults'

Then go to the P state menu and select P state 0 and input 9C into the FID box. 9C = 39 (your 39 multiplier in hex)

Come out of the P State page and in the Zen Common options ensure C States is enabled.

Since you have not mentioned overclocking BCLK or anything, I'm assuming your target is 3.9GHZ (since BCLK will be 100 by default and will be multiplied by the 39/9C value in the P state FID

You should know what value of Vcore you need to run stable at 3.9Ghz, so, if this value is higher than the default value in the P state 0 VID box, you will need to add that as an offset.

So, if you need 1.375 volts for example, your offset will be 1.375 - VID = X (the default VID in that P state is usually 1.35v (although it appears as 1350000 (microvolts) So X in that case would be 1.375 - 1.35 = 0.025v

Back in the Extreme Tweaker page, select positive offset then in the box, type the value of X. In my current set up X = 0.04v

Set LLC to level 2 and also it has been suggested to set phase control to 'optimised' rather than 'extreme'

Unless you are attempting to overclock your memory, everything else can be left as is. If you are overclocking your RAM and a different BCLK value is displaying that is not 100, then the FID value in the P state will need to be changed from 9C to get back the proper multiplier to get you that 3.9Ghz (CPU freq = FID x BCLK) But this BCLK with P states won't work with the bios you are using, of course.

REboot and if all goes well, then go back into the windows power plan and see if that 'minimum processor state' option is now available, it should be.

[brumylad2017]

Theagg wrote:
Yes, as I found out, that power plan option in Windows won't be available if certain settings in the bios are enabled/disabled/auto

So, why have you set a minus offset ? And what value ? I also found out from experience that setting an offset without setting a P state leads to problems, instability etc.

Try this, go to the 'exit' menu in the bios, then select 'restore optimised defaults'

Then go to the P state menu and select P state 0 and input 9C into the FID box. 9C = 39 (your 39 multiplier in hex)

Come out of the P State page and in the Zen Common options ensure C States is enabled.

Since you have not mentioned overclocking BCLK or anything, I'm assuming your target is 3.9GHZ (since BCLK will be 100 by default and will be multiplied by the 39/9C value in the P state FID

You should know what value of Vcore you need to run stable at 3.9Ghz, so, if this value is higher than the default value in the P state 0 VID box, you will need to add that as an offset.

So, if you need 1.375 volts for example, your offset will be 1.375 - VID = X (the default VID in that P state is usually 1.35v (although it appears as 1350000 (microvolts) So X in that case would be 1.375 - 1.35 = 0.025v

Back in the Extreme Tweaker page, select positive offset then in the box, type the value of X. In my current set up X = 0.04v

Set LLC to level 2 and also it has been suggested to set phase control to 'optimised' rather than 'extreme'

Unless you are attempting to overclock your memory, everything else can be left as is. If you are overclocking your RAM and a different BCLK value is displaying that is not 100, then the FID value in the P state will need to be changed from 9C to get back the proper multiplier to get you that 3.9Ghz (CPU freq = FID x BCLK) But this BCLK with P states won't work with the bios you are using, of course.

REboot and if all goes well, then go back into the windows power plan and see if that 'minimum processor state' option is now available, it should be.

i have tried this and been successful in getting the hidden option to appear but have noticed for some reason cpu temps idle around 28'C use the guide u have given compared to around 16'C using the settings im runnings and i can confirm my settings are fully stable.

also didnt need to give any manul offset voltage was happy at defualt 1.352v as in the bios and in windows never pulls over that.

can u please confirm u was on about cpu phase control yes ?

minus offset voltage i was using purely for testing now gone back to using plus offset now.

i have this memory
http://www.corsair.com/en-gb/dominator-platinum-series-16gb-2-x-8gb-ddr4-dram-3200mhz-c16-memory-kit...

so if u know of any ways to get this memory working @3200mhz then im happy to try but tried many settings and not had much joy. but currently running it @ 2666 with timmings 14-13-13-13-30 @1.35v

[entropic-remnan]

brumylad2017 wrote:

i have this memory
http://www.corsair.com/en-gb/dominator-platinum-series-16gb-2-x-8gb-ddr4-dram-3200mhz-c16-memory-kit...

so if u know of any ways to get this memory working @3200mhz then im happy to try but tried many settings and not had much joy. but currently running it @ 2666 with timmings 14-13-13-13-30 @1.35v

What is the version number on the memory? I have the "same" memory but apparently there are different versions of it. Mine is 4.24.

Refer to my posts on page 26 of this thread. I tried some different BIOS versions and I'm running with the 0081 "experimental" one as noted in my later post on that page.

So, running BIOS 0081 and getting the full 3200 mhz reliably but I've reverted to the stock timings (16-18-18-18-36) and a ProcODT of 80 ohms after more extensive memory testing with HCI Memtest. You WON'T get the full 3200 without a big base clock boost if your system is anything like mine. And I can't run at all that fast without setting the ProcODT value manually.

If you are like I was you are wondering what ProcODT is -- stands for "Processor On-Die Terminator". Basically it's a load that has to be on the signal lines to the DRAM to keep the signals clean. Like with coaxial cables and their impedance -- without a "match" the signal is degraded.

Anyway, apparently the AUTO search for that setting doesn't work as well as it perhaps could. So you have to play around and find it manually.

Good luck with your search for an answer. Mine so far is doing pretty well.

[brumylad2017]

entropic-remnants wrote:
What is the version number on the memory? I have the "same" memory but apparently there are different versions of it. Mine is 4.24.

Refer to my posts on page 26 of this thread. I tried some different BIOS versions and I'm running with the 0081 "experimental" one as noted in my later post on that page.

So, running BIOS 0081 and getting the full 3200 mhz reliably but I've reverted to the stock timings (16-18-18-18-36) and a ProcODT of 80 ohms after more extensive memory testing with HCI Memtest. You WON'T get the full 3200 without a big base clock boost if your system is anything like mine. And I can't run at all that fast without setting the ProcODT value manually.

If you are like I was you are wondering what ProcODT is -- stands for "Processor On-Die Terminator". Basically it's a load that has to be on the signal lines to the DRAM to keep the signals clean. Like with coaxial cables and their impedance -- without a "match" the signal is degraded.

Anyway, apparently the AUTO search for that setting doesn't work as well as it perhaps could. So you have to play around and find it manually.

Good luck with your search for an answer. Mine so far is doing pretty well.

not sure what the verision number is on my ram without checking but id imagine its 4.24. i wont be doing a BCLK overclock that high as its putting a lot of strain on the FSB and well mess my overclock on my cpu up. i know its only a matter of time until AMD fix the memory support and other things which need fixing.

[entropic-remnan]

brumylad2017 wrote:
not sure what the verision number is on my ram without checking but id imagine its 4.24. i wont be doing a BCLK overclock that high as its putting a lot of strain on the FSB and well mess my overclock on my cpu up. i know its only a matter of time until AMD fix the memory support and other things which need fixing.

Understood. I'm hoping for a more "standard" solution as well, but I wanted to share something that can be done in the meantime. If you want to stay with a reasonable Bclk, then it is for sure a "waiting game".

[jagilbertvt]

I just wanted to report that I was able to get my 32GB (2x16GB) memory kit running @ 3200Mhz. I'm using BIOS 0079 w/ Ryzen 1800x @ stock and G.Skill Trident Z memory (F4-3200C16D-32GTZA, https://www.newegg.com/Product/Product.aspx?Item=N82E1682023219).

This is running at 3200Mhz w/ 18-18-18-18-36 timings and default BCLK (100Mhz). I didnt have any luck posting w/ tighter timings. ProcODT is set to 96 Ohms. DRAM Voltage is configured @ 1.35v w/ DRAM boot voltage set to 1.45v, though I'm not sure the boot voltage increase is entirely necessary.

I was also able to post using the 2666Mhz memory setting w/ a BCLK of 120Mhz, but this adversely affects other components (M.2 drops to PCIe Gen, older Emulex 10GbE adapter was not being detected). I believe I was able to use 16-16-16-16-36 timings when using the 2666Mhz setting and 120Mhz BCLK.