X370 Taichi, Goes Blank; Code '00'

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   OK, first off, this IS NOT my first PC build and I've never had a problem like this before.  I know you gotta ask questions to try and narrow the problem, but some of those felt downright insulting.
I realize that updating bios is best done DOS, when I said primitive, I meant the bios not having a bios update tool installed in it already (which my version doesn't) and having to make your own boot drive.  My last few motherboards I've used over years had that, why not this one?  

Like I said in my original post, I've already wiped Windows and can't do a new install because everytime I try to reinstall Windows, I boot from the Windows USB drive, it starts to unpack the Windows install files, then goes blank and Dr.D flashes the '00'.  And I also said, I tried the DOS version and I can't get it to work either, though admittedly I've never had to update my bios this way before.  I made a bootable USB using rufus, extracted the the 1 .exe file in there to the drive and then booted from the USB.  It runs through a bit of stuff then gives me the C:\ prompt.  I type in the name of the update file.exe, but comes back invalid command.  I rarely use DOS, forget all the commands/intricacies, so maybe I'm not doing it right?  Better step by step instructions are needed for that!    

Yes, I've been able to keep the bios/settings open indefinitely.  I did that and went to the HW monitor section to watch the temp on the CPU for awhile because I thought it might be the cooler not working and the CPU overheating, but no, never got above 40C.  And even when I wiped the drive, that took 4 hours using Killdisk, that was booted from DOS.  

When I installed Windows 10 Friday night, everything was working fine.  Installed all the hardware drivers from the ones here on ASRock's site.  Continued to install some other programs, rebooted numerous times, never had a problem.  Saturday morning, tried to update the bios, no update happened, booted back into Windows.  After a few minutes (didn't even have a chance to update/install anything) the problem occurred.  Seems like too much of a coincidence to be anything else.  Then you mention Windows 10 updates...I don't know exactly what they may have updated, but I'll turn that off for next time for sure.  Where do you go in the setting to disable updates?  (Still new to 10)

Really I'm thinking of just sending both the CPU and MB back to Newegg just to be sure; get a replacement CPU then get a different MB from another brand.  I mean, if I were to get another one of these, who's to say the same thing wouldn't happen again when I tried to update the bios on that one!? 

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Hectic Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 12 Mar 2017 Status: Offline Points: 5	Post Options Post Reply Quote Hectic Report Post Thanks(0) Quote Reply Posted: 13 Mar 2017 at 12:39am
	OK, first off, this IS NOT my first PC build and I've never had a problem like this before. I know you gotta ask questions to try and narrow the problem, but some of those felt downright insulting. I realize that updating bios is best done DOS, when I said primitive, I meant the bios not having a bios update tool installed in it already (which my version doesn't) and having to make your own boot drive. My last few motherboards I've used over years had that, why not this one? Like I said in my original post, I've already wiped Windows and can't do a new install because everytime I try to reinstall Windows, I boot from the Windows USB drive, it starts to unpack the Windows install files, then goes blank and Dr.D flashes the '00'. And I also said, I tried the DOS version and I can't get it to work either, though admittedly I've never had to update my bios this way before. I made a bootable USB using rufus, extracted the the 1 .exe file in there to the drive and then booted from the USB. It runs through a bit of stuff then gives me the C:\ prompt. I type in the name of the update file.exe, but comes back invalid command. I rarely use DOS, forget all the commands/intricacies, so maybe I'm not doing it right? Better step by step instructions are needed for that! Yes, I've been able to keep the bios/settings open indefinitely. I did that and went to the HW monitor section to watch the temp on the CPU for awhile because I thought it might be the cooler not working and the CPU overheating, but no, never got above 40C. And even when I wiped the drive, that took 4 hours using Killdisk, that was booted from DOS. When I installed Windows 10 Friday night, everything was working fine. Installed all the hardware drivers from the ones here on ASRock's site. Continued to install some other programs, rebooted numerous times, never had a problem. Saturday morning, tried to update the bios, no update happened, booted back into Windows. After a few minutes (didn't even have a chance to update/install anything) the problem occurred. Seems like too much of a coincidence to be anything else. Then you mention Windows 10 updates...I don't know exactly what they may have updated, but I'll turn that off for next time for sure. Where do you go in the setting to disable updates? (Still new to 10) Really I'm thinking of just sending both the CPU and MB back to Newegg just to be sure; get a replacement CPU then get a different MB from another brand. I mean, if I were to get another one of these, who's to say the same thing wouldn't happen again when I tried to update the bios on that one!?

parsec Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 04 May 2015 Location: USA Status: Offline Points: 4996	Post Options Post Reply Quote parsec Report Post Thanks(0) Quote Reply Posted: 12 Mar 2017 at 1:19pm
	A UEFI/BIOS update is really a firmware update of a mother board. Any firmware update has some risk associated with it. Firmware is about the lowest level computer code/program that is used, and is not at the level of installing a Windows program, for example. That code is being written to the UEFI/BIOS chip itself, while all other software we use is written to a storage drive. We are also updating the code that is actually used by the UEFI/BIOS chip itself, replacing it with a new copy. Nothing else we install on a PC is similar to this. Also Ryzen systems are new, and as we are beginning to learn, the release date of the Ryzen processors was very aggressive, relative to the time that mother board manufactures had time to prepare their products for the market. For whatever reason, history has taught us that the Windows program UEFI/BIOS update method is the one that has the most failures. Did you remember to right click on the update program, and select Run as administrator? All I can tell you at this point is to try the DOS method again, or try the Windows method again, and be sure to run as administrator, with no other programs running. I would also try running the Windows update method from the C: drive. Sorry to ask, but all the UEFI/BIOS update files are .zip files that must be extracted before use, I assume you did that. I'm hoping your board gets the Instant Flash update files soon, as that method is the most reliable and is being added to your board's UEFI. I must also say that if the problem with the screen going blank did not immediately happen when Windows booted, and only happened after you "... continued with updates and things", please think back and consider if anything you may have done contributed to the problem you now have. The Windows UEFI/BIOS update method seems to have not even happened. You were able to use the UEFI/BIOS UI after the failed or never executed update, which does not seem likely if the update went wrong. Your conclusion that it was the cause of your display problem is based upon what, besides your feeling that it is? Can you go into the UEFI UI now, and stay in there indefinitely without the screen going blank? How did you install drivers after you installed Windows 10? Did you use the Express settings of Windows 10, which allows it to download and install drivers as Microsoft decides is best? Personally with a Windows 10 installation, I configure it to not install drivers and software automatically, and don't even connect to the Internet until after I have installed the basic driver set. Given the recent release of the Ryzen platform, what is Windows update installing that is preferred over the drivers provided by AMD that are provided on your board's download page? Also, a 00 POST code is a failure of the CPU. That is also seen when the 4/8 pin CPU power cable is not connected to the board. Any chance your PSU is having a problem, or that cable is not connected properly?


mgrandy@hotmail.co.u Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 20 Feb 2016 Location: uk Status: Offline Points: 65	Post Options Post Reply Quote mgrandy@hotmail.co.u Report Post Thanks(0) Quote Reply Posted: 12 Mar 2017 at 11:17am
	the reason you use dos is because its far more stable than windows as it uses just the basic functions this lessens the chance of corruptions what mdos is a file directory program without a UI what you should have on your card is mdos/flasher program/ file to flash can you locate the flasher program and if you do have the file have you located it throough mdos, using the mdos commands? and does the utility ask you to agree and then show a loading bar dr debug is pointing at your cpu with the error code so id hazard a guess that your cpu is at fault its cutting out for some reason you can still access windows right? and see the post and get into bios? dr debug im guessing is a built in "pci diagnostic card" which i might add is dyam handy! try lowering the clocks back to default and make sure you have the correct files for upgrading bios and repeat it seems your clocks are unstable for windows to load if its windows 10 i think it saves your clock settings in the os as well as in the bios i think so when your booting up bios is fine but when it loads your boosted settings during the os load it becomes unstable. from memory to remove clock settings in windows 10 i had to wipe the hdd but still check in the bios if its doing something it shouldn't and load a fresh copy of windows wiping the cmos will set the clock to default to prevent overclocking heres a link on how to check https://www.eightforums.com/tutorials/29504-bios-mode-see-if-windows-boot-uefi-legacy-mode.html if its in UEFI mode it will use your boosted clock setting regardless of what your bios wants i had the issue of i had saved the clocks from windows 7 @6.3 ghz when i loaded windows 10 it was using my clock settings for windows 7 that i had saved in the bios for future reference regardless of whether they worked or not it didn't even check just up and loaded at 6.3 followed by what your getting bar a code. Edited by mgrandy@hotmail.co.u - 12 Mar 2017 at 11:43am
	fx 9370 asrock, fatal1ty 970 performance 3.1, NZXT phantom f-atx, AeroCool Integrator 850W, Corsair Hydro Series H100

Hectic Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 12 Mar 2017 Status: Offline Points: 5	Post Options Post Reply Quote Hectic Report Post Thanks(0) Quote Reply Posted: 12 Mar 2017 at 9:46am
	Finally got all the parts and built up my new AMD build with the ASRock X370 Taichi motherboard, Ryzen 7 1800X processor, Corsair DDR4 3000 RAM and Windows 10 Pro. I put it together and turned it on yesterday, installed Windows no problem, then proceeded to install some drivers & programs. Got up this morning to continue and decided to go ahead and update the BIOS with the latest non beta version (1.5) before I continued to get better functionality CPU/RAM-wise. I used the Windows method, downloaded and executed the .exe file and it only took a second or 2 (thought that was a bit fast) and it asked to reboot. I hit yes and let the system reboot, but no update flashing of the bios took place. It just opened back up into bios showing the same version as before. I shrugged it off guessing it didn't do anything, but decided to try and OC the CPU just a bit by upping the multiplier a bit. Saved changes and rebooted. I booted back to Windows and started to continue w/ updates and things for a few minutes, then the screen went black and the Dr. Debug codes kept flashing '00'. I looked up the code meaning to check the CPU is connected correctly and to clear the CMOS. I checked the CPU (removed a little excess thermal paste) and cleared the CMOS back to defaults. (I cleared the CMOS numerous times) That update must have done something to screw things up because now anytime I tried to boot into Windows it does, but then goes blank and displays that same error code. I ran Killdisk in DOS and completely wiped the drive to do a fresher install of Windows than the first time, but when I tried to install again, it loads up the Window files then blanks out, same thing again. I even tried to upgrade bios using the DOS method, which they REALLY need to provide better instructions on/better way to do it, but I can't get it to upgrade that way either. I used Rufus to make the bootable USB (using a 16 GB drive) then copied the .exe file to it. I try booting to it, get some errors, then it goes to the C:\ prompt. I try to run the .exe file, but no go. Any ideas/helpful suggestions, or am I just going to have to RMA this thing back to Newegg? If this is what happens when trying to update bios...I'm nervous to even try at all. This needs some sort of bios flasher for Windows or especially in the bios! Having to make a bootable drive and boot to DOS then execute a file to update the bios is a primitive way to do this at best!