BIOS Recovery 990FX Extreme9
Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=2625
Printed Date: 27 Dec 2024 at 2:18am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: BIOS Recovery 990FX Extreme9
Posted By: oztane
Subject: BIOS Recovery 990FX Extreme9
Date Posted: 09 May 2016 at 7:04pm
|
Hello, I have a 990FX Extreme9 mother board. Yesterday I updated the BIOS to 1.80, and now I cannot get it to do anything. The error on the Dr. Debug has changed a bit: F2 I cleared CMOS 05 I reset my RAM and CPU then started doing it one stick at a time. Currently it is at 05. I believe the issue has to do with the BIOS. However, since the last thing I did was upgrade BIOS, I am wondering if something happened. Is there a type of recovery I can get to reflash?
|
Replies:
Posted By: eire1274
Date Posted: 23 Aug 2016 at 10:46am
|
Adding my complaint. I updated to 1.80 for NVMe over PCIe connectivity, and though the BIOS/UEFI update completed through the 1.70 UEFI control panel, the system will not recognize the CPU and displays "00", DrDebug = incompatible CPU. Nothing I can do will make it boot. I need to start the Crashfree BIOS to reload 1.70, but I can't get any key recognition, either. ASRock 990FX Extreme9 v1.4 AMD 9590FX 4x G.Skill Sniper DDR3 2133Mhz 8GB Corsair G 240GB SSD (NVMe SSD not yet purchased, thankfully) 2x WD Black 2TB 2x Sapphire Vapor-X R9 280X OC in Crossfire Windows 10 Pro 64-bit This is my video production machine, so being down (I was down earlier in the year due to a MB failure and RMA) is painful! My backup machine is an i5 laptop, so minimal OpenCL capability. What the desktop can render in an hour takes more than a day!
|
Posted By: wardog
Date Posted: 23 Aug 2016 at 1:09pm
|
Corsair G, or GS ? Try pulling the power and data from the Corsair SSD, clear not reset the BIOS, and see if she boots with KB support. BTW, What KB, and it should be in a USB 2.0 port at the rear I/O to try this. parsec here is an SSD/Sandforce controller whiz. Let me get his attention and see if he has ideas. |
Posted By: parsec
Date Posted: 23 Aug 2016 at 8:03pm
|
I don't see this as a NVMe SSD issue, since eire1274 is not using the new Corsair SSD yet. Plus the 00 Dr Debug code is CPU failure, and the POST checks of drives is done at the end of POST, CPU POST tests happen first. So I don't think this is SSD related. Sorry we missed the OP, who posted in May...  Quite a jump in time between 1.70 and 1.80, almost two years. If POST fails as it has with the 00 code, the PC is non-functional, no chance of getting into the UEFI/BIOS at all to change to 1.70, or whatever. You consistently get 00 on the Dr Debug display, right? All I can suggest now is removing the board's battery for an hour, but don't clear the UEFI/CMOS yet. If the battery removal does not work, then try a CMOS clear, which is normally not recommended right after a UEFI/BIOS update. I have done that once or twice without ruining anything. Have you done UEFI/BIOS updates with the Crossfire setup in the past without any problems? Perhaps the 1.80 UEFI has a bug, but we haven't been flooded with posts about it. Please keep us updated if you made any progress, or not. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
Posted By: justin
Date Posted: 27 Oct 2016 at 1:58am
|
" rel="nofollow - I do not have any NVMe, just two older Vector SSDs in RAID 1 via Sata3 for OS and HighPoint card in RAID 10 for data. My experience was the same--1.7 worked fine with FX8350 until I did the update to 1.8 in May. I used instant flash from inside of the BIOS and the result said "successful, press finish to continue" or similar. Result was straight to 00. Reseating CPU and memory made no difference. Also tried the battery removal for an hour and then CMOS clear. It was out of warranty, so simply purchased a new 990FX extreme9 and took the opportunity to upgrade to an FX9590. Worked fine until last night when my brain went out for a break without informing me and I clicked update on the BIOS again. Now back to 00 code. Tried the battery out for an hour thing and the CMOS clear button to no avail. Anyone have any luck at all? |
Posted By: parsec
Date Posted: 27 Oct 2016 at 8:38am
First I want to say that I am NOT questioning your statement about this happening to your boards and UEFI 1.80, or implying anything else in any of the following. I'm somewhat surprised you bought another Extreme9 board after your experience with the 1.80 UEFI. Meaning I doubt I would have done the same thing.  FYI, whatever it is that causes this to happen would not automatically disappear in any new UEFI updates, unless this situation is specifically listed as fixed in the description of the new version. So don't update your UEFI again unless you know it is safe. I know you did it accidentally this time. I am surprised that we have not heard of this situation happening from more owners of this board. If it happened to every owner of this board, we should be flooded with complaints about it, but apparently that is not the case. It would be extra strange if this only happens to a handful of users of this board. The question then would be, why? I am not aware of any simple fix for this problem, since this thread ended abruptly until your post woke it up. I can tell you that replacing the UEFI chip with the 1.70 UEFI version should get the board working again. The UEFI chip is in a socket, not soldered in place, and can be replaced. You can get that chip from ASRock, or from sources on eBay, both will load the chip with the UEFI version of your choice. I'll provide the link for ASRock as the source. Sorry but the forum's link tool is broken for some links, that is the correct URL: http://www.asrock.com/support/index.asp?cat=RMA If I had my choice, I would send you one free of charge, but I can't do that. I assume the lack of any update implies that this situation is not common, or that the 1.80 UEFI is the cause and will happen to anyone that owns this board. You said it happened with two FX processors models, which is odd. There is no reason I can think of why adding NVMe support would cause a CPU failure. One of the moderators here is now using an 990FX Extreme9 with an FX-9590. I'm curious what UEFI version he has in his board. ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
justin wrote:Posted By: wardog
Date Posted: 27 Oct 2016 at 9:25am
|
Odd. I just yesterday built the 990FX Extreme9/9590 in my sig and used Instant Flash from within the BIOS to go to 1.80. Knock on wood apparently, w/o issue. I wonder if folks who've this has happened are using the correct rear usb 2.0 and not the incorrect Etron usb 3.0 ports. |
Posted By: parsec
Date Posted: 27 Oct 2016 at 10:32am
Perfect timing. That seems to explain the lack of more complaints about the 1.80 update. If you are not dead in the water immediately after the 1.80 update, apparently you won't ever be. Now to identify the reason. Your comment is one possibility. There's a guy that apparently bricked his Intel board using an NTFS formatted USB flash drive for an Instant Flash update. ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: wardog
Date Posted: 27 Oct 2016 at 10:42am
The 9xx chipsets do not have native USB 3.0. Instead relying on 3rd party Etron or whoever USB 3.0 controllers. |
Posted By: parsec
Date Posted: 27 Oct 2016 at 10:54am
" rel="nofollow -
But will the USB flash drive even be recognized by Instant Flash in one of the Etron USB 3.0 ports? ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: wardog
Date Posted: 27 Oct 2016 at 11:51am
I'll post tomorrow if it does. IIRC it does. Maybe ASRock could disable Instant Flash from recognizing the non-native usb 3.0 ports. That'd be nice, if in fact that is what's happening. But it'll have to wait as I'm tired and the bed's calling my name. |
Posted By: wardog
Date Posted: 27 Oct 2016 at 6:46pm
Quixotically, yes it is. Which again I'll stand by my original conclusion of folks mistakenly using a usb 3.0 port with which to flash/brick. |
Posted By: jamiea249
Date Posted: 29 Oct 2016 at 9:05am
| I have the 1.80 bio and have no problem with that but I was on 1.70 and at late I have been having problem with the display turning off and no the plugs are fine no problems there is my GC getting hot no it stays at 35c to 40c even under load this would happen at random time made no changes to the computer there has been a few drivers that have been updated at late but nothing that would make this happen. I check a few other things some times it would give me a code error 62 after this happens. some times I would be working on stuff with like no load then it would have this happen at random. I try restarting with reset but then gives me code error 62 then I have to press and hold power button then to shut it down and then restart that way to get it to work right. some times I can have it in sleep mode and then a few minutes later it would do this to. but not every time, I have this same motherboard. this error just started happening for the last few days. any help would be great. |
Posted By: wardog
Date Posted: 29 Oct 2016 at 10:16am
" rel="nofollow -
Odd. 62 is chipset initialization and the way around that is to rest the BIOS. Scroll down to page 3: http://asrock.com/support/qa/TSDQA-102.pdf Have you added any hardware recently? Too, if you've had your board for any length of time I'd replace the CMOS battery and cross my fingers. |
Posted By: frapuni
Date Posted: 03 Feb 2021 at 4:07am
|
Another BIOS (MB?) bricked by a succesfull (but not gone as expected) bios upgrade to 1.80. I admit, I used USB3 port, actually it's not written anywhere using USB2 is mandatory... shouldn't InstantFlash verify bios integrity anfter having loaded it and before flashing it? I don't know. Anyway it immediately found the bios and loaded it into motherboard. "Bios upgrade succesful" or something like that. Press OK to reset. I hit Enter and NOTHING. Dr Debug = 00. Never changed to anything different after bios upgrade. Before the PC worked and booted like a charm. 1.70 BIOS was present. Now I really hope a BIOS chip from EBay can solve it seeing no flashback\recovery feature is present. Will it? Thanks for help. |
Posted By: wardog
Date Posted: 03 Feb 2021 at 6:15am
Have you tried a HARD BIOS reset? Battery out, then BIOSCLR jumper to short? |
Posted By: frapuni
Date Posted: 03 Feb 2021 at 6:19am
Yes, of course. I waited one hour. tonight I am trying the full night without battery no power CLRTC\CMOS jumper on reset and tomorrow I'll try again but every reset tries have been a no go. |
Posted By: frapuni
Date Posted: 04 Feb 2021 at 12:24am
|
Tried after an entire night of no battery following the procedure in this forum. Nothing. Still Dr Debug 00 with little flickering too. Motherboard and fans turn on. After a while some fans like video card stop. No post, black screen. |
Posted By: frapuni
Date Posted: 06 Feb 2021 at 5:26am
|
I wrote to Asrock support. They have been very kind and they'll send me a new BIOS chip. They think it could solve the problem. They told me that USB2 or USB3 port is not relevant (even if just USB2 ones support BIOS feature to be recovered in case of power failures). I have just been unlucky, as some other guys here. I will change BIOS chip as soon as it arrives and let you know. |
Posted By: frapuni
Date Posted: 09 Feb 2021 at 10:49pm
| Received new BIOS chip from Ebay. WORKED PERFECTLY (just the GUID firewire error but it is sufficient to disable firewire) |