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

Clouseau wrote:
@Syaoran - what helped me finally iron out the ram timings was the departure of using any of the presets or using the ram calculator. Left all the voltages as before and only changed all the ram timings to Auto. With the ram speed still at its desired setting, only changed the first four ram timings to their desired setting (for me 15-15-15-15) for Tras and Trc, I referred to the XMP settings as stated by Typhoon Burner in ns. Tras was listed at 19.876ns. My BCLK is set to 100.4. Therefore Tras calculated to ((1733x100.4) x .019875)/100 = 34.5878 so 35 was the new setting. Those were the only two ram timings that XMP was used as reference. The rest were provided by the bios except for TrdrdScl and TwrwrScl which I referred to the Stilt's values of 2. I may have lost a nit picky amount of bandwidth according to Aida64 but the latency went down from 65.6 (when using the presets) to 65.3 (using the new values). You may want to give this a try with the 3560 speed you were able to use before.

EDIT: After all was said and done, switched all the timing values, aside from the ones mentioned above, off of Auto to what the bios trained the ram at.


The BIOS training the RAM isn't so much of the issue. It's stability. I can boot into Windows at the old settings I used and even at 3,501 with things on auto. When testing the RAM though, it doesn't pass and in games that use a lot of memory, the system will blue screen.
Syaoran

Syaoran wrote:
The BIOS training the RAM isn't so much of the issue. It's stability. I can boot into Windows at the old settings I used and even at 3,501 with things on auto. When testing the RAM though, it doesn't pass and in games that use a lot of memory, the system will blue screen.


I think you have to wait for the next stable bios release, so far i know companys, they fix problems for the most people first.
Means.. Ram which is above 3200 will be cared later than stability issues, misreading of temps, fix of OC bugs etc.
If you are lucky, they might work on it but as you can read on the Asus support page of the C6H under-> specs its unsupported by the mainboard.
So the priority of higher ram above 3200 is low, likely kindness if they fix it.

Syaoran wrote:
The BIOS training the RAM isn't so much of the issue. It's stability. I can boot into Windows at the old settings I used and even at 3,501 with things on auto. When testing the RAM though, it doesn't pass and in games that use a lot of memory, the system will blue screen.


The reason for the post was what ended up being a different approach that has garnered more stability than I had in the past. CLDO_VDDP along with the CAD Bus settings are all on Auto. The one thing that I noticed about all the timings, the most stable ones for me all shared the same tertiary timings except they all had Twrrd wrong. The bios provided the correct value. The slightly looser Trfc timings also added to needed stability; Tfaw as well. Was sharing what finally ironed out all the kinks in regards to stability for me in hopes the method may work for you and others as well. The only conversions needed was for Tras and Trc from the XMP profile unique to the flavor of ram being used. Keeping the timing in ns the same in regards to the desired operating speed.

mito1172
Level 9
3008 BIOS is not doing a cold boot ram 3200 MHz very good

70051
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

mito1172 wrote:
3008 BIOS is not doing a cold boot ram 3200 MHz very good

70051


You can set the trc manually to 48.
Mine works at 3200 CL14 but each restart now it has problems with it, set it again up and it works.
Since thats annoying, i ve set it to 3140 CL14 and now it doesnt complain each start.

Red Core wrote:
You can set the trc manually to 48.
Mine works at 3200 CL14 but each restart now it has problems with it, set it again up and it works.
Since thats annoying, i ve set it to 3140 CL14 and now it doesnt complain each start.


standard ram profile no need to make any adjustments for me. no problem when you restart
70071
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

mito1172 wrote:
standard ram profile no need to make any adjustments for me. no problem when you restart
70071


The XMP profile of my ram show CL14 @3000mhz 1.35V but i went above it.
It can reach 3200 with CL14 but at each restart it makes problems and need to set it up again.
So it works without any problems at 3140 CL14 which is above its max XMP clocks.
Also your ram is 8gb each ram stick, mine is 16gb each ram stick, of course your ram is made to reach higher clocks above 3200mhz.

Red Core wrote:
The XMP profile of my ram show CL14 @3000mhz 1.35V but i went above it.
It can reach 3200 with CL14 but at each restart it makes problems and need to set it up again.
So it works without any problems at 3140 CL14 which is above its max XMP clocks.
Also your ram is 8gb each ram stick, mine is 16gb each ram stick, of course your ram is made to reach higher clocks above 3200mhz.


16 GB single-ram and 3000 mhz yours? okay then. I do not have problems xmp 3008 BIOS da. I have 2 x 8GB RAM, G.SKILL Flare X DDR4-3200Mhz C14 16GB (2x8GB)
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

rsquires
Level 9
Any word on whether Ryzen is subject to the CPU security bug? News sites are saying bios updates will also be needed.

This is quite small issue, but...

the following happens only after when computer was disconnected from mains and then reconnected. When restarting or booting after shutdown (so that computer was not disconnected from mains in between), all works OK.

I have 8 external Seagate Backup Plus Slim 2TB USB 3.0 HDDs connected to those 8 USB 3.0 ports at backpanel.

I disconnect my computer from mains and then reconnect power cable. All those 8 HDDs try to spin up. But this pre-booting fails after ~2sec and computer shutdown. Then comes ~3 sec silence and then all those HDDs try to spin up again - and again after ~2 sec, computer shutdown. Also when I try to turn on my computer this will still repeat in loop (pressing power button does nothing) UNLESS I disconnect at least 1-2 of those 8 HDDs so that no more than 6-7 are connected (depending on what ports are left populated), computer boots OK. After that I can reconnect all drives and boot works OK with all drives connected even after shutdown.

This issue has been around since I bought my C6H last spring and updated BIOS to 1201 by then. I am now running BIOS 3008 - but this issue still remains.

Connected HDDs (purchased over several years):

Seagate BUP Slim BK: firmware: 0304, capacity: 2TB, cache size: 31MB
Seagate BUP Slim BL: firmware: 0304, capacity: 2TB, cache size: 128MB
Seagate BUP Slim BK: firmware: 0304, capacity: 2TB, cache size: 128MB
Seagate BUP Slim SL: firmware: 0304, capacity: 2TB, cache size: 31MB
Seagate BUP Slim BK: firmware: 0107, capacity: 2TB, cache size: 31MB
Seagate BUP Slim BL: firmware: 0304, capacity: 2TB, cache size: 128MB
Seagate BUP Slim SL: firmware: 0302, capacity: 2TB, cache size: 31MB
Seagate BUP Slim BK: firmware: 0304, capacity: 2TB, cache size: 128MB