X370 Taichi, Debug code 55 after flash to 5.60

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

   I have a X370 Taichi and Ryzen 1600x. I went to the Asrock site to get the newest BIOS. I noticed that 5.80 said that it wasn't suitable for Summit Ridge (1600X). Therefore, I went to 5.60 and there were no warnings like that so I assumed 5.60 would be fine. There were detailed instructions, which I followed to the letter. First, was installing the latest AMD All in one driver. DONE. Second was flashing to 5.10. DONE. No problems noticeable with 5.10

Then finally I flashed to 5.60 BIOS said that it was a successful flash. But when it restarted, it got hung up on debug code 55. At this point I hadn't even touched the memory. So this is strictly a firmware issue in my mind.

I've attempted to orient the memory in every way imaginable with no luck. I've tried to clear the CMOS and I can't even tell if it is doing anything. I know that I left the BIOS battery out for quite a while with PSU off. When I put the BIOS battery back in, same thing. Code 55

Now here is the thing I wish I noticed before I started. It says that you cannot flash to a previous BIOS once 5.60 has been loaded. Could this be the reason why I can't clear CMOS?

I don't really want to do an RMA. Is there a third party solution I can use to get the ball rolling here? Perhaps a USB thumb drive with certain software?

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
SF0614R18 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 18 Oct 2019 Location: Florida Status: Offline Points: 14	Post Options Post Reply Quote SF0614R18 Report Post Thanks(0) Quote Reply Topic: X370 Taichi, Debug code 55 after flash to 5.60 Posted: 18 Oct 2019 at 1:00am
	I have a X370 Taichi and Ryzen 1600x. I went to the Asrock site to get the newest BIOS. I noticed that 5.80 said that it wasn't suitable for Summit Ridge (1600X). Therefore, I went to 5.60 and there were no warnings like that so I assumed 5.60 would be fine. There were detailed instructions, which I followed to the letter. First, was installing the latest AMD All in one driver. DONE. Second was flashing to 5.10. DONE. No problems noticeable with 5.10 Then finally I flashed to 5.60 BIOS said that it was a successful flash. But when it restarted, it got hung up on debug code 55. At this point I hadn't even touched the memory. So this is strictly a firmware issue in my mind. I've attempted to orient the memory in every way imaginable with no luck. I've tried to clear the CMOS and I can't even tell if it is doing anything. I know that I left the BIOS battery out for quite a while with PSU off. When I put the BIOS battery back in, same thing. Code 55 Now here is the thing I wish I noticed before I started. It says that you cannot flash to a previous BIOS once 5.60 has been loaded. Could this be the reason why I can't clear CMOS? I don't really want to do an RMA. Is there a third party solution I can use to get the ball rolling here? Perhaps a USB thumb drive with certain software?
	X370 Taichi (rev5.80) Ryzen 3400G with Vega graphics Nvidia GTX 1080

SF0614R18 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 18 Oct 2019 Location: Florida Status: Offline Points: 14	Post Options Post Reply Quote SF0614R18 Report Post Thanks(0) Quote Reply Posted: 18 Oct 2019 at 1:10am
	So right now I can't get into the BIOS at all. Smashing F2 as soon as I power up and it gets hung up on the debug code before BIOS.
	X370 Taichi (rev5.80) Ryzen 3400G with Vega graphics Nvidia GTX 1080

SF0614R18 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 18 Oct 2019 Location: Florida Status: Offline Points: 14	Post Options Post Reply Quote SF0614R18 Report Post Thanks(0) Quote Reply Posted: 18 Oct 2019 at 1:14am
	I tried some g.skill 3200 i had laying around and that wouldn't work either. i have no idea what asrock will attempt to charge me for rma fees, this is out of warranty by just a little i'm not entirely convinced it's appropriate for me to pay anything. someone should have to tell me what I did wrong, no? at this moment, i don't feel like i did anything wrong. and i could be wrong, but i feel like asrock kind of screwed up.
	X370 Taichi (rev5.80) Ryzen 3400G with Vega graphics Nvidia GTX 1080

SF0614R18 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 18 Oct 2019 Location: Florida Status: Offline Points: 14	Post Options Post Reply Quote SF0614R18 Report Post Thanks(0) Quote Reply Posted: 18 Oct 2019 at 1:55am
	Well anyways, it appears Asrock wants me to do an RMA so I guess that's what going to happen. I tried posting this situation on like three different forums and nobody really had the answer. I'm not mad, that's just how it goes sometimes.
	X370 Taichi (rev5.80) Ryzen 3400G with Vega graphics Nvidia GTX 1080

Ray62 Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 01 Jul 2018 Location: Germany, Berlin Status: Offline Points: 706	Post Options Post Reply Quote Ray62 Report Post Thanks(0) Quote Reply Posted: 18 Oct 2019 at 4:12am
	5.10 was the last Version for Gen1 and Gen2 CPUs. "Update AMD AGESA to 1.0.0.6" means AMD_PinnaclePi_1.0.0.6 Yes, very bad documented and the brain damaged AGESA version scheme from AMD is in no way acceptable. Because of that some guys made a table for all AM4 mainboard vendors and the bios versions: https://www.hardwareluxx.de/community/f12/ultimative-am4-uefi-bios-agesa-ubersicht-17-10-19-a-1228903.html
	Asrock Fatal1ty X370 Professional Gaming Offline Under test: MSI X570_MEG_ACE \| AMD Ryzen 9 3900X \| Scythe Mugen5 \| 2x16GB F4-3200C14D-32GTZ@3466 \| ASUS GeForce GTX 1080 Ti FE

Ray62 Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 01 Jul 2018 Location: Germany, Berlin Status: Offline Points: 706	Post Options Post Reply Quote Ray62 Report Post Thanks(0) Quote Reply Posted: 19 Oct 2019 at 10:43pm
	Debug code 55 seems to be "Memory not installed". Did you try it with one RAM stick in A2 and no drive connected? There would be a way for downgrading, but it requires a running windows.
	Asrock Fatal1ty X370 Professional Gaming Offline Under test: MSI X570_MEG_ACE \| AMD Ryzen 9 3900X \| Scythe Mugen5 \| 2x16GB F4-3200C14D-32GTZ@3466 \| ASUS GeForce GTX 1080 Ti FE

Hartukktu Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 16 Jan 2018 Location: Leiden Status: Offline Points: 10	Post Options Post Reply Quote Hartukktu Report Post Thanks(0) Quote Reply Posted: 02 Nov 2019 at 8:22am
	Running 5.60 with R5 1600 just fine. Have crucial ballistix 2 x 16 GB 3000 CL15 RAM, running @3200. Did load latest chipset drivers and upd as Ted all devices in device manager.

Hartukktu Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 16 Jan 2018 Location: Leiden Status: Offline Points: 10	Post Options Post Reply Quote Hartukktu Report Post Thanks(0) Quote Reply Posted: 19 Nov 2019 at 3:17am
	Also: to really reset the CMOS: unplug (physically remove the 220/110 V powercable from power supply, other wise the mainboard will still receive a trickle of power) remove the CMOS battery. Let sit for five minutes. press the clear CMOS button for a couple of seconds. Then put in the battery and power cable. Turn on the computer, go into BIOS and load defaults. power off. power on, and re-setup the BIOS to your liking (in my case: setup the RAM speed, make sure the IO and processor virtualization features are turned on are turned on, make sure the fan profiles are OK and so on and so forth) By the way the Crucial Ballistix is Micron E-die and really great, runs at 3200 MHz no problem.

SpotAnime Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 18 Dec 2019 Status: Offline Points: 4	Post Options Post Reply Quote SpotAnime Report Post Thanks(0) Quote Reply Posted: 18 Dec 2019 at 9:33am
	Hey SF0614R18, curious whatever happened with this? I ended up having the EXACT same issue a couple of weeks back, but I was able to successfully rollback the BIOS to 5.10. But running a 1700X, 5.10 works great, 5.60 gave me Dr. Debug 55 errors. I even bought new DDR4 G.Skill ram thinking my memory went bad, but got the same error. Only rolling back solved the problem. If it's truly an electronic issue causing this, I guess I should RMA it. But I kinda don't want to be without my computer for that long...