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.

[JohnnyKurzschlu]

You were able to put that thing to sleep? I can use hibernation (suspend-to-disk) but resuming from sleep always gives a series of Qcodes waiting for me to reset it, loosing all the data.
But didn't test it again in a while now...

But I'm guessing that relying on ASEGA makes work harder. The guys who code this are mostly electronics engineers btw - you wouldn't trust a pure software engineer for this as the electronics guys learn programming for a good reason 🙂

i tried lm_sensors from archlinux. didn't find a sensor. i really can't tell it's temp...

[Darth_Ender]

The sensors for ryzen boards have been out for a while just not incorporated into the vanilla kernel. Unfortunately i'm at work right now or I'd give you the git repo that i've been using since about a week after ryzen was released. It's been working fine for temp reporting for me the entire time.

[Muddy_Paws]

Darth Ender wrote:
The sensors for ryzen boards have been out for a while just not incorporated into the vanilla kernel. Unfortunately i'm at work right now or I'd give you the git repo that i've been using since about a week after ryzen was released. It's been working fine for temp reporting for me the entire time.

please share I beg you

[BlackBishop]

You don't even need to look for new sensors / kernel - you may force load previous module for temp monitoring - works well - same reading as in BIOS / windoze.

[Darth_Ender]

Muddy Paws wrote:
please share I beg you

I've been using this git branch since ryzen was released ...well maybe 5 days after.

https://github.com/groeck/it87.git

[Muddy_Paws]

Darth Ender wrote:
I've been using this git branch since ryzen was released ...well maybe 5 days after.

https://github.com/groeck/it87.git

thanks for that +rep

[JohnnyKurzschlu]

which module?

i tried around since the system was less stable with the new BIOS:
first, i just changed the multiplier to 40
without any change to voltages CPU went again up to 1.47v (!!!!) it's got a bit hot there
so i thought offset mode would bring me exactly the given offset apart. set offset for core voltage to -50mV
but when i went back to check it, it was a pretty constant 150mV lower...

What the heck does Auto mean for core voltage?
I changed it to -6mV (the minimum) and think i got what i wanted. this is confusing.
system is stable so far. now at 3.85 GHz. ( Is it still a constant frequency if i do so? seems like to me )
I made changes in the VRM, but setting things like standard power phase. I thought this could get me closer to what the core needs...

[Saikamaldoss]

I tried 1071 and man it’s vcore voltage is off.. it’s hitting 1.56 at times and temp hits sky high.
finally went back to 1401 which is the best for CPU and ram OC. They should discard all the versions and start building on 1401 and stable 4.0ghz at 1.32 to 1.35v and ram running 3200mhz 14-14-14-14-26-42

[HnS-CHH]

Ok, 1701 patched. I really don't get it using same ddr4 3466 setup as previous now error within 30 %. While I run easily 3200c14 very tight timing over most people. But somehow imc cannot handle 3200c12 or 3466c14?? How does other able to do 3466c14 while having lesser timing on 3200c14? I probably got a golden trash here. Although I don't see people post their stability on 3466c14.

[Saikamaldoss]

HnS-CHH wrote:
Ok, 1701 patched. I really don't get it using same ddr4 3466 setup as previous now error within 30 %. While I run easily 3200c14 very tight timing over most people. But somehow imc cannot handle 3200c12 or 3466c14?? How does other able to do 3466c14 while having lesser timing on 3200c14? I probably got a golden trash here. Although I don't see people post their stability on 3466c14.

First you need to update your system spec in your profile. You are having 16GB single rank kit ? If so, 3466 is easy. I am running 2 x 32GB F4-3200C14D-GTZ and getting 3200mhz with 14C is great for a duel rank 64GB kit *