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.

[Syaoran]

sbakic wrote:
Components:
CPU 1700x
CPU Cooler NZXT Kraken62
RAM F4-3200C14Q-32GTZ
Motherboard Asus Crosshair Vi Hero WIFI

My current overclocking settings:

BIOS version 1701

CPU overclock p0 state 9D -> 39.25x

Extreme Tweaker
CPU Core Voltage = Offset mode
CPU Core Voltage Offset Mode Sign = +(plus)
- CPU Core VoltageVoltage Offset = 0.03125
CPU SOC Voltage = Offset mode
VDDSOC Offset Mode Sign = - (minus)
- VDDSOC Voltage Offset = 0.03125
DRAM Voltage = 1.35000 (Default)
Extreme Tweaker \ DRAM Timing Control
DRAM ... = 14-14-14-14-34-48-6-8-39-Auto(4)-Auto(12)-Auto(24)-Auto(0)-3-3-312-232-142-Auto(14)-8-Auto(6)-Auto(3)-Auto(1)-Auto(7)-Auto(7)-Auto(1)-Auto(5)-Auto(5)-Auto(8)
ProcODT_SM = 60 ohm
Cmd2T = 1T
RttNom = RZQ/7
RttWr = RZQ/3
RttPark = RZQ/1
Extreme Tweaker \ External Digi+ Power Control
DRAM VBoot Voltage = 1.35

Stress test passed:
RealBench(32GB RAM): 8h
AIDA64: 8h
OCCT CPU small: 8h
OCCT CPU large: 8h
OCCT Linpack (with AVX): 8h
Intel Burn Test: 8h
prime95 small: 8h
prime95 in-place: 8h
prime95 blend(with 29GB ram): 24h
mprime: 24h
hci memtest 1000%
memtest86: 4x runs
google stress test: 1h
ryzen kill script: 24h

So overclock is stable. But I have Failed RAM Trainig from cold boot and I hate it.

I tried to set procODT to 68,8 ohm and 80 ohm, still same. 53.3 ohm will not even boot from restart.
I tried Vboot to 1.375V and even 1.4V, nothing
I tried to change from auto to
MemCadBus ClkDrvStren_SM = 30ohm, 30.0 Ohm, 30 ohm

MemCadBus AddrCmdDrvStren_SM = 30omh, 30.0 Ohm. 30 ohm

MemCadBus CsOdtDrvStren_SM = 30 ohm,40.0 Ohm, 60 ohm

MemCadBus CkeDrvStren_SM = 40 ohm, 60.0 Ohm, 60 ohm
Still the same.

I don't know what to do anymore. Can someone help me to solve this issue? Thanks.

Up your RAM boot voltage to 1.4v. You are probably going to need more than that to get 32GB of RAM to boot into Windows stable. 1.42v should be considered as something to try. 1701 is definitely far from the current latest BIOS. However, that doesn't necessarily mean things will improve if you update.

[sbakic]

Syaoran wrote:
Up your RAM boot voltage to 1.4v. You are probably going to need more than that to get 32GB of RAM to boot into Windows stable. 1.42v should be considered as something to try. 1701 is definitely far from the current latest BIOS. However, that doesn't necessarily mean things will improve if you update.

I tried 1.4V, however I didn't try 1.42V. Not sure whether should I do that.. it's to high, but maybe like a last options.

[Syaoran]

sbakic wrote:
I tried 1.4V, however I didn't try 1.42V. Not sure whether should I do that.. it's to high, but maybe like a last options.

Although I have mine set at 1.425, it still, at times, reaches as high as 1.46. My RAM is Samsung B-Die though. What most get with 16GB is harder when the density of the memory is higher or you are using all 4 RAM slots. You could also try setting the RAM boot to 1.4v and putting your RAM voltage, SoC, and others on auto and get an idea of what it wants to pull, if it successfully boots.

[HnS-CHH]

2700x that auto voltage...


Supposed to receive on saterday but my bell that day was malfunction.

ie we are not under NDA as required contract and a warning paper for us shall forum occure.

Pff... the occt default setting crashed upon 1.4v, 4.2 ghz at 2 min and 42 sec and fast timing from 1usmus 3466c14 is not guaranteerd to boot either.

Edit: 3333c14 seems to be hard limit for my memory just like my 1700. Now I think there is something wrong with my cpu temp it is unusually high for a 360 radiator. Also managed to run occt over 7 min with above setting and 1.45v but a error pop out, CPU temp was hitting nearly 79C though.

Edit: Can confirm that aio pump never worked on first place. Before on 1700 and 650w psu.

[Darth_Ender]

isn't -32GTZ ram dual rank? and you are trying to use it as single according to your settings post. I'd imagine very few attempts would succeed at training it. (cmd2t)

[sbakic]

Darth Ender wrote:
isn't -32GTZ ram dual rank? and you are trying to use it as single according to your settings post. I'd imagine very few attempts would succeed at training it. (cmd2t)

It's dual rank, what do you mean i am trying to use it as single, what settings are those? RAM training doesn't work every time. That's the point.

What is left to try 3502 BIOS with default 3200 Mhz clock if that doen't work every time I will probably need to hibernate PC every time instead of shut down. Would hibernate help?

[Darth_Ender]

sbakic wrote:
It's dual rank, what do you mean i am trying to use it as single, what settings are those? RAM training doesn't work every time. That's the point.

What is left to try 3502 BIOS with default 3200 Mhz clock if that doen't work every time I will probably need to hibernate PC every time instead of shut down. Would hibernate help?

dual rank ram is always cmd2t = 2. you had yours as 1. 1 only works on dual rank ram at low frequency if at all. That's all i meant. Trying to run dual rank with cmd2t=1 will most definitely cause issues trying to train the ram and lead to unstable behavior when using it. That is, assuming it is actually running at cmd2t=1 when it does boot. cpuz would tell you for sure.

[FoxTech]

Hello Darth Ender

I wouldn't sign, that cmd2t 1T is made for Single Ranked and 2T for Dual Ranked Ram.

Currently using 2x16GB Dual Ranked Dominator Platinum 3466 @3333. (14-14-14-35)
Just teststed it with 1T and 2T
Both settings working and no Test faild.
But 1T is faster in Benchmarks. I bet I wouldn't notice any differnce in real life computing.
1T seems stable on my system.

[Darth_Ender]

FoxTech wrote:
Hello Darth Ender

I wouldn't sign, that cmd2t 1T is made for Single Ranked and 2T for Dual Ranked Ram.

Currently using 2x16GB Dual Ranked Dominator Platinum 3466 @3333. (14-14-14-35)
Just teststed it with 1T and 2T
Both settings working and no Test faild.
But 1T is faster in Benchmarks. I bet I wouldn't notice any differnce in real life computing.
1T seems stable on my system.

the norm is that if you have dual rank and it's having trouble running at the specs it should be able to run at, the first steps you take is setting cmd2t to 2 and start pushing procodt up.

there is some rank2 ram that can handle cmd2t=1 ...but most can't. just like how most can't even run at 3200 on ryzen systems even if they're rated for it but there are a small minority that can. So call it a rule of thumb then instead of a hard rule.

[FoxTech]

Thanks for explaining Mate!
Then I'm a lucky one 😉

The Ram controller sit in the CPU, as far as I know. So with a quite nice CPU you gain higer Ram clocks.
Well, I haven't had AMD for years. Maybe this is complete nonsense I type.