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.

[Jonotallica]

Thanks, but due to using 2700X, I'm stuck being able to use versions 6004 or later. I'll have to do some searching and browsing around I guess. As the stability of BIOSs would be dependant on which CPU you are using. So what's unstable for a 1700X might not be unstable for 2700X and vice versa. But then if it's a decent company like ASUS (usually), maybe the latest can be best for all CPU's, even the older ones. I don't think it's like this was Asrock though. Especially how you can't go back.. that really sucks to be stuck having to wait for a fix of a beta BIOS.

Good news that ASUS let's you go back and forth without that limitation.

[AfterShock]

Jonotallica wrote:
Thanks, but due to using 2700X, I'm stuck being able to use versions 6004 or later. I'll have to do some searching and browsing around I guess. As the stability of BIOSs would be dependant on which CPU you are using. So what's unstable for a 1700X might not be unstable for 2700X and vice versa. But then if it's a decent company like ASUS (usually), maybe the latest can be best for all CPU's, even the older ones. I don't think it's like this was Asrock though. Especially how you can't go back.. that really sucks to be stuck having to wait for a fix of a beta BIOS.

Good news that ASUS let's you go back and forth without that limitation.

I'm also using 2700x and haven't had any issues with the 6401 or 7002 firmware.

[Falck]

Last BIOS brought back my RAM OC! Great!

[KWSW83]

I notice my 1800x throttling at 75°C based on Ryzen Master when running the Asus real bench stress test. Is this something to do with Sense MI or is there another option in the bios I should be changing? I don't think my 1800x should be running this hot on stock considering i am running an water cooling AIO. Everything is on auto for my bios settings.

[Falck]

After some testing I reverted back to 6302 for CPU and RAM OC stability.

[AfterShock]

Falck wrote:
After some testing I reverted back to 6302 for CPU and RAM OC stability.

did you ever get a random crash where the qcode was flashing 8, I'd be playing metro exodus and eventually my monitor would just shut off and I would notice that error message flashing away, I believe it's because the PBO is still screwed up in this version , using the performance enhancement level 1 or 2 shows 1000A in ryzen master which isn't possible no matter what type of cooling was being used, now if I disable PBO completely then the performance levels don't really do anything. Pretty amazing for how long this board has been out and we are still beta testing bios versions.

[Falck]

AfterShock wrote:
did you ever get a random crash where the qcode was flashing 8, I'd be playing metro exodus and eventually my monitor would just shut off and I would notice that error message flashing away, I believe it's because the PBO is still screwed up in this version , using the performance enhancement level 1 or 2 shows 1000A in ryzen master which isn't possible no matter what type of cooling was being used, now if I disable PBO completely then the performance levels don't really do anything. Pretty amazing for how long this board has been out and we are still beta testing bios versions.

No, never had a crash like that. What I experienced with later BIOS'es was a big regression of CPU performance when OC'ing. But not crashing or not beeing able to OC. Also I lost my RAM OC with AGESA 0.0.7.0, although it got somewhat back in 0.0.7.2 I didn't get the timings back, only MHz.

So I'll stick with 6302 for now.

[purecain]

@falk how did you revert back. what did you name the bios. I tried using C6H.CAP and was given an error message!

[Falck]

That's exactly what I did. Renamed file to C6H.cap (I need to name it to c6hwifi.cap) and used the BIOS flashback button on the IO panel.

[Falck]

That's exactly what I did. Renamed file to C6H.cap (I need to name it to c6hwifi.cap) and used the BIOS flashback button on the IO panel.