Crosshair VI Hero: UEFI build update thread

[FoxTech]

Bios 6003 (installed 13.4.2018)

I needed to flash the file two times.
The CPU cooler wasn't recogignized. Q-Fan faild, Post screen error No CPU cooler found.
CPU cooler was running at 100%

After a reflash, its working nicely. No BSOD or anything so far.

[Syaoran]

Bios 6003 (installed 13.4.2018)

I needed to flash the file two times.
The CPU cooler wasn't recogignized. Q-Fan faild, Post screen error No CPU cooler found.
CPU cooler was running at 100%

After a reflash, its working nicely. No BSOD or anything so far.

That has always been something I would recommend with this board. For whatever reason, a single flash is not rarely reliable. This goes way back to the fan and pump failure issue and has been present on the board since the 1xxx series BIOS's. Load defaults, flash, boot to BIOS, load defaults, flash, and then you should be good to actually start setting things up normally.

[FoxTech]

Good to know.
Seems, I was lucky so far. This issue happens only once for me.
But will remember this the next time. Probably next wendsday^^ 6004? haha

[Syaoran]

Good to know.
Seems, I was lucky so far. This issue happens only once for me.
But will remember this the next time. Probably next wendsday^^ 6004? haha

It wouldn't surprise me to see another new one rushed out the door.

I loaded up 6003 and almost instantly after setting a basic OC, the incorrect CPU clock values are still incorrect! Is it really so hard to actually try fixing things?!? This honestly makes me wonder if all they are doing is pushing the same BIOS code with AGESA code updates and no actual fixes for anything else. We expect and deserve better, Raja!

[FoxTech]

I hope, they don't optimize for the new Ryzen2 or next generation only.
Sometimes it seems, they left us first Ryzen owners alone... as Beta Tester =(

New Bios often brings back old issues and/or don't bring solutions for other problems.
I'm not a programmer and I don't know how hard it is to optimize a Bios file.
But other brands can for some reason.
And tbo.. the CH6, a high end Ryzen board should run out of the box (mostly)

Well, lets see, what future will bring.

Yep, CPU clock still not correct. Fixed at 4,0 Ghz with turbo off. But I can live with this issue

[Syaoran]

I hope, they don't optimize for the new Ryzen2 or next generation only.
Sometimes it seems, they left us first Ryzen owners alone... as Beta Tester =(

New Bios often brings back old issues and/or don't bring solutions for other problems.
I'm not a programmer and I don't know how hard it is to optimize a Bios file.
But other brands can for some reason.
And tbo.. the CH6, a high end Ryzen board should run out of the box (mostly)

Well, lets see, what future will bring.

Yep, CPU clock still not correct. Fixed at 4,0 Ghz with turbo off. But I can live with this issue

I do think that will cause more issues for us original Ryzen and X370 owners in the end of it all. The more you try to cater to, the more potential problems there can be. It is frustrating to continue to face some of the same annoyances over and over with this board. Most people who buy a Ryzen 2 is not going to want to put that in an X370 motherboard. Asus really needs to get us a half decent and stable BIOS before focusing on anything else.

[looncraz]

It wouldn't surprise me to see another new one rushed out the door.

I loaded up 6003 and almost instantly after setting a basic OC, the incorrect CPU clock values are still incorrect! Is it really so hard to actually try fixing things?!? This honestly makes me wonder if all they are doing is pushing the same BIOS code with AGESA code updates and no actual fixes for anything else. We expect and deserve better, Raja!

Use ASUS ZenStates. Seriously, works flawlessly.

Also, are others having the same issue as you? If not, you should think that you might have a defective component.

[FoxTech]

I guess Syaoran menas the CPU Clocks shown in Windows or sometimes in HWMonitor.
Windows tells me up to 4,4 Ghz and HWMonitor up to nearly 4,2Ghz.
But thats impossible. Glockspeed set to 4,0 Ghz (multipl. 40,00, Bclk 100, Turbo off)

If I use P-State OC or regular over/basic OC Windows reports fals clocks. Not a big deal, if you know your Bios settings.
The bigger problem are the voltages when using LLC or simply flashing a new bios file.
I had it happen in an earlier Bios that my CPU got feed with nearly 1,55 Volt.
Instantly run bios and fixed voltage to 1,3625v But not all user are aware of this things.
We CH6 owner have to take an eye on things every time.

[Syaoran]

I guess Syaoran menas the CPU Clocks shown in Windows or sometimes in HWMonitor.
Windows tells me up to 4,4 Ghz and HWMonitor up to nearly 4,2Ghz.
But thats impossible. Glockspeed set to 4,0 Ghz (multipl. 40,00, Bclk 100, Turbo off)

If I use P-State OC or regular over/basic OC Windows reports fals clocks. Not a big deal, if you know your Bios settings.
The bigger problem are the voltages when using LLC or simply flashing a new bios file.
I had it happen in an earlier Bios that my CPU got feed with nearly 1,55 Volt.
Instantly run bios and fixed voltage to 1,3625v But not all user are aware of this things.
We CH6 owner have to take an eye on things every time.

What I mean is, the CPU speed shown in the BIOS. I have my CPU set to 3800 but the but the first screen of the BIOS shows 3400 for my 1700X regardless of what I set it to. This has been an issue from 300X forward and it goes away if I flash back to 170X and earlier. CPU-Z and AIDA64 report the correct values 6003. The BIOS not reporting the correct information though is concerning.

[BlackBishop]

3400 is base clock for 1700X.
For 1700 it will show as 3000 and 3600 for 1800X.
When you enter BIOS you can see your settings correctly in upper right corner.