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]

Darth Ender wrote:
Not to be that guy, but discussing discrete sound card issues is like (well, probably even less common than) discussing the compatibility of SCSI controllers. I dont think you're gonna find much help in figuring out what exactly is going on because you're a niche user that probably makes up 0.0001% of their customer base.

I'm assuming the sata controllers either have a driver problem or perhaps not properly causing the motherboard to fall back to the different pcie modes. Perhaps if you manually set the pcie modes in the bios they would behave like they do in other machines you are testing on (provided the same OS is being used to narrow the issue down to the motherboard/bios).

edit: also why are you adding sata cards in the first place? Used up the 8 sata3 ports that come with the motherboard? Not that you shouldn't be able to use them if you want... but seems like an unnecessary step in the process you're making for yourself. It's not like these are hardware raid cards you're adding.

I wasn't looking for help. My post was just to say I have also had issues with the PCI-E X1 slots where I couldn't find a solution. Just because people choose less common configurations mean those issues are any less important.

[baretvaih]

Darth Ender wrote:
Not to be that guy, but discussing discrete sound card issues is like (well, probably even less common than) discussing the compatibility of SCSI controllers. I dont think you're gonna find much help in figuring out what exactly is going on because you're a niche user that probably makes up 0.0001% of their customer base.

I'm assuming the sata controllers either have a driver problem or perhaps not properly causing the motherboard to fall back to the different pcie modes. Perhaps if you manually set the pcie modes in the bios they would behave like they do in other machines you are testing on (provided the same OS is being used to narrow the issue down to the motherboard/bios).

edit: also why are you adding sata cards in the first place? Used up the 8 sata3 ports that come with the motherboard? Not that you shouldn't be able to use them if you want... but seems like an unnecessary step in the process you're making for yourself. It's not like these are hardware raid cards you're adding.

All 8 SATA ports are already in use - 2x850 EVO + 6xWD30EFRX connected. But I need to add 2 WD30EFRX more ...also now that Silverstone TS12 disconnects/reconnects after 5 mins or so... I am running Win 10 Fall Creators Update, and have set the "USB selective suspend setting" to disabled in power settings

[skellattarr]

baretvaih wrote:
All 8 SATA ports are already in use - 2x850 EVO + 6xWD30EFRX connected. But I need to add 2 WD30EFRX more ...also now that Silverstone TS12 disconnects/reconnects after 5 mins or so... I am running Win 10 Fall Creators Update, and have set the "USB selective suspend setting" to disabled in power settings

i don't use raid but i have one ssd one m.2 and three 3tb hdd hooked up to my system and i would lose my hdd's on boot tell i figered out that if i turn off fast boot the problem went away so give that a try
well i desided to try a software raid 0 with my 3 3tb hdd's after some studying on google search and man did it make my drives a lot faster i was able to backup 569 gb of data in 30 minutes where before it took 2 hours

[Falck]

Is it possible to flash this on ROG CROSSHAIR VI HERO (WI-FI AC) motherboard? or is it only for the one without the "ASUS" wifi?

[RobrPatty]

Beta BIOS 3008 for C6H/C6HWIFI/C6E: is on the first page. OP.

[Darth_Ender]

Just to be clear, since the 1st page seems out of date. The current Bios's seem to be the following. With the beta 6001 from the primary Asus support page being the newest release.

Elmor Beta :
3502 released Jan 24, 2018
3501 released Jan 10, 2018
3101 released Dec 20, 2017
3008 released Nov 28, 2017
0070 released Nov 24, 2017
0020 released Nov 20, 2017

Asus Beta :
6001 released Feb 12, 2018

Asus Release :
3502 released Jan 30, 2018
3008 released Dec 13, 2017
1701 released Oct 3, 2017
1602 released Sep 18, 2017
1501 released Aug 18, 2017

[Ryzen94511]

Rocking latest Beta 6001 BIOS, working great!
3,8GHz R7 1700
3400MT/s DRAM CL16

Keep up the good work.

I do have one problem with "ASUS real bench" where I get same error on stock/ OC settings.
"Program files modified or corrupted!". It passes Stress test normally, both stock or OC-ed, but bench ... Anyone?

[Theagg]

Just a quickie. Have any of these recent bios versions fixed the problems with PCIEx4 and PCIEx1 slots not being usable (ie being unable to have any more than two PCIe cards in the board (including 1 of them being the GPU). I'm still on ver 3008.

[rsquires]

Hello! Rage3D forum mentioned current beta bioses contain a tweak for Vega graphics in Ryzen motherboards. Can someone knowledgeable say if this affects only APUs with vega, or discrete Vega GPUs as well? I have a Vega64 card so this would be an interesting update!

[baretvaih]

I got those 2 new WD30EFRX to work in my Ryzen machine.

I bought 4th card - Startech PEXSAT32 - and it works perfectly - no BSODs, no instability. I intentionally bought it because it uses Marvell controller (like ST-LAB A-520 does). Both I-tec PCIe SATA III 2-channel Card PCE2SATA and Startech PEXESAT322I uses ASMedia - ASM1061 chipset, but PEXSAT32 uses Marvell - 88SE9128.
AMD X370 chipset is designed by ASMedia so does those PCIe cards using ASM1061 have some conflict with C6H causing those BSODs?