With this Ryzen build I opted for AsRock instead of asus, that's the first time in a looong time I switch mb brands. 

Had the board running bios 2.20, so far so good, I was really enjying my system stability and memory at 3000MHz. 

Today I went to start my computer, connected the psu to the wall, hit the power button. The q-code reader cycled normally to q-code 99 but then the board self restarted. Okay, not the first time this board has pulled that. It went trough some q-codes again but then got stuck at q-code E4, and it could never get past it again.

So far I have tried:

- clear CMOS - No go

- clear CMOS, removing all ram sticks - No go

- clear CMOS, getting another brand of ram at slot A2 - No go

- Tried to find something that could help me in the manual - No go

- clear CMOS, remove battery, disconnecting EVERYTHING, GPu, PSU, RAM CPU, Pswitches, getting the board naked of any other components the same as it came to me and let it sitting with clear CMOS jumper in the clear position - No go

- Gettinghaving a USB stick fat 32 formatted with the bios file inside and connected to the boards USB port - No go

Then I tried to find on the internet on how to recover a bricked bios on this $ 200 AsRock made board...

My question is really simple:

S3 Resume Progress Codes - 0xE4-0xE7 Reserved for future AMI progress codes.

So, in my case had SMT disabled, I wonder how tight my problem is related to the CROSSHAIR HERO self bricking problems that asus had corrected more than a month a go. The thing is that Asus motherboard can recover from a bricked bios, this asrock board seems to have no bios recovery features. 

If you ask me it is a shame, specially after you see AsRock saying AMD didn't gave them time to get stuff done.  But then AsRock is not making it any easier by not having a bios recovery feature on a $ 200 board with self bricking issues.

Sorry, I'll just return this motherboard, get me an ASUS and never look back again.

Yes, because you came here saying hey, don't do this and don't do that but then the first thing the link you pointed is telling me to:

[/QUOTE]

Yes, I have tried a different PSU, Ram, GPU. Now the only thing I am missing of replacing is the CPU but still, it is not like I was doing dumb stuff, I have been here since the Slot A Athlons and you won't catch me trying to prove that latency > Frequency on Ryzen and DDR4 

Really a shame, I was enjoying the board's virtues, the only thing missing is the dual bios or the likes of asus flashback. The AMI Aptio V allows for that kind of recovery with a corrupted bios, no dual bios needed, no bios post required, asus provides that by the name of flashback. You would just get the bios inside a USB stick, press a button for a few seconds and voilá, rom is good to go again.

Well, I have ordered another motherboard. Let it be.

Yes, I had memory on board when I tried to boot again, also the PSU was connected too...Oh well, crasheless bios feature is within the specs of this mobo but then;

I tried to find info for the Crashless feature on manual- No go

Asked for directions here - No go

Looked at the web and there is nothing but the copy and paste crap stating that you must have the USB stick connected to a USB 2.0 port. Figures...-No go

If you click the DOS bios update info, you can clearly see that hte article is dating back to the windows millenium era... LOLED

http://www.asrock.com/support/BIOSIG.asp?cat=DOS8

Do not get these mixed or you will need to deal with their REALLY BAD CUSTOMER SUPPORT, or here, dealing with the likes of wardog.

Please bare in mind guys that we mods are not paid for our efforts here, we are not Tech Support. We give of our time and knowledge freely in order to help any and all who come here with issues. Now when someone shows up here angry because they have an issue things can get heated even at the best of times. Add to that context issues, not to mention cultural differences in this being a global forum and misunderstandings happen. 

Now I am not making excuses for or defending anyone here, simply providing some context. These things happen and for the record, Wardog bends over backwards to help people around here often spending an entire day trying to help a single user. We all have a trigger and when 2 people manage to hit that on the head things can get ugly. Arguments happen and in this instance it should have gone to PM long before names were called out and insults thrown. If any of you feel a moderator or any user for that matter is being offensive please take it to personal message. Ask them what they mean and give them a chance to explain themselves. More often than not these things can be resolved peacefully and frequently are rooted in misunderstanding. If a user persists in being rude or otherwise violates the code of conduct then please report it to one of the moderators (yes, even if it is one of us at fault). We take the atmosphere of these forums very seriously and strive to keep things helpful and friendly as many of you have already seen. 

So for the sake of the forums and our amazing community here, please, lets put this to bed and move on. We are here to help each other out, share experiences and enjoy the pleasant atmosphere this forum usually demonstrates. 

While describing the issues I have been trough and asking on how to use the recovery function that is specified within the boards features this is the e-mail I have received from AsRock North American support.

The X370 Taichi is a great board hardware wise, I was genuinely enjoying it, I was advocating in favour of the Taichi over other boards at it's price range and above that. 

But then the bios has many problems and AsRock support is just bellow the CRAP line.

While ASUS support is not perfect you can count on ASUS rep/engineers spread all around the web finding problems and helping users with simple & advanced questions, that may be undocumented or not.

The CVIH is a single bios board, in the self bricking episode with the CVIH had you had asus people working with users to research and find a solution. They provided customers with directions, a new bios and solved the problem.

SNIP wrote: Edited for inappropriate conduct -Xaltar

After the issues I had with Taichi@asrock support I don't see myself buying a AsRock product again.

I am sorry that you did not receive the tech support you were hoping for Kevin A. If you like, please make a new thread regarding your issue and we can try to assist you further.