X370 Taichi - self bricked

Locked, this thread is going nowhere.

After reading your post, I can agree with a point or two made. Mainly "...context issues, not to mention cultural differences in this being a global forum and misunderstandings happen."

Absolute agreement there.

By the way, historically speaking, a forum allows all exchanges/challenges to be brought to the forum that a Moderator and the participants agree to. - Historically speaking. Today of course that would not allow foul language, ethnic slurs, gender slurs and the like. But would allow statements or views that may be viewed as criticism that is unfair or unjust. Again, just historically speaking.

I disagree that a moderator(for example in a school debate, college debate, political debate or otherwise) can have their 'trigger' pulled so as to allow themselves to 'sink' to an ugly level. I believe they should always 'rise above that'. Again, just my thoughts.

I also disagree with "...we are not Tech Support". Yes, Xaltar (and other Mods) you are, and more. Much more. You are just not the TSD(AsRock Tech Support Department).

I know you mentioned "... lets put this to bed and move on". I find that incredible as it is in opposition to what a forum is. A setting for continued issues, yes issues that arise again and again because it is dealing with...humans. The same issues arise yearly because each year we are still...humans. What complicates things in this forum is that the issues that a customer has can be belittled, dismissed or ignored by the TSD. So a customer choses the only other option they believe that they have... to make their voice heard in a forum. Do you have a better direction for a customer to have their issues heard? A complaints department? A name, email or address to write to? If so, I myself will jump on that today!






Edited by Kevin A - 16 May 2017 at 1:05am

I was going to wait but....

'You' guys... as in Moderators and Tech Support have to be 'bigger' than to 'stoop' to threats or even cyber-fist-fighting with forum members or customers.

I truly know it is hard. I've been there, but you have to (using a sports analogy) let your 'game-speak-for-itself'. Take the insults. Take the criticism(just like a sports team or individual athlete). Whether fair or unfair. Just or unjust. 'Rise above it all'... and let your response(the aforementioned 'game') speak for itself.

I actually feel massively disappointed in the 4 tech support tickets I have sent in. Speaking as a customer. 2 of them I received a 'dismissive' response. 1 was ignored. 1 was a 'back and forth' that each time (Pablo) basically was saying 'screw you...'. Nothing was resolved.

vpz may not be 'tactful' and 'polite' or he may just be 'upset' and not calming down before a post/reply.

Nonetheless, AsRock's BRAND name is being crafted with each interaction with the TSD(Tech Support Department), Forum interaction with Moderators and the product itself.

Just my thoughts. I didn't 'have' to share but, I thought I should.

Edited by Kevin A - 15 May 2017 at 11:53pm

vpz wrote: An update on my case. The board will self brick with BIOS 2.20 if: - You have SMT OFF - S3 States enabled 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.

vpz, I don't know what crawled up your shorts but I'll wake up tomorrow or sooner and decide if you get Banned or not for your continued unnecessary and unwelcome attitude.

So this may be your first / only / last warning.

parsec wrote: vpz wrote: Okay. 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: There are any ways to recover this board from a bios that won't post ???  Did you ever see a different POST code besides E4 while trying to diagnose it? The board won't POST without memory installed, just FYI. The only thing I don't think you tried is a different PSU. I know it's a lot of work swapping the PSU, and I'm not suggesting you buy one if you don't have another to try. Otherwise, it sounds like you have done everything possible to recover from whatever happened to your board. You seem to think it's a corrupted UEFI/BIOS, but a component failure on the board can easily cause a POST test to fail. If you cannot return that board to your retailer, you can start the RMA process here: http://www.asrock.com/support/index.asp?cat=RMA Asus had some self-bricking AM4 board problems too? I know MSI had at least one BIOS version that was known to do that. Your post I believe is the first one I've seen in the forum about an X370 Taichi board having this problem.