New Bios (7.06) bricked with XMP on, Broke Window

Latest Intel spec 0x129 microcode BIOS update now live.

https://www.asrock.com/support/index.asp?cat=BIOS

I still had BSOD, but dialing back to my previous stable numbers fixed it. Also, latest Win11 update killed the ASROCK RGB App, so hopefully they are working on that. Ran similar numbers to previous, best so far, Cinebench numbers. Also I added a -2 core speed to the AVX2 coding, hoping it will help with some Blender render crashes I am having (I can get 10-15 frames at a time before it crashes, CPUs hitting 100 C at around time of crashes). I might just implement at hard 99 C cap on thermals. Microcode might be actively killing it at 100 C.

Yeah, 30kplus seems more inline with what is to be expected. I'm guessing you have appropriate cooling and just need to find the right tweaks to get up there again. The TVB thing starts kicking in pretty soon in my opinion, reducing turbo once the temp reaches 70 degC, all too easy to get on these cpu's. Having said that, of course this limit is there for stability and durability reasons, so maybe just go with it despite a minor performance reduction you're probably only going to notice in a benchmark anyway.

just rerun cb23 to be sure and also get a sc score, to compare:
https://imgur.com/a/hGnjFJF

OK, installed new BIOS (9.1). Still can't do default CPU multipliers. Still only stable at 56 and 44. New BIOS wanted to volt to 400, so I also put it back at 307. Basically back to what I had on the old BIOS, BUT my Cinebench did increase back up a bit, to 28596 MC, and 2034 SC From 20522 MC. Much more respectable numbers, but still down from my original numbers on this CPU. At this point, I will take the 5.5x performance increase and just pray for years of stability.

That's exactly how I see it. But the motherboard manufacturers could have given the customers "security" by offering TURBO, OC, Extrem... any other settings as a base with an Intel, AMD "stupid sure" setting, which I don't think has been adjusted exactly to this day into the BIOS. The same is true for memory, with AsRock Optimized and other timings, in addition to the XMP profile, which also approach the timings guaranteed by the memory manufacturer by 1-2 points if this option is turned on. If you don't like rummaging through the BIOS, either because you don't understand it, or because you think that when you build a machine, all the components will be coordinated and run on their factory settings and not on settings "optimized" by the motherboard manufacturer, this is unpleasant. Because you don't know where to turn, you can look for the fault..... :(
My problem seems to be temporarily solved, the freezes stopped when I replaced the memory pair that generated the Fantom XMP profile mentioned above with the same memory pair taken from the second PC, but which did not produce an error. I am now running the rounds with the dealer, who will admit the memory error after testing it. And this is also produced by the memory in His test machine. In vain, I sent him a video of the error phenomenon with the bad memories, and then of the flawlessly working machine I installed. If the returned memory in His PC
if it doesn't produce the error, then I have a couple of expensive unusable memories in my possession, which can only be solved by the manufacturer's RMA, or not at all...