ASRock.com Homepage
Forum Home Forum Home > Technical Support > AMD Motherboards
  New Posts New Posts RSS Feed - X370 Taichi, Goes Blank; Code '00'
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

X370 Taichi, Goes Blank; Code '00'

 Post Reply Post Reply Page  <1234 5>
Author
Message Reverse Sort Order
Cantine View Drop Down
Newbie
Newbie


Joined: 08 Oct 2017
Status: Offline
Points: 16
Post Options Post Options   Thanks (0) Thanks(0)   Quote Cantine Quote  Post ReplyReply Direct Link To This Post Posted: 13 Oct 2017 at 12:25am
How did you remove the oil? Contact cleaner?
Back to Top
wardog View Drop Down
Moderator Group
Moderator Group


Joined: 15 Jul 2015
Status: Offline
Points: 6447
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post Posted: 06 Oct 2017 at 12:05pm
I will contact Tech Support and have this looked into.

Thank You for returning and notifying us.
Back to Top
Ivan_83 View Drop Down
Newbie
Newbie
Avatar

Joined: 22 May 2017
Status: Offline
Points: 85
Post Options Post Options   Thanks (0) Thanks(0)   Quote Ivan_83 Quote  Post ReplyReply Direct Link To This Post Posted: 06 Oct 2017 at 8:19am
Probably I found cause of issue: it is some kind of oil from thermal pad, it leak on mobo over chipset: http://forum.ixbt.com/post.cgi?id=attach:9:68823:5110:1.jpg

I remove it and looks like mobo works fine now.
Same crap probably with Fatal1ty X370 Gaming K4, X370 Killer SLI, Fatal1ty X370 Gaming X and other mobo with near design.




EDITED TO DISPLAY PICTURE. HOT-LINKING ISSUE


Edited by wardog - 06 Oct 2017 at 12:03pm
Back to Top
Ivan_83 View Drop Down
Newbie
Newbie
Avatar

Joined: 22 May 2017
Status: Offline
Points: 85
Post Options Post Options   Thanks (0) Thanks(0)   Quote Ivan_83 Quote  Post ReplyReply Direct Link To This Post Posted: 01 Oct 2017 at 7:54pm
RMA mobo.
Back to Top
fergazer View Drop Down
Newbie
Newbie


Joined: 26 Sep 2017
Status: Offline
Points: 1
Post Options Post Options   Thanks (0) Thanks(0)   Quote fergazer Quote  Post ReplyReply Direct Link To This Post Posted: 26 Sep 2017 at 4:45am
I have the same problem with Fatal1ty X370 Professional Gaming since day one. Running Linux and under even 0 load, just idling, it will end up locked with 00 flashing, randomly, but at least once a day.

RAM & CPU stock volts & freq. 

Ran Memtest86 for 36 hours worked fine.

RMA'd the 1800X CPU so far, and it did not help.

Kinda lost as to what to test next.
Back to Top
Snow View Drop Down
Newbie
Newbie


Joined: 12 Sep 2017
Status: Offline
Points: 10
Post Options Post Options   Thanks (0) Thanks(0)   Quote Snow Quote  Post ReplyReply Direct Link To This Post Posted: 12 Sep 2017 at 7:57am
I get this too, but with windows 10, x370 taichi board.


Edited by Snow - 12 Sep 2017 at 7:58am
Back to Top
Ivan_83 View Drop Down
Newbie
Newbie
Avatar

Joined: 22 May 2017
Status: Offline
Points: 85
Post Options Post Options   Thanks (0) Thanks(0)   Quote Ivan_83 Quote  Post ReplyReply Direct Link To This Post Posted: 12 Sep 2017 at 7:40am
Well.
I take Bristol Ridge 9700 and got same issue on taichi.

I take all my hardware, except taichi and use AB350M Pro4 or Fatal1ty X370 Gaming X and system runs OK without any issues.
This is not software BUG, because I do not change any settings in my FreeBSD after mobo changed.
Back to Top
CraazyCanuck View Drop Down
Newbie
Newbie
Avatar

Joined: 30 May 2017
Location: Canada
Status: Offline
Points: 5
Post Options Post Options   Thanks (0) Thanks(0)   Quote CraazyCanuck Quote  Post ReplyReply Direct Link To This Post Posted: 30 May 2017 at 2:00am
I too have this issue. It is while running prime95. I've run prime stable for 1 hour plus at 3.6 with no issues. It's only during the search for stability at 3.7 that thus far it has occurred. But Ivan is not overclocking so something else? Screen goes back then flashing 00. Power to the board still occurring with fans running etc. Soft boot takes care of the problem.
I've rune Cinebench and Firestrike with no issues. And other then that just some Planetside 2, that brought up an audio issue even after reinstalling the realtek driver and disabling the Nvidia driver. Choppy playback in game while using headset.
The only other issue I've encountered thus far is F62 when I try to use the XMP file. It requires a cmos reset.
 
Running latest bios.
Windows 10
r5 1600
Fatality X370 K4
16GB Vengeance LPX running at 2133
Patriot Hellfire 480GB
 
All drivers were installed individually off the site as the all in one did not work.
Back to Top
Ivan_83 View Drop Down
Newbie
Newbie
Avatar

Joined: 22 May 2017
Status: Offline
Points: 85
Post Options Post Options   Thanks (0) Thanks(0)   Quote Ivan_83 Quote  Post ReplyReply Direct Link To This Post Posted: 25 May 2017 at 9:11pm
IHMO, Dr.Debug it is integrated to MOBO LPC-debug port decoder. (google: PCI-E PCI+LPC Port Diagnostic Test Debug Post card)
BIOS on some control points of code execution write to some register num-code of step where it now, so if there are some error happen then we can know on what step we got error.

If you really want to know what codes mean then you need get documentation from ami/award to get base codes and from asrock to know about vendor specific codes.


Edited by Ivan_83 - 25 May 2017 at 9:12pm
Back to Top
Lisanderus View Drop Down
Newbie
Newbie
Avatar

Joined: 30 Apr 2017
Status: Offline
Points: 10
Post Options Post Options   Thanks (0) Thanks(0)   Quote Lisanderus Quote  Post ReplyReply Direct Link To This Post Posted: 25 May 2017 at 8:06pm
I also get an annoying code 00 - when tested with a prime95. At first I was pretty scared, because in the description it says: Please check if the CPU is installed correctly.
Later came to the conclusion that it just signals instability of overclocking. The computer restarts and glows 00, it is necessary to restart. So... what this code 00 really mean?

Back to Top
 Post Reply Post Reply Page  <1234 5>
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.173 seconds.