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

Darth_Ender
Level 9
Well, with some more playing around with voltages and adding a custom P2 to 1600mhz 900mv and letting P1 and P0 be auto, i have a stable 4Ghz OC that sits around 70-75C after 20min of all core linpack. That + 3200mhz ram, is looking pretty ideal given my setup.

Hello to all here reading...

First, let me start with the problem I'm having since I bought my rig 1 month ago.
With every new BIOS (currently on 3502) I was unable to isolate bug/problem that most of you said it's no longer a problem since april BIOS release last year.

Whenever I tried to read temperatures of some application (AIDA 64, Corsair LINK, CPU-Z, ect...), my temperature on CPU or VRM drops down to -70*C or -42*C, and my two intake fan coolers stop sppining. It doesnt happen as soon as I open application to read temp values, but after some time...sometimes after 20min or sometimes after 1or2 hours of web surffing, playing, enjoying music.
At first I was blaming Asus software, but since I removed all of it, even Corsair LINK (Corsair Link dongle is however still conected to PSU and internal USB2 header)...all other apps that can read temperatures, mostly AIDA 64 (with logitech LCD support ON)...problem still happens. I tried numerous BIOS-es, reverted back to old ones and new ones, via flashback option (and reseted BIOS to default before updating it + remove battery for 10min), still problem is here.

+ I have very high DPC Latency (micro freezing sound and video) when starting AIDA 64 or CPU-Z. Is that normal? I found what is cousing high dps latency, it was my external HDD WD Elements 1.5Tb USB3.0...but still after it is disconnected, AIDA 64 and CPU-z high DPC latency still occurs.

If any of you can help, I would really appreciate it...
Thanks in advance!!!

Bjes99 wrote:
Hello to all here reading...

First, let me start with the problem I'm having since I bought my rig 1 month ago.
With every new BIOS (currently on 3502) I was unable to isolate bug/problem that most of you said it's no longer a problem since april BIOS release last year.

Whenever I tried to read temperatures of some application (AIDA 64, Corsair LINK, CPU-Z, ect...), my temperature on CPU or VRM drops down to -70*C or -42*C, and my two intake fan coolers stop sppining. It doesnt happen as soon as I open application to read temp values, but after some time...sometimes after 20min or sometimes after 1or2 hours of web surffing, playing, enjoying music.
At first I was blaming Asus software, but since I removed all of it, even Corsair LINK (Corsair Link dongle is however still conected to PSU and internal USB2 header)...all other apps that can read temperatures, mostly AIDA 64 (with logitech LCD support ON)...problem still happens. I tried numerous BIOS-es, reverted back to old ones and new ones, via flashback option (and reseted BIOS to default before updating it + remove battery for 10min), still problem is here.

+ I have very high DPC Latency (micro freezing sound and video) when starting AIDA 64 or CPU-Z. Is that normal? I found what is cousing high dps latency, it was my external HDD WD Elements 1.5Tb USB3.0...but still after it is disconnected, AIDA 64 and CPU-z high DPC latency still occurs.

If any of you can help, I would really appreciate it...
Thanks in advance!!!


I have given up trying to manage temps on this baord. Voltages, temps, bus speed are all thumb sucks really. The negative temps are really odd though. The way i fixed an issue i had was to select one of the OC profiles, i uesed the 3600mhz memory one. It reset the BIOS too defaults. I then set everything manually and it seems to be working. i dont think that i will ever use the word stable with this build, ever.

What memory are you using and what timming is it running at? I have found anything below 2400mhz is terrible. I have 32gb of generic 2133mhz memory and it is horrible, lag /stutters almost all the time.

mrjonnyrock wrote:
I have given up trying to manage temps on this baord. Voltages, temps, bus speed are all thumb sucks really. The negative temps are really odd though. The way i fixed an issue i had was to select one of the OC profiles, i uesed the 3600mhz memory one. It reset the BIOS too defaults. I then set everything manually and it seems to be working. i dont think that i will ever use the word stable with this build, ever.

What memory are you using and what timming is it running at? I have found anything below 2400mhz is terrible. I have 32gb of generic 2133mhz memory and it is horrible, lag /stutters almost all the time.


At the moment, CPU on default and memory on 2666 Mhz(15,15,15,36,51,1T)since I went nuts with tweeking everything. I use to run CPU on 4000Mhz and RAM on 3200Mhz...but I don't want to run it without exact temperature reading. I never had this kind of stupid issues with my old rig Asus P6T, i7-920 o.c. to 3800, 12Gb Corsair XMS3 @ 1600Mhz. Most stable MB/PROC/RAM combo ever, 9 years without problems on Win7 PRO - 64Bit.

I read about other X370 motherboards and I regret not buying cheeper GA-AX370-Gaming K7 with 3200Mhz RAM speed out of box, instead I went for ASUS which was always my first choice in the past.

mrjonnyrock wrote:
I have given up trying to manage temps on this baord. Voltages, temps, bus speed are all thumb sucks really. The negative temps are really odd though. The way i fixed an issue i had was to select one of the OC profiles, i uesed the 3600mhz memory one. It reset the BIOS too defaults. I then set everything manually and it seems to be working. i dont think that i will ever use the word stable with this build, ever.

What memory are you using and what timming is it running at? I have found anything below 2400mhz is terrible. I have 32gb of generic 2133mhz memory and it is horrible, lag /stutters almost all the time.


The issue was identified as having more than one program polling PCH. The problem appeared to have been resolved when some individuals chose to just have one program poll the PCH. When opening HWiNFO64 for the first time a window pops up stating that it detected that the board appears to "what ever type of sensor". The PCH is that sensor.

Clouseau wrote:
The issue was identified as having more than one program polling PCH. The problem appeared to have been resolved when some individuals chose to just have one program poll the PCH. When opening HWiNFO64 for the first time a window pops up stating that it detected that the board appears to "what ever type of sensor". The PCH is that sensor.


Thats what stats look like at 4hgz, and HWiNFO64 is the only thing i a m using to monitor.

mrjonnyrock wrote:
Thats what stats look like at 4hgz, and HWiNFO64 is the only thing i a m using to monitor.


My own experience has shown that the fans are sensitive to the Tcke setting; the very last ram timing item. For me, the way my rig is set up, Tcke of 8 provided the best results. When on Auto the bios wants to set the value at 9. Since having set it to 8 I no longer have fans stopping. The value may be different for others. All I know is what finally worked for me. Just for reference have included a file of my bios settings. The synchronicity of the ram timings plays a huge part. As we have all found out, another's settings may not work as well for someone else.

Darth_Ender
Level 9
So i've been checking to make sure this config is all stable. So far so good.

Got some readings from phoronix that let me know i'm in the right ballpark.

Compared to the stock 1800x in this test below, my numbers are anywhere from 12-20% better. sometimes more and a couple times less. Not bad. Could probably do better if i put the other two fans on my radiator that i never installed.

(mine are at the end labeled 4Ghz 3200Mhz)
https://openbenchmarking.org/result/1802195-FO-1802172FO52

this is done with bclk at 109Mhz, all pcie at gen 3 cept usb at gen2, cpu custom p-state p2 at 1.6Ghz 900mv, p1 and p0 at auto (causes system to clock p0 at 4Ghz @ 1.35v). I'm using offset voltages to bring that up a bit. Ram is at 3200Mhz 14 14 14 - but it's rank 2 being that it's 64GB.

Temps max at around 75C, leading eventually to the cpu throttling frequency down to 3.8Ghz. I really should put all the fans on the radiator rather than half. With half, it seems incapable of dealing with the 130-ish wattage the cpu is putting out when under load. And when playing with voltage at 4GHz, it's _very_ easy to hit 200watts on this cpu that's supposedly designated for 95w tdp. Every 0.1v you can lower and be stable is significant at those speeds.

I've had 0 crashes after a couple days of some very strenuous stress testing, despite the high temps i'm letting it reach. So i'm happy with this bios - even if the same company seems to make so much better ones for intel when it comes to basic stability.

Darth_Ender
Level 9
if memtest86 says your ram is bad, then your cpu or ram is corrupting memory. The program simply doesn't make false positives. It's old, the code is well reviewed, it's not dependent on anything about the OS if you boot directly to it. If it says something is wrong, then something is wrong. It may not be a physical defect, but data is getting corrupted and you would get corruption if nothing is changed under a normally operating setup under similar strain.

in a similar vein, other synthetic stress testers put the cpu into levels of stress that are beyond realistic - and to an extent that's the point. If you survive it, you can survive anything. OCCT with avx is what i use for cpu and memory stress testing. Now it wont test if your memory is faulty, but it will stress it and your cpu to the limits. Some people run it for 24 hours, to me, i just run it for about half an hour to an hour. If it survives, it's good enough for me.

But i would totally not bin memtest86. It's an extremely useful program in tracking down bad blocks of ram if you've otherwise, put your system in a stable setup and still get weird issues that can really only be faulty hardware.

However you feel is the way you feel. I happen to have a different opinion about the program. Your experiences are different from mine. Does not make either opinion more or less correct than the other. Like stated, I lost all confidence in the program when it failed ram that worked perfectly after it failed. What the cause of the failure is meaningless. The same ram functioned perfectly in the setup it failed in. I was asked what I used and answered. Does not mean Memtest86 is a bad program. It is just a program I had a bad experience with. Chalk it up to whatever you like. Does and will not change how either of us feel about the program.