X370 Taichi - self bricked - ASRock Forums

Author

Message

Topic Search

Topic Options

MisterJ

Senior Member

Joined: 19 Apr 2017
Status: Offline
Points: 1097

Posted: 10 May 2017 at 8:46am

Thanks, vpz. Enjoy, John.

vpz

Newbie

Joined: 10 May 2017
Status: Offline
Points: 17

Posted: 10 May 2017 at 8:35am

https://ami.com/ami_downloads/Aptio_V_Status_Codes.pdf

MisterJ

Senior Member

Joined: 19 Apr 2017
Status: Offline
Points: 1097

Posted: 10 May 2017 at 8:34am

vpz, please post a link to the Dr. Debug codes you found. Thanks, John.

vpz

Newbie

Joined: 10 May 2017
Status: Offline
Points: 17

Posted: 10 May 2017 at 8:21am

I have found some on AMI bios regarding that code and it is "S3 status resume" related.

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.

Edited by vpz - 10 May 2017 at 9:53am

MisterJ

Senior Member

Joined: 19 Apr 2017
Status: Offline
Points: 1097

Posted: 10 May 2017 at 7:55am

Sorry, vpz, I do not have an answer for your question - obviously suspect a HW failure. I searched for some information on E4 Dr. Debug code and only found "E4 - Reserved for future AMI progress codes". Please e-mail ASRock Support with your information and ask them what the code means and where we all can find definitions of all the Dr. Debug codes.
Thanks and enjoy, John.

vpz

Newbie

Joined: 10 May 2017
Status: Offline
Points: 17

Posted: 10 May 2017 at 7:24am

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 ???

Edited by vpz - 10 May 2017 at 7:48am

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
MisterJ Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 19 Apr 2017 Status: Offline Points: 1097	Posted: 10 May 2017 at 8:46am
	Thanks, vpz. Enjoy, John.

vpz Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 10 May 2017 Status: Offline Points: 17	Posted: 10 May 2017 at 8:35am
	https://ami.com/ami_downloads/Aptio_V_Status_Codes.pdf

MisterJ Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 19 Apr 2017 Status: Offline Points: 1097	Posted: 10 May 2017 at 8:34am
	vpz, please post a link to the Dr. Debug codes you found. Thanks, John.

vpz Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 10 May 2017 Status: Offline Points: 17	Posted: 10 May 2017 at 8:21am
	I have found some on AMI bios regarding that code and it is "S3 status resume" related. 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. Edited by vpz - 10 May 2017 at 9:53am

MisterJ Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 19 Apr 2017 Status: Offline Points: 1097	Posted: 10 May 2017 at 7:55am
	Sorry, vpz, I do not have an answer for your question - obviously suspect a HW failure. I searched for some information on E4 Dr. Debug code and only found "E4 - Reserved for future AMI progress codes". Please e-mail ASRock Support with your information and ask them what the code means and where we all can find definitions of all the Dr. Debug codes. Thanks and enjoy, John.

vpz Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 10 May 2017 Status: Offline Points: 17	Posted: 10 May 2017 at 7:24am
	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 ??? Edited by vpz - 10 May 2017 at 7:48am