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,152,359 Views
2,794 REPLIES 2,794

PwnSensei wrote:
yes I have. The button does not light up ever

UPDATE: problem solved, here is more information
I noticed on a youtube video that when the system is off the "clear cmos" button on the back, the one next to the BIOS button, is supposed to be lit up. Mine wasn't lit up. There was no way to get it lit up while the system was off.
After some testing I noticed that with the PSU switched off, if I were to press the power button, the on-board leds would lit up for a few seconds.
1. prepare usb stick and plug it in
2. Switch the psu off
3. Press power button
4. Quickly press the BIOS button on the back to start the flashback tool
5. Once the flashback tool starts, switch the PSU back on
Now the bios flashback tool will keep working for the entire duration of the process.
Clearly this is a dangerous operation. Only do this if you're desperate like me and do not blame me if things go south. Blame ASUS for ****ing up.


I changed the name of the interesting bios and made it with flash ez
AMD Ryzen 7 1800X 3.6 GHZ (NOCTUA NH-U12S SE) ASUS ROG CROSSHAIR VI HERO (Sapphire Nitron+Radeon RX 580 4G) G.SKILL Flare X DDR4-3200Mhz C14 32 GB (4x8GB) Samsung 970 PRO 512 M.2 SSD \Samsung 850 PRO 512GB 550MB-520MB/s Sata3 SSD

6808 and 6903 were pure rubbish, trying now on 7002 and so far seems fine... At least for now I didn't get random q-code 2 or random q-code 8 at runtime like i got with the previous firmwares.

Just a note: flashing from 6401 to 7002 and then resetting everything to run b-die RAM @ 3200 had a first long 2 minute or more of boot with different q-codes before proper OS loading, which may looks like a freeze for most impatient people...Maybe it was for the different microcode.. All the following boot works fine in a couple of seconds, even from a complete power down with the traditional and undocumented double boot.
So, I advice simply to wait at least a couple of minutes before starting panic mode when you upgrade or downgrade the BIOS and then change a lot of settings..

Alessio1989 wrote:
6808 and 6903 were pure rubbish, trying now on 7002 and so far seems fine... At least for now I didn't get random q-code 2 or random q-code 8 at runtime like i got with the previous firmwares.

Just a note: flashing from 6401 to 7002 and then resetting everything to run b-die RAM @ 3200 had a first long 2 minute or more of boot with different q-codes before proper OS loading, which may looks like a freeze for most impatient people...Maybe it was for the different microcode.. All the following boot works fine in a couple of seconds, even from a complete power down with the traditional and undocumented double boot.
So, I advice simply to wait at least a couple of minutes before starting panic mode when you upgrade or downgrade the BIOS and then change a lot of settings..


nevermind, just got q-code 8 at runtime...

Alessio1989 wrote:
nevermind, just got q-code 8 at runtime...


This is definitely my last asus mobo.

I increased of 1 step the socket and the RAM voltage (although both they were already set to the optimal values), seems more stable. The funny is that in every BIOS config I used every time I tested it for hours with memtest64 obtaining always zero errors..

UPDATE: and... another q-code 8 at runtime with DRAM orange led blinking... -_-

vbraun wrote:
Also tried flashing 7002, suddenly random bit patterns blinking on my 2 screens. Power cycled after a while, system did not boot.

Bios flashback to 7002 works.

My recommendation: prepare the USB stick before attempting to flash 7002...


I usually just do it it through the bios but this update has something wrong with it. I'm currently on an older one.


@PwnSensei: my qcodes were going crazy too.

Falck
Level 10
Yeah. This is the first BIOS I get the flashin 8 QC when OCing. And the LED on the board report graphicscard-error when I use DisplayPort (White LED keeps lit). Is possible to override if booting with HDMI cable and switch to DP after Windows login.

Falck wrote:
Yeah. This is the first BIOS I get the flashin 8 QC when OCing. And the LED on the board report graphicscard-error when I use DisplayPort (White LED keeps lit). Is possible to override if booting with HDMI cable and switch to DP after Windows login.


I've been having the white led stay on for along time, like 4 or 5 bios versions, everything still works but the monitor wouldn't turn on until I was booted into windows, a restart would make it go away and then sometimes It would be just fine for a week. Haven't hooked up an hdmi cable to see if it goes away completely because besides the delay before the monitor turns on it doesn't really mean anything.

skellattarr
Level 10
i have been on bios 6301 forever no problems with it. with all the problems i have been hearing with all the newer bios I will stick with this one forever 6301 is my final bios
amd ryzen 9 3950x
CROSSHAIR Viii hero
Corsair Hydro Series H115i
G.SKILL Trident Z 3200mhz 64gb 4x16 timings 16,18,18,38
asus rog strix gtx 1080
TOSHIBA 3TB hdd 3x a total of 9tb, 10 tb hdd and a 1tb mushkin ssd
corsair axi 1200i 1200 watt psu
thermal take view 71 case

6903 crashed me like I haven't seen since the early days. Lots of weird numbers coming out of the different voltages etc.
7002 is back to stability and running just fine at 4300mhz.
Memory at 3000mhz 64GB 68 OHM.
Very happy with new bios thus far. Installed it from USB drive using the bios flash tool in the bios without issues.
However, I can attest to having a massive issue a couple bios's ago that took me 2 hours to get my machine to boot so I feel anyone having issues atm.