Crosshair VI Hero: UEFI build update thread

[MunkeyBalls]

Q-Code 8 normally relates to CPU or memory instability. I would reseat the CPU if you haven't done so already. Some earlier CPU cooler mounting kits tend to put too much pressure at the rear if overtightened.

I tried reseating, running in differen't ram slots etc... Then I eventually gave up and bought a different motherboard....

Now this new board was lighting up a red CPU led, which also indicated something was wrong on the CPU side. Same strange behaviour where the light would keep burning even after taking out the PSU cable and removing the battery.

Then I noticed something odd... I pulled out the DisplayPort cable, and voila, the light turned off. I quickly replaced the DisplayPort cable with a regular HDMI cable and the PC actually booted up (still testing the new motherboard). Then I went to the amazon page of the DP cable I bought (and have already been using for months) and took a look at the 1star reviews. It seems these cables feed back 3v to the mainboard which causes a whole host of issues with booting and resuming from hibernation.

This was really a hair pulling experience, but maybe my findings help someone else.

I actually really like the new mainboard though, it boots up lightning fast compared to the slow post times of the Asus Crosshair, and the fan control actually works... Just one problem, there is a high frequency constant noise on the audio output. I still have a new CPU and PSU on the way back (ordered in a rush after the new motherboard also didn't post, figured either of the 2 had to be broken.. Would never have expected a stupid display port cable to be the culprit). I will probably try the new PSU with the new MB to see if this fixes the high pitched noise and in that case I'll say goodbye to the Crosshair. If that doesn't work I guess I'm still stuck here waiting for updates on the post times / crazy fan control.

[darkvader75]

I loaded the bios Elmore listed. I havn't had any fan controller issues.

[quasimodo18]

The 6301 BIOS is still not on the ASUS support page. Is this an interim bug/beta release and not official?

[FoxTech]

6301 is a beta Bios
I run it since a few days without any issues.
Seems, they updated the AGESA Code? Now my DRAM ist capable to run at 3333MHz

[Tiburan]

Using the beta as well, but I still have issues with my W_PUMP connector loosing power from time to time.
Quite frustrating.

[gupsterg]

The 6301 BIOS is still not on the ASUS support page. Is this an interim bug/beta release and not official?

TBH pretty much many of the publicly released betas became "Official". You could compare a beta and later the same version numbered "Official" and byte for byte they were identical. So I really wouldn't get too hung up if UEFI is beta or "Official".

TBH "Official" are only bug free until one is found.

6301 is a beta Bios
I run it since a few days without any issues.
Seems, they updated the AGESA Code? Now my DRAM ist capable to run at 3333MHz

AGESA was the same as previous builds.

I personally experienced/believe that testing needs to be varied and of some length on Ryzen. For example I do reruns of tests on same POST, different POST and even POSTs were power was completely removed from rig prior to POST. Only yesterday I passed a setup of 3466MHz C15 4x8GB on my 2700X+C6H of 400% in HCI Memtest (~4hrs), on a repost it failed within minutes. Basically the settings used for profile were not correct and POST to POST training variance was occurring.

Using the beta as well, but I still have issues with my W_PUMP connector loosing power from time to time.
Quite frustrating.

If you are using UEFI 6301 with ASUS WMI it does not fix fan PWM issues if you use applications which do not use the "communication" method. So you need to be using UEFI and SW supporting ASUS WMI.

Currently the applications I am aware of that use the new implementation are:-

- HWInfo v5.88 or later
- HWMonitor Beta: http://download.cpuid.com/betas/hwm_b17.zip
- SIV 5.32 or later
- CPU-Z Beta: http://download.cpuid.com/betas/cpuz_a0.zip
- AIDA64 v5.98.4800 or later

Anything else which accesses Super IO chip could cause you issues, AFAIK even ASUS utilities like Ai Suite, etc.

[FoxTech]

Hello gupsterg

After I posted here, I found out, that AGESA is still 1.0.0.2.
I was too srprised, running my Dram at 3333MHz.
Well, till yesterday... Wont run stable anymore. Win-StopCode told me Nvdia driver issues, Windows Kernel and others.
The whole variety of errors.
Now I stick again with 3200MHz on my ram. No BSOD since.

Why do we don't see AGESA improvement? Even the MSI B350 Tomahawk (a cheap product) offers 1.0.0.4c since july 2018
Maybe Asus want us to buy the CH7 ;-)

[gupsterg]

Hello gupsterg

After I posted here, I found out, that AGESA is still 1.0.0.2.
I was too srprised, running my Dram at 3333MHz.
Well, till yesterday... Wont run stable anymore. Win-StopCode told me Nvdia driver issues, Windows Kernel and others.
The whole variety of errors.
Now I stick again with 3200MHz on my ram. No BSOD since.

Why do we don't see AGESA improvement? Even the MSI B350 Tomahawk (a cheap product) offers 1.0.0.4c since july 2018
Maybe Asus want us to buy the CH7 ;-)

Dunno why your same profile has not worked. Again only thing I can think is it had not had fullest testing on previous UEFI. I can only state when I tested UEFI prior to 6301 (UEFI 0001), whatever profile I had on it, actually worked on 6301. I had 4.1GHz 3400MHz C15 1T on 4x8GB on UEFI 0001 and it worked the same on UEFI 6301.

Do go and read that some of the owners of boards which have AGESA 1.0.0.4 have had issues and some reverted back to past UEFI. The C7H has also been on same AGESA as C6H, only had a beta of 1.0.0.6 a week'ish ago.

As stated before I do not know why people have this thing that the latest AGESA is going provide a vast gain. All I can say is that comparing what Ryzen gen 1 and C6H was at launch, Ryzen gen 1/2 and C6H/C7H is vastly developed and I really can't see any big gains coming from firmware.

The C6H has not been gimped or left behind in development so far IMO. In fact I prefer my C6H to C7H, I have been using the C6H more than the C7H. Due to the ASUS T-Topology that C6H has, it handles 4 dimms better than the C7H does in my experience.

[Tiburan]

If you are using UEFI 6301 with ASUS WMI it does not fix fan PWM issues if you use applications which do not use the "communication" method. So you need to be using UEFI and SW supporting ASUS WMI.

Currently the applications I am aware of that use the new implementation are:-

- HWInfo v5.88 or later
- HWMonitor Beta: http://download.cpuid.com/betas/hwm_b17.zip
- SIV 5.32 or later
- CPU-Z Beta: http://download.cpuid.com/betas/cpuz_a0.zip
- AIDA64 v5.98.4800 or later

Anything else which accesses Super IO chip could cause you issues, AFAIK even ASUS utilities like Ai Suite, etc.

Thanks for the detailed feedback, I will be patient for now. I kinda like the Aisuite software and prefer using this for fan controls etc.

[gupsterg]

Thanks for the detailed feedback, I will be patient for now. I kinda like the Aisuite software and prefer using this for fan controls etc.

NP .

I can only assume ASUS will update the utilities soon. Hopefully by soon is not the same time scale as how long the ASUS WMI implementation has taken to come about.

I have been using now UEFI 6301 since release, for a lot of hours each day. No issues to report with HWINFO, CPU-Z, AIDA64 and ASUS Turbo V. Fans I use custom profile in UEFI, I use CPU_FAN, CHA_FAN1 and CHA_FAN3.