X370 Gaming K4 Dr.Debug 00

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

   Computer has been working fine since Dec, never had a problem, etc.  But I fell behind on UEFI updates (was on 4.60).  I tried to flash 4.80 and now my system won't post what so ever - all I get is a Dr. Debug code 00.  Any way to recover from a bad flash or am I up ----- creek with out a paddle?

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
nukedathlonman Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 25 Nov 2017 Location: AB, Canada Status: Offline Points: 6	Post Options Post Reply Quote nukedathlonman Report Post Thanks(0) Quote Reply Topic: X370 Gaming K4 Dr.Debug 00 Posted: 10 Sep 2018 at 9:04am
	Computer has been working fine since Dec, never had a problem, etc. But I fell behind on UEFI updates (was on 4.60). I tried to flash 4.80 and now my system won't post what so ever - all I get is a Dr. Debug code 00. Any way to recover from a bad flash or am I up ----- creek with out a paddle?

kerberos_20 Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 06 Dec 2017 Location: czech republic Status: Offline Points: 3687	Post Options Post Reply Quote kerberos_20 Report Post Thanks(0) Quote Reply Posted: 11 Sep 2018 at 4:46am
	reset cmos, unplug ram, if u have speakers u should hear beeps if u get no beeps and u do have speaker connected to mobo, they u will need to RMA mobo
	userbenchmark

nukedathlonman Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 25 Nov 2017 Location: AB, Canada Status: Offline Points: 6	Post Options Post Reply Quote nukedathlonman Report Post Thanks(0) Quote Reply Posted: 11 Sep 2018 at 5:00am
	I waiting to hear back from ASRock. But I tried all that except for the beeps - no speaker. Even tried the AMIBIOS8 trick of loading a working BIOS on a usb stick (with the file name set to AMIBIOS.ROM) and turing on the computer - no go. I grabbed an MSI X370 Pro Carbon to use in the mean time, hopefully ASRock gets back to me quickly. Edited by nukedathlonman - 11 Sep 2018 at 5:00am

kerberos_20 Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 06 Dec 2017 Location: czech republic Status: Offline Points: 3687	Post Options Post Reply Quote kerberos_20 Report Post Thanks(0) Quote Reply Posted: 11 Sep 2018 at 5:10am
	speaker has 2 pins +5V and ground use some internal led if u got no speaker, like for hdd activity or power led they use same 5volts connect it to speaker pins + to + ground to ground u will not hear any sound (its a led) and what led does? it will light up :) sooo if u will see no light from that led then it same as hearing no sound from speaker (no input) without ram it should light up 3 times
	userbenchmark

ket Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 13 Jul 2017 Location: UK Status: Offline Points: 1676	Post Options Post Reply Quote ket Report Post Thanks(0) Quote Reply Posted: 12 Sep 2018 at 3:00am
	You could invest in a CH341A programmer and SOIC8 clip to reprogram your ROM chip - no RMA process necessary assuming it is just a bad update. I do keep mentioning in my Asrock reviews that the boards should have a backup ROM chip to allow easy recovery from these situations. Maybe one day.