x470 BIOS 8.01 [Beta]

It really depends. Some Beta versions simply add a niche feature or fix and never
leave Beta as whatever they add is either very niche or is set to be included in
the next major release anyway. In other cases I have seen ASRock include "beta"
versions of BIOSes for boards that other manufacturers would no longer be supporting.
I suspect they are still fully supporting the x470 range though so in all likelihood
we should see a new BIOS version as soon as they have a more major version update.
I have no information on when that will be however.

Hello, I also hope to leave Beta but ...

Xaltar wrote: In other cases I have seen ASRock include "beta" versions of BIOSes for boards that other manufacturers would no longer be supporting.

This is true, ASRock just published BIOS (also Beta) with the latest AGESA version for all its X399 series (2017 release) downloadable from support websites for each model.

Considering the frenetic market for CPUs/Motherboards IMO this translates into respect for the customer.

Another issue is the policy of AMD or Intel stopping microcode improvements for their 2-year-old chips, really unsustainable and disrespectful. At least we get security mitigations, otherwise it would be a crime.



Thanks T1125P for your OP and Xaltar answering here, an interesting topic to discuss in current times

Hello @T1125P

I'm using it 1.2.0.8 hence share good news bad news.

Bad news first, loading XMP from non QVL ram list will fail to POST, so we've got to key them in manually.
example cmk32gx4m2b3000c15=3000MT/s=1500Mhz,
the voltages does not load, does not update to required voltages,
i.e.
vddr_soc does not load to 1.1v,
cldo_vddp does not load to 1.0v,
VDDG_CCD & IOD does not load to 1.1v respective,
>>>> they all just remains at AUTO, versus some older bioses will show actual voltages to be applied next, and true enough reboot failed to even POST, because all the voltages written above remains for clean bios boot 2133MT/s, which I recall is around
vddr_soc 0.9v
cldo_vddp 0.7v
vddg_CCD & IOD 0.9v
all not enough to run XMP.

Then XMP's secondary timing was not loaded, i.e. tRAS, tRC, tRFC, tRFC2, tRFC4, tRRDS, tRRDL, tFAW, then POST also fails.....

in ASRock's defence, they ran out of space for auto update voltages and timing ranges to fit in agesa 1.2.0.8 hahahahaaha

bad news end.



Good news start: -

loadline Level 3 for CPU and SOC needed.

successfuly POST and run windows for the FIRST time in 6 years the hynix AFR 25nm process cmk32gx4m2b3000c15 @ 3466MT/s = 1733Mhz in 3800x in taichi_x370 using agessa 1.2.0.8. Minimum POST voltage is 1.48v simple 1usmus EASY memtest 6000MB pass multiple rounds, but game crash after 10 minutes....... pretty good start..... so next test 1.5v (to be reported in future).


More good news, the cmk32gx4m2b3000c15 can even POST and run windows (light load = simple browsing, file browsing using windows explorer, screen capture, etc simple stuff) @ 3533MT/s = 1766Mhz HOORAY !!! minimum post voltage is 1.56v, will try 1.6v later (to be reported).

timings started from a baseline copying Patriot's 32GB x 2 = 64GB, thanks to @POUL from overclock.net for sharing.
tCL 18
tRCD 22
tRP 22
tRAS 42
tRC 68
tRFC 991 (timing range not allowed, auto correct reduce to 990, I suspect whenever one of the timings cannot be read/fit will cause the entire secondaries timing not to load at all)
tRFC2 631
tRFC4 469
tRRDL 10
tRRDS 9
tFAW 40

then TARGETing timings from 1usmus dram calculator SAFE with A0/B0 with dual rank with 2 sticks, then slowly reduce timings a little at a time and one by one.

tomorrow will upload performance screen cap.

Edited by cx5 - 08 May 2023 at 11:42am

@cx5
Thanks for your info, and that screenshot. I see you went ahead and flashed the beta bios. So they ran out of space for the XMP profiles? LOL And you need to enter them yourself? Could be also the reason it's still in beta but, it works when you enter them manually which I see. That is good news then, being 1.2.0.8 is just for some security vulnerabilities that's probably not really needed for most home desktops I will hold off and wait until it leaves beta, if it does.