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

mito1172 wrote:
Processor stock speed is only 3.6 GHz


Thats wrong. If in the bios the Turbo is enabled and no manual oc is set, the Cpu frequency goes up to 3,7Ghz at this C6H.
Measure it with HWmonitor.

From 3,6 to 3,8 Ghz @Cpu the reported temps are correct and the system is stable.
When reaching 3,9Ghz and above, the system isnt stable, i had a crash in Cinebench and some while the system rebooted.
(might be because i dont wanted to go above 1.35V)

But so far about the cpu..
I was able to OC my ram from 3000 to 3200 above the max XMP info from the Ram without changing the timings,
for stability safety i did increase the voltage from 1.35 to 1.37.
Now my Ram runs at 3200 dualchannel CL14 1T stable, tested it serveral times with CB.

There is only a reading error of some programs or the sensor which is on the mainboard i guess.
Because my cpu runs at 3,8Ghz and not 3,6Ghz if this score would be with 3,6Ghz (as u can see in the picture below) i would be proud of this cpu 😉
But it isnt, anyway a good result, the Ram increase made a difference +10points to 1701 funny that this was the previous bios that ive used 😄
70020


My system crashed many times in row trying to get again on 3200, it didnt worked suddenly, so i went down to 3140
Now its at same timings again stable but the voltage is at 1,35 as it was before with 3000.
Also updated my cpu info, for encoding safety it runs at 3,8Ghz 1,35V and use at CB 130Watt.

skellattarr
Level 10
I have this problem ever since I tried bios beta 3008 the system would crash because of the page file it would say page file was accessed with larger than or equal to it even did it on the bios i have now 3101. what i did was increast the page file too 16gb my system has 32gb of ram so far no crashes but is there any harm in having the page file that large?
in the event viewer when it did crash it said bugcheck event id 1001The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x00000000000018e0, 0x0000000000000002, 0x0000000000000001, 0xfffff803ce67e028). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e39d82cc-ca30-4b00-a0e5-dec69e3116c7.
amd ryzen 9 3950x
CROSSHAIR Viii hero
Corsair Hydro Series H115i
G.SKILL Trident Z 3200mhz 64gb 4x16 timings 16,18,18,38
asus rog strix gtx 1080
TOSHIBA 3TB hdd 3x a total of 9tb, 10 tb hdd and a 1tb mushkin ssd
corsair axi 1200i 1200 watt psu
thermal take view 71 case

Waxinator
Level 7
I would just like to take the opportunity to report my solution to all my problems with
fans jumping into full speeds and processor temperature erratic fluctuations.
I tried all BIOS from 901 to 1501 but stayed on 1403 as that worked best for me.

I had five months (apr-aug) of almost daily problems with restarts in order to run this MB.
For these last four months (sep-dec) I have had not a single problem with this MB.

What I did was installing a small 80 mm half speed quietly running fan onto my MB.
The fan is placed laying over and ventilating the problematic sensor chip (left fan).
I also put a fan over of my M.2-SSD to cool that drive (right fan).

Happy New Year to all of you out there !!! 🙂

69989

Waxinator wrote:
I would just like to take the opportunity to report my solution to all my problems with
fans jumping into full speeds and processor temperature erratic fluctuations.
I tried all BIOS from 901 to 1501 but stayed on 1403 as that worked best for me.
[Eaten by mice] 🙂


Interesting indeed! Now thinking about additional heatsink 4 the chip. Maybe, it'll be useful.
By the way, which chip exactly? Currently too lazy 4 opening the case and searching fan area - evening...

dAlexis wrote:
Interesting indeed! Now thinking about additional heatsink 4 the chip. Maybe, it'll be useful.
By the way, which chip exactly? Currently too lazy 4 opening the case and searching fan area - evening...


It's the SUPER I/O chip in this picture. The chip is hidden under the plastic cover just bellow the graphic card slot.
A heatsink can't be fitted here, but a fan can ventilate the chip.

70037
70039

Waxinator wrote:
It's the SUPER I/O chip in this picture. The chip is hidden under the plastic cover just bellow the graphic card slot.
A heatsink can't be fitted here, but a fan can ventilate the chip.

[Eaten by mice]



Thanks! Looking on the images, I understood, why the MB is working 4 me. CPU & GPU are liquid cooled, case is large, and it's not too hot in the area. But something with regular cooling...

By the way! The plastic can be easily cut after warranty period. Not steel indeed 😉 (I already made a large hole in metal, when moving a PSU in Fractal Design Node 304 NAS case) After hole in the plastic - thermal glue and heatsink is installed. The area is hot, but self-made heatsink may be long; 5-10 cm upper and the chip will be cool. Required piece of aluminium is not a problem 2 find.

P.S. placing such chip under plastic is NOT good indeed. It should be somewhere near post codes indicator.

dAlexis wrote:
Thanks! Looking on the images, I understood, why the MB is working 4 me. CPU & GPU are liquid cooled, case is large, and it's not too hot in the area. But something with regular cooling...

...[eaten by my cats]...

P.S. placing such chip under plastic is NOT good indeed. It should be somewhere near post codes indicator.

Thank you dAlexis for your feedback and comments about my findings ! :eek::eek::eek:

Syaoran
Level 7
Although 3,600 or for that matter, anything above 3,466 is now completely unstable at higher voltages than I never needed before for stability. The 3101 BIOS does seem to help a lot with tighter timings at 3,200 when it comes to Stilt's settings. Before, 3,200 Stilt's tight timings were not stable for me but are rock solid on my F4-3600C15 G.Skill memory. I guess that is some consolation but I can't get anything near the 3,560 I had before updating, which is truly disappointing.

Why is BIOS flash back disabled for 3008 and 3101 to go back to anything that starts with a 1 or 9?
Syaoran

Clouseau
Level 7
@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.