Dr Debug loops, Internet Flash FAIL, ASRock Z97 Extreme 6 won't start,

HvStV

Reputable
Aug 15, 2015
13
0
4,510
Hi,

I just got a ASRock Z97 Extreme6. And because I wish to have it run at it's best and ready for all CPU's, I started by updating the BIOS. So only a small amount of mem, a test CPU (G1820) mouse and keyboard. O, and an internet cable.
I used Internet Flash which seemed like a smart thing to do. But after downloading the BIOS it says something like 'Flash fail' in a textballoon which has an 'OK' button so after reading of course I clicked it. After that it started doing stuff and asked me not to turn of computer, which seems more then logical; one does not mess with the BIOS, one just follows instruction.
At the end the process asked or mentioned a reboot. But it got stuck in loop when it did. After a while I noticed the MoBo was in BIOS B. And because I read somewhere it wasnt possible to update BIOS B I figured that would have been the issue and so... switched it to BIOS A.

This time my keyboard wasn't found by the MoBo/start up so I couldn't enter one of the mentioneed functionkeys (I believe F2,F11,F1). So I bought 2 new keyboards. one with USB, one with PS/2. The last mentioned I used first and hooray, I could continue. Again I went for Internet Flash and above happened to this BIOS as well; flash fail.

So now the only thing I get is Dr. Debug looping with longer periods waiting at: 10, 35, 36, F2, F9. F2, F9, 35, 4F, 35 4F, 35. 4F, and then repeats the serie over and over.

Or with info about what the code means:
10 - PEI Core is started
35 - CPU post-memory initialization. Boot Strap Processor (BSP) selection
36 - CPU post-memory initialization. System Management Mode (SMM) initialization
F2 - Recovery process started
F9 - Recovery capsule is not found
F2 - Recovery process started
F9 - Recovery capsule is not found
35 - CPU post-memory initialization. Boot Strap Processor (BSP) selection
4F - DXE IPL is started
35 - CPU post-memory initialization. Boot Strap Processor (BSP) selection
4F - DXE IPL is started
35 - CPU post-memory initialization. Boot Strap Processor (BSP) selection
4F - DXE IPL is started

When I press reset it sometimes restarts the setup (one in ten or so?), but mostly it just starts with Dr. Debug with the loop sequence at 10, so that's why I mention it as the first code.

Hardware:
System Specs:
Asrock z97 extreme6
Intel Celeron G1820 (+CNPS 10X Extreme cooler)
2x2GB DDR3 (CMV4GX3M2A1333C9) in slots A2 and B2
Zalman ZM360B-APS
BIOS V. 1.xx (can't really remember if it was 1.30/40/60/70, I lean towards 1.70)

Anyone any suggestion how to get this fixed?

I feel a bit fooled by ASRock and it's own 'savest way to update the BIOS'. Seems almost like a NoNo.

Thanks

edit 05/01/16 13:28: info about BIOS clearified, typo's.
 

HvStV

Reputable
Aug 15, 2015
13
0
4,510
Update: At the moment I dismantled the setup so nothing is in touch with the MoBo.
I cleared CMOS by pressing the button at I/O and again with the jumper.
I took out the battery and hopefuly tomorrow it wil be fine again.
But in al fairness, this hardly seems like a valid solution.
 

HvStV

Reputable
Aug 15, 2015
13
0
4,510


Thank you for replying, however luckily you are wrong. :bounce::) That's good news none the less.

Since I've posted above a few developments. With a solution that doesn't include RMA. It takes less then a minute and not much skill actually.

First: ASRock support kindly assisted me and suggested to download the file to USB (flash-drive) and put it in a USB2 port. Apparently I misunderstood the specifics at first. Thinking it would only help me if I could get into (the second) BIOS. Most likely I mixed up 2 possible solutions brought by ASRock Support. Perhaps not. In the end it doesn't matter because it did result in a resurrection of my precious motherboard. So many thanks and thumbs up for ASRock after all!

Anyhow, ASRock generously send me a new set of BIOS-chips WITH the updated version 2.50 after mentioning both my BOIS's couldn't start up.

However, waiting isn't my favourite thing so I tried the updated BIOS on flash drive and stuck it in the USB-port mid-board (next to BIOS-chips) and pressed F6 continuously. Pressing F6 was one of the suggestions, however I thought it could only work WHILE BEING IN BIOS SETTINGS. Can't say for sure if pressing F6 made any difference. Non the less it (F6 and/or putting flash in USB drive) kick-started a install of the new BIOS. And after I could copy to BIOS B and I'm a happy person again.

Looking back at it all, perhaps the F2 code in Dr. Debug (F2 - Recovery process started) could mean it's trying to connect to the USB-port mentioned to get a new (or any) BIOS executable install program (download "instant flash"). Because of the USB2_0 being without the flash-drive with the unpacked version of the instant install it returned with F9 - (Recovery capsule is not found).

So (without any real prove, but confident about it non the less) I'm concluding a motherboard can still be fixed with just an Flash-drive (with a BIOS version) if the code F2 will show in Dr. Debug. If anyone should find himself in the same situation, I would suggest not to press F6 when starting up with the Flash-drive with downloaded and unpacked BIOS instant-flash file (.exe) in place.

I will not recreate the incident but if anyone finds this helpful I'm interested if it's an automated restore or if it's triggered by F6. And thus proving my conclusion one way or the other.

At least RMA isn't needed.
 

thepotatoman

Prominent
Jan 21, 2018
1
0
510
Thanks so much for this. I just had the same exact problem and that solution fixed it. I can also confirm that hitting f6 is required. It did nothing when I didn’t hit f6.

I thought updating bios might fix an issue I had with a usb controller, but now I know to save that solution as the very last resort.