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,223,582 Views
2,794 REPLIES 2,794

Which ports? Because some SATA ports (2) are driven from CPU and some (6) from chipset.

Not SATA ports (internal HDDs are not causing any problem) but USB 3.0 ports:

AMD Ryzen™/7th Generation A-series/Athlon™ Processors :
4 x USB 3.0 port(s) (4 at back panel, blue)
AMD X370 chipset :
6 x USB 3.0 port(s) (4 at back panel, blue, 2 at mid-board)

baretvaih wrote:
Not SATA ports (internal HDDs are not causing any problem) but USB 3.0 ports:

AMD Ryzen™/7th Generation A-series/Athlon™ Processors :
4 x USB 3.0 port(s) (4 at back panel, blue)
AMD X370 chipset :
6 x USB 3.0 port(s) (4 at back panel, blue, 2 at mid-board)


I would guess there is a device limitation on Usb 3.0 or a TB limitation at the Usb ports?
Because its quite much TB which is pluged in there. I would guess the system crash by testloading the HDD's.
each reach 100mb/s, so 800mb/s through Usb might be a limitation but im not sure.

Its not a fix but if want, u can open up some the external HDD's cases and install the HDD direct inside via Sata 3.
(External HDD's are usual HDD's in a additional box + wire)

baretvaih wrote:
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


remove the plug and attach it. sometimes my steering wheel (T150) is not recognized, but there is no problem when I restart the pc. no problem without pulling the plug
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

I ve tested arround and reached 4Ghz encoding stable OC which i ve tested with Cinebench.
With 1.425V 150W 4Ghz would run but at 1.5V 160W its stable for Cinebench.

But the temps are incorrect, doesnt matter with Sense MI enabled or disabled.
It show me temps arround 82°C but the cpu cooler is only warm, not hot, if i touch the heatpipes direct, these r only warm.

To compare.. at 3,8Ghz 1.3725V 130W~ its at 50°C vs 1.5V 160W 82°C = 30°C+ for 30W? Thats wrong.
The real temp is 62°C NOT 82°C.

Its annoying that the fan spin up 100%, THIS need to be FIXED ASUS! 😞
I ve changed already 1x because of these wrong temps the thermal conductance paste, so no problem with that.

"Its not a fix but if want, u can open up some the external HDD's cases and install the HDD direct inside via Sata 3."

I will not open any of my external HDDs. I want to use them via USB bus. Besides I have 2 x Samsung 1TB 850 EVO + 6 x WD30EFRX already connected to SATA ports so all of them are already occupied.

"remove the plug and attach it. sometimes my steering wheel (T150) is not recognized, but there is no problem when I restart the pc. no problem without pulling the plug"

Removing/reattaching the plug does not fix anything, no matter how many times I repeat. Neither does if I remove some of those HDDs and attach them to USB 3.1 Gen.2 ports, still the same thing repeats.
I am considering to buy 2 more 2TB external drives and connect them to USB 3.1 Gen.2 ports (USB-C via adapter to USB-A) but then I may have to remove 3-4 drives before I can boot my computer after it was disconnected from mains.

"I would guess there is a device limitation on Usb 3.0 or a TB limitation at the Usb ports?"

If there are ports where I can connect devices to I expect them to work no matter how many of them are populated in every situation.


Still after all, C6H is best motherboard I have owned (processor: 1600x). Rock solid USB, not a single device dropout ever! I had very good experience with Maximus V Gene, USB stability also rock solid!

Does anybody know if PSU quality affects USB device stability? Crosshair/maximus boards have "TrueVolt USB" does it make any difference in practice compared to for ex. Strix boards or "mainsteam" mobos? Or does PSU quality generally affect mainboard USB stability?.

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


Not Meltdown/Specter specifically, but there's always this: http://seclists.org/fulldisclosure/2018/Jan/12 This is going to fall more on OS/kernel level fixes.

whiskey-foxtrot wrote:
Not Meltdown/Specter specifically, but there's always this: http://seclists.org/fulldisclosure/2018/Jan/12 This is going to fall more on OS/kernel level fixes.




The truth is, they made it intentionally or do you really think they suddenly found this out?
A mistake which wasnt discovered by these companys for over 20 years?

This is made intentionally, america spy always and they made a small backdoor for this.
Most chats.. social media all infos goes to america, this is obvious.

Now updates will fix this.. and make again one other backdoor open for "special acces" of course just to KEEP YOU SAFE.
... and everybody else too, so we need to know what you do, if we get somehow suspicious infos from your google search etc.
Welcome to America:cool:

The safety of a country goes above the rules and rights of each citizen.
Thats how they justify it. They created a system with rules and dont care about the rules.
Rather acting like a God.

And ive read such problems doesnt exist at phone processor...
Well.. there is everything already open, there was never a security, google was and is always able to see your data,
where you are and who did you call. Since google is preinstalled into the OS and android is much supported by google.
You might imagine the influence.

Short explained: They know..
Where you are, who you called/call
What you think or do via social media messages/chat messages.
What your favorites are, what you dislike.
Its even possible that they can see your through your phone camera if that is really needed.
Or public camera's.

Even if people argue, thats no true, well there is a high chance that this is true and even if its happen, you dont recognize it.
For real security, dont use a phone, dont use internet, play at a computer in your own home network.
If not, thanks for your sharing;)

Red Core wrote:
The truth is, they made it intentionally or do you really think they suddenly found this out?
A mistake which wasnt discovered by these companys for over 20 years?

This is made intentionally, america spy always and they made a small backdoor for this.
Most chats.. social media all infos goes to america, this is obvious.

Now updates will fix this.. and make again one other backdoor open for "special acces" of course just to KEEP YOU SAFE.
... and everybody else too, so we need to know what you do, if we get somehow suspicious infos from your google search etc.
Welcome to America:cool:

The safety of a country goes above the rules and rights of each citizen.
Thats how they justify it. They created a system with rules and dont care about the rules.
Rather acting like a God.

And ive read such problems doesnt exist at phone processor...
Well.. there is everything already open, there was never a security, google was and is always able to see your data,
where you are and who did you call. Since google is preinstalled into the OS and android is much supported by google.
You might imagine the influence.

Short explained: They know..
Where you are, who you called/call
What you think or do via social media messages/chat messages.
What your favorites are, what you dislike.
Its even possible that they can see your through your phone camera if that is really needed.
Or public camera's.

Even if people argue, thats no true, well there is a high chance that this is true and even if its happen, you dont recognize it.
For real security, dont use a phone, dont use internet, play at a computer in your own home network.
If not, thanks for your sharing;)

You spoke the truth my friend.

FoxTech
Level 7
@Red Core

Exactly. I mentioned this in another forum aswell.
I don't wanna wake dogs but this "security patches" they roll out now, could be more worst in privacy reasons.
Probably this update is a compatibality update to Governments new data-collecting servers.
Why I say this? Never saw such a reaction to any ohter security leak or ransomware attack, virus threat...
The whole world goes nuts atm about this. Something, Not a single hacker knew about this before.
In my eyes, this behavior is strange
Greetings