I agree that logically it stands to reason that updating the BIOS is likely the culprit here, but taking your frustrations out on a Moderator who is only trying to help will not do you or anyone any favors. It won't motivate ANYONE else to try and help you, and it won't magically help a dead board come back to life.

I've only been building computers for about six years now, but in all that time, I have never once updated a BIOS that did not warn me beforehand about the dangers of the update process. You take the life of the board in your hands when you perform an update. This is not a Ryzen thing, or an ASRock thing. EVERY manufacturer warns of the dangers, and explicitly directs people away from updating if the system is functional with the current BIOS.

Oftentimes, the sequence of updates can affect the success of any one update. There have been times where I was instructed to update all BIOS updates in their chronological order, that is, not to jump to the latest version.

The OP, in this case, CAME from one beta to another. It was only after he bricked the board on the second beta update that he realized his folly. I mean no offense Mextech, but updating to the first beta you installed was irresponsible enough. Perhaps the successful installation of 1.55 filled you with a false sense of confidence, and that's why you didn't feel trepidation when you nosedived into 1.93D. It's a little unclear why you didn't go from the 1.55 beta to the stable 1.60, but it's a little late for that now.

I wish you the best of luck with the RMA process, I hope you get a working board back soon, and find a compassionate person in your life to let you use their computer in the meantime.

I was tempted myself to jump on the beta bandwagon, but too many people count on me for the work that I do. Embarrassment would have been the least of my worries had I bricked my board. A foolish mistake like that may have cost me some of my clients.

Let this be a lesson to everyone chasing higher memory speeds. Either fork out the cash for RAM that other users have VERIFIED works with a STABLE BIOS, or be patient and wait for ASRock to make some magic happen.

Yes, agree, this time wardog didnt help :) In this case corsair is irrelevant - it dont change fact that it worked before, and dont work with 4 different sticks. Fact is that with stock bios and 1.55 all worked fine (memory related) but in 1.93D it dont post. 

Beigtapel3 - thanks for feedback, so im not only one that so lucky.... Yes really ironically i hoped that it start to work better.... but yes its look like 1.93D dont support any RAM @ all - today was in service and tested few ram sticks, nothing helps. Now my work is unfinished and im in a lot of trouble :)

SO people who reading this, dont update bios if u have working board - update only than if u have a lot of free time and u will have replacement. :(

How do you think he managed to launch the system before and update BIOS with a memory that's not compatible? The system worked fine before but after 1.93D update it doesn't (ironically after a BIOS which improves DRAM compatibility).

I found this thread today, right after one of our customers brought a bricked Fatal1ty X370 Professional Gaming board. It doesn't POST with any of 5 different brand and capacity DDR4 memory sticks right after 1.93D update and gives the same 4F error. There is only one explanation - 1.93D update bricks the motherboard. Unfortunately there's no solution apart from creating a RMA request.

Clear CMOS doesn't do anything. 4F error code all the time...