Asrock X370 Taichi error code 07

kingsims wrote: Interestingly my issue started when i moved the memory from Banks A1 A2 to A1 B1 for dual channel. Failed to Post moving it back made no difference.

Ummm........ A2 and B2 are for Dual Channel using two sticks !

The User Manual that was included with purchase, pg23

and the below link too next to Memory

http://www.asrock.com/mb/AMD/X370%20Taichi/#Specification



Too, the BIOS chip is not socketed, thus it is not User exchangeable/replaceable.

Disappointment and frustration is perfectly understandable. All Wardog meant was that in this particular situation (regarding Ryzen) these issues are beyond any manufacturer's control. Keeping cool and calm is the only way to work through issues 

wardog wrote: Don't be a guinea pig and chase that magical BIOS just yet. Wait, be patient, and read of others headaches for them leading the way. Follow cautiously, but don't lead. And if you've read many of my posts, I'm not a follower. Hardly. NOT!

I understand you here, but the fact still remains that early adopters of this platform will have to update bios in order to fix bugs and improve performance. As you know AMD has been steadily releasing microcode updates and the only way to receive them is through a bios update.  Are we just suppose to wait until Asrock makes a final bios version and just never update? By the time they include all of the fixes, Ryzen 2 will be here and possibly a whole new chipset and/or motherboard.

wardog wrote: It's not the processor nor motherboard that you and Asylum suffer, it's all memory related.

You're right that it's a memory support issue, but that doesn't excuse the fact that if something goes wrong the only solution is to hope it fails before the 30 day return is up or be forced to ship your motherboard back to Asrock for repairs while you no longer have a computer to use for weeks while you wait for a replacement...  In this day and age, having a computer is kind of important. If the problem I was having was due to memory it doesn't explain how out of the box it worked just fine but magically stopped with a newer bios considering the main reasoning behind releasing newer versions is to improve support for RAM not take it away... kinda ironic, don't you think? lol

wardog wrote: C'mon and let's keep our wits tempered and not let anger cause us to do something ridiculous like switch MB's when you'll likely be facing the exact same issue.

I'm not exactly "angry", I'm just disappointed... out of all the motherboards I was looking at this one was the most attractive to me so I took the plunge and bought it despite it not having a recovery feature because my experience with other motherboards that didn't have recovery never had an issue like this. Yes, there might be a possibility that I'd run in to the same problem with another brand, but if I did go with another brand I would've at least had way to recover instead of just being screwed with Asrock's solution.  I would have just "flipped a switch" and off I go or via Asus' method with a usb stick.  This also ignores the fact all the other manufacturers had NO PROBLEMS implementing this kind of solution on their AM4 boards yet Asrock only wanted to include that option on their Intel boards. It can't be due to a different bios implementation vs. the Intel motherboards.  If that was the case, explain all the other brands being able to include a backup feature and yet Asrock mysteriously deciding against it ONLY on their AM4 boards... kinda hard to overlook that fact, sorry.  I'm not saying that I would not buy from Asrock again in the future, but it's hard to recommend any of their current AM4 motherboards due to this glaring issue.  Money doesn't grow on trees.

Edited by Asylum - 03 Apr 2017 at 4:03pm

Got home with 2 different model of dimm's.

Why do you think removing CPU is needed? :) Tried it, but after removing the CPU, i'm not putting it back until new/replaced mobo.