Asrock X370 Taichi error code 07

I updated my bios through the instant flash utility (I did not use Windows) with the new version 1.94A and it said that it completed successfully, hit enter to reboot.  It didn't freeze or crash (was still acting stable and responded when I hit enter by promptly rebooting), I was not overclocking, and everything was set to default out of the box settings except for setting up a RAID and I forced the CPU pump fan header to run at full speed so my pump would not be throttled. Now it keeps displaying error code 07 on the debug led. I have removed all but one RAM stick, removed all USB devices, reset the bios by a jumper and the button on the I/O shield, and I have removed the battery while having the PSU unplugged while doing all those. Is my motherboard bricked or is there possibly some way to fix it?

I would like to add that prior to this problem I'm experiencing, the motherboard was working perfectly out of the box.  I was able to install Windows and everything was stable.  I only updated to the beta 1.94A because of all the new features/fixes that people mentioned which piqued my curiosity and I never had any problems with beta bios on any of my previous motherboards ever before, so I felt confident in giving it a try.  The fact that it said it completed successfully and responded as though everything went smoothly puts me at a loss as to why it won't post anymore.  It's a pain having to tear down my system after just getting the motherboard two days ago.  If there's any possible way it can be fixed, I am open to suggestions.

Thanks.  I will try this out and report back.

ETA: The exact model of my ram is G.SKILL TridentZ F4-3866C18D-16GTZKW

It's not listed on the QVL but it didn't have any issues and using Windows worked just fine.  I believe they are SR Samsung ICs.


Edited by Asylum - 02 Apr 2017 at 2:18pm

Asylum wrote: I first tried 10 minutes, then tried for 4 hours.  Same error code 07.

Hmmm ........ that sux.

Let's try a simple BIOS clearing, no battery out, first with only one stick in A2

If that fails do the clear BIOS, no battery out, with the other stick in A2

I just went to the store and bought another set of RAM to see if I could get past the "07" code, but it still does the same thing.  I tried a single one in all slots and both sticks in both channels. No change.  I also tried formatting a usb stick to FAT32 and placing a bios file in the root directory and spamming F6 in both usb 3.0 and 2.0 and it didn't have any effect (though after searching the forum, I found this method was completely useless)... 

This process has been nothing but frustrating.  Bios updates on the AM4 platform will be almost mandatory if not highly recommended due to all the bug fixes and memory enhancements that are coming in the near future.  That fact alone should have made having a recovery feature also mandatory.  This means nobody can ever fully trust performing a bios update because in my experience even if it says it was successful it might not have been and if the bios update fails you're completely screwed.  All this is going to do for Asrock is make the people that buy an Asrock AM4 motherboard second guess even trying to update the bios due to the HUGE possibility that their hard earned money could just instantly be flushed down the toilet after the return policy and warranties run out...  Luckily I'm still within my return window, but I can only hope that if somebody finds this thread it will serve as a warning to them so that they can second guess purchasing one of these and they can avoid having to go through the same headache I have gone through the past 2 days losing sleep with trying to solve an unfixable issue that could have EASILY been prevented in the first place.  If the reason for not including that feature was to aim for a certain price range then it can be compared to the illogical equivalent of a car manufacturer not including windshield wipers. This almost seems like it's an insult gesture towards AMD  because if you check out the Z270 Taichi it actually does have a way to recover the bios.

Hey,