X370 Taichi BIOS 2.00 Problem

I updated from BIOS 1.6 (stable) to BIOS 2.0 (stable) using the Windows BIOS install as I did when I upgraded from 1.4 to 1.6 when I first purchased the board from MicroCenter. After the BIOS program prompted that all is good with the install, I rebooted and the computer is now constantly cycling on and off with Dr. Debug codes 55 and then 43 which are the last numbers I see before it starts cycling all over again. Taking the codes into account being it could be a memory issue per Dr. Debug, I used all 4 seperate DIMMs to attempt to get it to POST--no such luck. I cleared CMOS numerous times to see if I could get it to POST. It appears the ASRock Windows BIOS update version may have issues with my board or perhaps an item with my board. I have not peripherals or items plugged into the board. This issue became an issue immediately after restarting from flashing the drive in Windows. I did use the correct x64 program as I was in Windows 64bit. The memory I am using is F4-3200C16-8GT. I have a total of 4 DIMMS. Any ideas on how to overcome this issue without having to RMA this board?

p.s.
sorry forgot to mention
i used bios loader to flash to v2
i had no problems (this really is the only way to play the odds in your favour ,windows flashing is really risky, i dont think they should even give users the option myself)
always use the direct bios flasher in future its easier than windows in my view

datonyb wrote: ......windows flashing is really risky, i dont think they should even give users the option myself

No wiser words have been spoke concerning BIOS flashing.

Use Instant Flash, or for those old enough to remember DOS, use the DOS method.

But DO NOT use Windows to flash the BIOS. Way WAY too many background instructions running Windows to feel safe using ANY Windows Flashing Utility

wardog wrote: datonyb wrote: ......windows flashing is really risky, i dont think they should even give users the option myself No wiser words have been spoke concerning BIOS flashing. Use Instant Flash, or for those old enough to remember DOS, use the DOS method. But DO NOT use Windows to flash the BIOS. Way WAY too many background instructions running Windows to feel safe using ANY Windows Flashing Utility

  < ="chrome-extension://hhojmcideegachlhfgfdhailpfhgknjm/web_accessible_resources/index.js">

Edited by GenesisDoes - 13 Apr 2017 at 1:20am

Hi Sam--The issue for me is not the same as your issue unfortunately. My issue was that the Windows x64 BIOS Flash utility this time did not work. I tried all the tricks and a few on top of that. While I had no other processes going on in the background it was just bad luck that it made the board go into an infinite loop and no option for bypassing. As other users have noted, do not use the Windows BIOS flash utility unless it is a last resort. My error as I was very tired and lazy that day that cost me more in time and some money than I anticipated. Remember, there are no alternatives to BIOS recovery for this board. It is soldered onto the board so you can't just purchase a new one, not sure why this is the course of action they took with it being bleeding edge technology, but I am sure it was for expediency and that the Rev V2 may have a BIOS recovery option. Overall, if you cannot go through your retailer, RMA via ASRock and they will take care of you and the new board they will send to you will carry the same warranty. One more thing, if you RMA via ASRock, cannabalise that board (i.e. BIOS battery, backplate, etc.) as they will ONLY send you the motherboard.

Edited by taichidude - 14 Apr 2017 at 12:42am