I tested in every configuration like in 1302 to get it stable, but random reboots even appear on default optimized settings.

I can copy the describtion from this thread:
https://rog.asus.com/forum/showthread.php?119540-ROG-CROSSHAIR-VIII-HERO(WI-FI)-BIOS-2103-High-Insta...


I had the same issue, I wondered why this bios was stated on reddit as beta while it was not marked as beta on the website some days later it was stated as stable bios on reddit too, from u/ASUSTechMKTJJ. (https://www.reddit.com/r/Amd/comment..._viii_hero_no/)

I installed the new bios via UEFI and set everything on default and started to type in my settings.
Suddenly the pc just reboot, while I´m in the bios....
So it won´t be any sudden windows issue.

Okay, I though maybe bad luck. Lets type in the settings.
Typed in all my stable settings from 1302 and started.
So far so good run a few cinebench test worked good. Played some RS6, everything fine. Chilling in the evening on twitch and discord.
Restart....
Next day I set everything on standard let run a karhu test over 10 hours while I was at the homeoffice.
No issues no restart.
After work turned of karhu, chillin on twitch...
restart.
turned on pc went to bios to check something...
restart in the bios again.
Flashed 1302 on USB2 did a bios flashback => Everything runs smooth no issues.
After the 2103 BIOS was announced on reddit as final bios I gave it another try. (https://www.reddit.com/r/Amd/comment...and_other_am4/)
This time with bios flashback to avoid any bad flashing issue.
moved to bios to confirm the optimised settings.
Restart...

Went back to 1302 everything is fine again.

This is the first time since 10 years ASUS Mainboards that I encountered such a messy bios
__________________________________________________________________________________________

It´s a german forum, but I´m pretty sure a lot ppl know IgorsLab.
He mentioned that it is an BETA BIOS.
https://www.igorslab.de/community/threads/agesa-combopi-v2-1-0-8-0.3020/

Another sad story, that ASUS again don´t mark it as BETA.

Guys if you wanna try, just make a backup of your old settings and save it on a USB Stick.

BIOS flashed to 2204 and for now, all good.

I haven't suffered any restarts from inside the BIOS nor Windows yet, I have been testing for around 3 hours now. Karhu RAMTEST passed 3200% without issues with my previous timings (CL14 with Samsung B-dies). Voltages seems alright, nothing weird. Mouse lag from within the BIOS still there, from 2010 BIOS ...

Performance is similar to what I already had with the 1302 BIOS. PBO behavior is still broken, it does not work, plain and simple.

I wont be assuming this BIOS is still OK for normal use until I don't test it for a few days with different workloads, I have been reading some reports of people (hi you) with issues yet (restarts)

I noticed that, most people with restarts use Hynix memories, could be there is a problem with Hynix compatibility since the 2010 BIOS?

I will be reporting more when I have the chance. Good luck

slice313 wrote:
BIOS flashed to 2204 and for now, all good.

I haven't suffered any restarts from inside the BIOS nor Windows yet, I have been testing for around 3 hours now. Karhu RAMTEST passed 3200% without issues with my previous timings (CL14 with Samsung B-dies). Voltages seems alright, nothing weird. Mouse lag from within the BIOS still there, from 2010 BIOS ...

Performance is similar to what I already had with the 1302 BIOS. PBO behavior is still broken, it does not work, plain and simple.

I wont be assuming this BIOS is still OK for normal use until I don't test it for a few days with different workloads, I have been reading some reports of people (hi you) with issues yet (restarts)

I noticed that, most people with restarts use Hynix memories, could be there is a problem with Hynix compatibility since the 2010 BIOS?

I will be reporting more when I have the chance. Good luck

Thank you for your feedback. At first view it looked also good. Karhu run well with my settings for over 8 hours too with 2103 but then randomly restart....really random...I´m using G.Skill 3600 CL16 B-Dies. Please let me know if you test it some more days. I also just realized the restart coz HWinfo was closed than I have checked the even manager in windows and have seen a critical restart.

My Stuff:
Crosshair VIII Hero Wifi
3950x cooled via noctua NH-D15
Corsair 750D case
Corsair AX850 PS
Gskill 3600 Cl 16's (16x4)
1TB Samsung 860 x2
2080ti
I have this thing set pretty mild: dcop setting enabled. FAns set to 100%. everything else default.
1302 ran without issue.
2103 ran without issue.
installed 2204 last night......and same. runs without issue 🙂

Maybe I got lucky, or just because I haven't done any type of OC aside from DCOP setting enabled, haven't had a problem yet, running rock solid.

I have the same issues as on 2103: https://rog.asus.com/forum/showthread.php?119540-ROG-CROSSHAIR-VIII-HERO(WI-FI)-BIOS-2103-High-Insta... Good news is that, the same workaround works.

tommy7600 wrote:
I have the same issues as on 2103: https://rog.asus.com/forum/showthread.php?119540-ROG-CROSSHAIR-VIII-HERO(WI-FI)-BIOS-2103-High-Insta... Good news is that, the same workaround works.

Can you explain to me your workaround and which specific settings you adjust? I read the whole thread, but couldn't figure it out sorry...

I have Crosshair VIII Wi-Fi and G.Skill Trident Z Neo F4-3600C14Q-32GTZNB. Interestingly, this kit isn't listed on Asus website as QVL, but it is listed as QVL on G.Skill website for the same motherboard. The QVL on the Asus website appears to be old dating back to March!

Getting a bunch of BSOD with and without DOCP. It is worse on 2204 than it was on 2103. Now that I've reverted back to 2010 I'm still having some issues which I swear i didn't have before...

New version 2206 is UP . i have Impact and that has 2103 and 2206 so i wonder if 2204 was some kind of beta for Hero version