cancel
Showing results for 
Search instead for 
Did you mean: 

Crosshair VI Hero: UEFI build update thread

Raja
Level 13
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.
2,153,054 Views
2,794 REPLIES 2,794

Been running 6808 since last night and have done some experimentation.

As everyone knows, Precision Boost is broken, so I'll pass over that.. nothing I did could make it better (configuring cTDP, Performance Enhancer, etc..). On the plus side, P-state 0 works (the rest are, seemingly ignored, but it does downclock... just without dropping voltage).

Memory compatibility seemed unchanged when running my dual rank 2x16GB DDR4-3600 CL19 kit... I could still only hit DDR4-2400 CL15 with it.. while my wife's ASRock AB350 Gaming K4 can run it at 3200 CL19 without issue (didn't try higher or tighter, but that passed a good half hour of memory stress testing and benchmarking, which was enough for me considering it won't even POST on my Crosshair VI Hero at 2667 with any timings).

While testing that memory in my wife's system, I felt I should experiment with 4x8GB as well as 2x8GB to see if there's been any improvement. Noticed nothing with 2x16GB, DDR4-3600 CL15 is still a bit sketchy. However, 4x8GB, which previously would not POST above 2667 CL15 (and not stable above 2400 CL15), now works at 3200 CL14... and I'm just blown away! I'm not sure it's the BIOS (nothing much seems to have changed, honestly) or if somehow something else changed, but I tried everything to get this memory to work together before without success... now it works like it's supposed to (running at FlareX 3200 CL14 XMP timings).

Falck
Level 10
The last BIOS breaks my DRAM OC 😢

Falck wrote:
The last BIOS breaks my DRAM OC ��


I screwed around for about 30 min and no matter what I set my voltage to under heavy load the vcore drops to 1.28 and the clocks sink to 3.6, this isn't a bios update its a system crippler. have to use bios flashback if you want to revert.

Falck
Level 10
CPU OC seemed ok on my board, but I haven't had the time to test that. But, OC'ing dram to 3466, that worked with last BIOS, it won't post with 6808. 3200 works (XMP)

FoxTech
Level 7
Another BIOS for this board in combination with a 1800X without any steps forward. (DRAM related)
DRAM problems when trying to go over 3200MHz (3466 Platinum) Flashed the bios 2 times in a row to avoid any errors + latest Chipset 18.50.16
With the older BIOS, I was at least able to boot and work on desktop with 3333. But wasn't stable enough. Now, I get F9 Error by changing the slightes setting.
Going back to 6401...

@Deflated Last Fan problems with 31xx
I have a mix of PWM and DC fans without any issues. No external Fan-Headers.
Greetings

FoxTech wrote:
@Deflated Last Fan problems with 31xx
I have a mix of PWM and DC fans without any issues. No external Fan-Headers.

Thanks FoxTech. I might have to try a full power down battery out clear cmos and see where that gets me. I read how to do a proper clear cmos ages ago on OCN but it's been a while. Gonna look for it and try it out.

SaLSouL
Level 10
So CHVIe is still waiting on a AGESA update to 0070, the x370 - I -gaming was waiting too, it seems that asus has bunny-hopped the 0070 update in favour of 0072 the X370-I-Gaming just got updated to AGESA 0072 here is hoping the CHVIE gets the same treatment as that is now the only x370 board to not get any update to either 0070 or 0072.

Trylen
Level 7
I have often wondered.. why do AGESA versions reset with the next version of the upcoming CPUs/chipsets? Why not a Generation/update/version sort of thing?
It be easier to understand something like R1.18.23 for first gen ryzen , update 18, version 23. Dunno...

Also sad that I have both the CH6 Wifi and a TUF b450M-plus (for my linux box), the Tuf board already has the 0072.. but the CH6 is waiting... such is life..

Trylen wrote:
I have often wondered.. why do AGESA versions reset with the next version of the upcoming CPUs/chipsets? Why not a Generation/update/version sort of thing?
It be easier to understand something like R1.18.23 for first gen ryzen , update 18, version 23. Dunno...

Also sad that I have both the CH6 Wifi and a TUF b450M-plus (for my linux box), the Tuf board already has the 0072.. but the CH6 is waiting... such is life..


Couldn't agree more!

I've also noticed lower tiered boards getting updated before CH6/7 - I seem to remember lots of complaints about why CH6 was getting updates before everyone else - maybe they decided to do it the other way this time..... though you would have thought higher tiered boards would be updated first. The Prime X370 Pro had 0072 about a week ago.
About me: I am dyslexic and DO occasionally miss things!

There are 10 types of people, those who understand binary, and those that don't.
F people in 10 don't understand hexadecimal

bigtop1967 wrote:
Couldn't agree more!

I've also noticed lower tiered boards getting updated before CH6/7 - I seem to remember lots of complaints about why CH6 was getting updates before everyone else - maybe they decided to do it the other way this time..... though you would have thought higher tiered boards would be updated first. The Prime X370 Pro had 0072 about a week ago.


the higher tier x370 board "IS STILL WAITING" for 0070 no update for the CHVI Extreme at all since december last year. It remains THE ONLY x370 board without 0070 or 0072.... 😐