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.
1,426 Views
2,794 REPLIES 2,794

Feo11 wrote:
Will it happen again?

What is the most stable BIOS version for my 1800X and my memories?


(1) Your system is old enough now to require a bios battery change. If this happens again, replace the bios battery.

(2) The latest BIOS is always best bios to be running, unless specifically noted otherwise.

RedSector73 wrote:
(1) Your system is old enough now to require a bios battery change. If this happens again, replace the bios battery.
Oh, I had not thought of it. Thank you

(2) The latest BIOS is always best bios to be running, unless specifically noted otherwise.


I understand that the versions from mine are practically more thought for the 2000 and 3000 series and would not give me anything more than the problems that you have been describing lately. Also, the BIOS 6401 not losing performance due to loss of a feature?

Thanks for everything again. Excuse my English.

Feo11 wrote:
Oh, I had not thought of it. Thank you.

Also, the BIOS 6401 not losing performance due to loss of a feature?
Thanks for everything again. Excuse my English.


No problem.

At least you have another language, some of us are stuck with only English as a known and google translate for everything else - like me.
Latest Bios has the most up to date AGESA Code https://en.wikipedia.org/wiki/AGESA and 99% of the time is best option to run.

Rikthir wrote:
Extreme just has all phases active at all times. For memory, not a big deal. For CPU, it makes a decent bit of extra heat. If you have any airflow, you should be fine, but you'd have to look at your VRM temps for your use case.

If you think it's shutting off due to over current, try raising the DRAM current capability, but at 1.35v I can't really see that. You can always try it though. I run mine at 130% on a Crosshair VII. 1.4v boot, 1.4v running. 130%/Extreme, 4x8GB gskill 3200c14@3600c16, manual SoC voltage 1.05, but always reads low in software/BIOS. I also have a profile at 3600-14-15-14-14-28-42-160nsRFC @1.5v and I've never had an overcurrent shutdown, so 1.35 seems unlikely to do it. 1.5v is nothing to sneeze at, but it's not obscene for daily. It's Karhu 30,000% stable, never higher than 41c/stick in software, but I run a monoblock and a memory waterblock because lolynot.

Extreme on SoC shouldn't be a big deal unless your voltage and LLC is set high. Extreme phase control and high/tight LLC on CPU is unnecessary unless you're going ham on an all core OC on the higher core count chips. That's IMO.

Ok, thanks.
I seem to need the 130% current cap and it's anyway just about limits, it won't force more current.

And I don't want LLC. I used it on an intel platform but with AMD I can't make sense out of it, so I use "Auto" there.
The CPU uses standard power phase control. I changed the SoC one and was worried it might harm something. But if it's just about temperature, i think that's fine.
The effect of SoC voltage seems to be almost no where.

But my system didn't crash again since I changed it, 8 1/2 days so far - while playing games in a VM and streaming and whatsoever. everything looks good and I'm happy ^^
Having an ASUS board?
Increasing the Capabilities in your Digi+ VRM can prevent your hardware from being shut off (relaxes over-current condition).
Do it if you DID NOT set bad settings but didn't get it stable. (i.e. your hardware is for overclocking, high destiny, whatever).

Alessio1989
Level 9
With BIOS 7803 now the MB refueses to boot if CSM is disabled, stuck at q-code 3b and CPU red led. To solve a clear CMOS must be performed and CSM must remain enabled.

Alessio1989 wrote:
With BIOS 7803 now the MB refueses to boot if CSM is disabled, stuck at q-code 3b and CPU red led. To solve a clear CMOS must be performed and CSM must remain enabled.


Same Issue with CSM but stuck on error code 43 instead, Flashed back to previous bios for stability, the new bios doesn't offer anything useful to this board

SpaceGravity
Level 7
It looks AMD will provide a code where manufacturers are able to choose what CPUs to support on what board. I really hope we get support only for the 4 CPUs they have announced (5600x-5800X-5900X-5950X). I think these will be enough for all Asus Crosshair owners with X370 chip.

SpaceGravity wrote:
It looks AMD will provide a code where manufacturers are able to choose what CPUs to support on what board. I really hope we get support only for the 4 CPUs they have announced (5600x-5800X-5900X-5950X). I think these will be enough for all Asus Crosshair owners with X370 chip.


If not enough BIOS capacity to support all CPUs at same time, maybe could be possible to provide two line of BIOS-es, i.e. to split supported CPUs in 1st line to Zen1&Zen2 and other BIOS line to Zen2&Zen3.

I am happy owner of CH6 from day1, from 1700, for a year now now on 3900x, really hoping in the future to be able to update it with 5900x or maybe even 5950x.

i've read that some manufactures are suporting Ryzen 5000 series on their x370 line up

i wouldn't expect less from Asus. That's why i always choose asus for mainboard since early 2000.
Asus Crosshair VI hero | AMD Ryzen 1700 | G.Skill Trident Z 3200Mhz CAS16 | Samsung 850 EVO 250GB | Seasonic S12II 620W | Ignorance is bliss!

r3dleh wrote:
i've read that some manufactures are suporting Ryzen 5000 series on their x370 line up

i wouldn't expect less from Asus. That's why i always choose asus for mainboard since early 2000.


maybe we can hope:
https://www.guru3d.com/news-story/amd-ryzen-5000-zen-3-cpus-spotted-working-on-a320-and-x370-motherb...