Saya Barak sounds for mem that your 6000mhz setting isn't stable.
so the ram calculate wrong values and crash the system.
check with karhu the system stability with 6000mhz. i'm sure thats not a bug of f20a, i believe that the clock is to high or your latency to less.

the performance of f15d is still the same like with f15c (i imported the previous pbo setting from f15c) (b550 aorus pro)
i see no changes. if somebody found something, please let us know.

nothing f15c runs without any issues. i try flck 2000 for the first time and it also works. only my ram setting was not finalized for a 24/7 workload.
nobody has to wait, that gigabyte will delete the letter in the name and make a release of f15c.

i look for some bios updates for...

Where did you set the values. I try it on the main page (above the CPU and ram setting)
I set 1025mv and zentiming show me my default value of 0.9976v

in the pbo menu vddg ccd and vddp works. zentiming show me 1024mv by a set value of 1025mv. but the value for vddp iod ist stil 997.6...

so gigabyte will skip 1.2.0.6c?

attention: if you want to use the new ryzenmaster automatic detection tool to determine the pbo curve optimizer potential of your cpu.
please verify the values of ryzenmaster with corecycler. https://github.com/sp00n/corecycler
for a bulletproof system, use the setting "heavy"...

i have asked for a f15b beta for my board and called the post of the_real_skar as source. i have no problem with vddg but with cold boot since the new agesa

additional: i get a quick response, there is no new bios available.

msi release 2 days ago a agesa 1.2.6c
https://de.msi.com/Motherboard/B550M...port#down-bios

good to know that i'am not the only one with a cold boot issue. i'm waiting for a new bios. amd anounce agesa 1.2.0.7 for ryzen 5000 on b350. so maybe it will come in the near future.

esupport of gigabyte doesn't intresst in my feedback to f15a (agesa 1.2.0.6b). since i'm back to f14c every thing runs perfect.
did anybody known the vulnerabilities of agesa 1.2.03 which will fix in agesa 1.2.05 and higher?