AGESA 1.0.0.6

The UEFI on all AM4 boards is still under development, both by AMD and manufacturers. Rest assured, whatever issues AGESA 1.0.0.6 has will likely be ironed out, either by AMD or by manufacturers. We will either see a 1.0.0.7 or a vendor level fix. I don't have any details other than it is being worked on by ASRock and AMD both. It will, like all things, take time. Bare in mind however that AMD is not like intel, the AM4 platform will likely be compatible with several processor generations. This means that your board will serve you for quite some time to come 

I have always loved that about AMD too. Finally there is a competitive architecture from AMD again  

oile wrote: Regarding SPD, I was beginning to think about buying Thaiphoon to do the same you thought. Writing proper manual timings on a separate profile. The point is that I don't have an Intel platform to actually verify what the sticks are capable of to be sure the custom-xmp would work properly on the best case scenario, but most importantly, based on what I've seen in these betas, It would have been simply not worth the hassle.

You don't verify what they'll do on an Intel system. Why would you????????

It is painstakingly done on the system they are to run on. Verify on the Ryzen system you have.

It's slow arduous and tedius. With you becoming very VERY familiar with reaching for the Reset switch, and clearing the CMOS

I will be testing L2.34 on my Taichi once I have my system built. I will backup and upload it if anyone wants it. It will be a few days though, I am waiting on a few parts still.

Can someone tell me where I can report BIOS bugs? I have been testing the beta BIOS for the x370 Pro Gaming L2.36, and it still has the exact same RAM OC bug that the latest stable BIOS has L2.30.

It would be nice if I can report this now before Asrock finalizes the BIOS, because this bug makes memory overclocking a real pain. I almost RMA'd my board because I though it was broken until this bug was pointed out to me in an overclocking video somewhere. IIRC that guy was on a 1.xx version of the Taichi BIOS so this bug has been around for a while.

I'm also going to post the bug here so that people on the forum and googling around can find this and be aware of this issue. This bug is present on the latest stable BIOS and the latest beta BIOS. This bug effects the X370 Pro Gaming and the x370 Taichi IIRC.

When memory overclocking, if you choose any speed or setting that is unstable and will not pass post. You MUST clear CMOS to apply ANY memory settings or it will never pass post outside of the default memory speeds (in my case DDR4 2400). Even if you apply memory settings that you know for a fact are stable, and have passed post before. It will never pass post until you clear CMOS after failing post during the retries.

For example: You set 3600MHz as your memory speed, it doesn't pass post. After the retries it resets back to default. Go right into the BIOS when it boots up after the retries. You enable the XMP profile, you will still not pass post ever. Even if you have booted with the XMP profile before. The board just gets stuck in this loop until you clear CMOS or reset to default settings in the BIOS and reboot without changing anything.

If requested I can record a short video showing this, incase this doesn't make sense. It was a bit difficult for me to articulate this issue.

As you can imagine this makes memory overclocking a serious pain in the ass. As I found out last night.

Hopefully we can get this fixed soon.