ASRock.com Homepage
Forum Home Forum Home > Technical Support > AMD Motherboards
  New Posts New Posts RSS Feed - Strange Boot Menu
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

Strange Boot Menu

 Post Reply Post Reply Page  <12345 7>
Author
Message Reverse Sort Order
Aurumvorax View Drop Down
Newbie
Newbie


Joined: 16 Jun 2018
Status: Offline
Points: 42
Post Options Post Options   Thanks (0) Thanks(0)   Quote Aurumvorax Quote  Post ReplyReply Direct Link To This Post Posted: 20 Jun 2018 at 2:39am
Originally posted by Xaltar Xaltar wrote:

That is entirely up to you. Looking through this thread though it does seem that just about every possible solution has been tried. 

The only other solution I can think of is using a ROM programmer (with a clip on adapter) to flash the BIOS remotely. That is a tricky prospect at the best of times and would require you purchase the necessary hardware to do it. It's a little over the top as solutions go. If your system came into my shop and was out of warranty, that is how I would resolve it but as a home user you are better off just RMAing it and getting a replacement. 

It's frustrating because the issue is actually very simple, some corrupt registers in the boot info.... 

On the up side, it seems ASRock is returning to replaceable BIOS chips on some of their newer models, sadly that doesn't help you. 

Personally, I would go about the RMA as soon as possible. You shouldn't have any trouble given how easy the issue is to fix with the right tools. I suppose you could also try taking it in to a Tech and seeing if it will be quicker/cheaper to have them remote flash the chip for you. It won't void the warranty or anything so may be worth a shot if you can find someone with the tools to do it.


I'm going to send it in. Hopefully they can fix it, since this board is EOL and I don't plan on getting another one.

Originally posted by datonyb datonyb wrote:

WE ARE FAILURES.....................................

Ouch


Don't say that! You tried your best. In the best case the board will be fixed the way Xaltar described. Hopefully I get it back as soon as saturday.
Back to Top
Xaltar View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 16 May 2015
Location: Europe
Status: Offline
Points: 24713
Post Options Post Options   Thanks (0) Thanks(0)   Quote Xaltar Quote  Post ReplyReply Direct Link To This Post Posted: 20 Jun 2018 at 2:37am
Originally posted by datonyb datonyb wrote:

WE ARE FAILURES.....................................

Ouch

All we can do is try to help, we can't solve them all sadly Wink

What matters is that we try Big smile
Back to Top
datonyb View Drop Down
Senior Member
Senior Member


Joined: 11 Apr 2017
Location: London U.K.
Status: Offline
Points: 3139
Post Options Post Options   Thanks (0) Thanks(0)   Quote datonyb Quote  Post ReplyReply Direct Link To This Post Posted: 20 Jun 2018 at 1:08am
WE ARE FAILURES.....................................

Ouch
[url=https://valid.x86.fr/jpg250][/url]

3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold
Back to Top
Xaltar View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 16 May 2015
Location: Europe
Status: Offline
Points: 24713
Post Options Post Options   Thanks (1) Thanks(1)   Quote Xaltar Quote  Post ReplyReply Direct Link To This Post Posted: 20 Jun 2018 at 12:53am
That is entirely up to you. Looking through this thread though it does seem that just about every possible solution has been tried. 

The only other solution I can think of is using a ROM programmer (with a clip on adapter) to flash the BIOS remotely. That is a tricky prospect at the best of times and would require you purchase the necessary hardware to do it. It's a little over the top as solutions go. If your system came into my shop and was out of warranty, that is how I would resolve it but as a home user you are better off just RMAing it and getting a replacement. 

It's frustrating because the issue is actually very simple, some corrupt registers in the boot info.... 

On the up side, it seems ASRock is returning to replaceable BIOS chips on some of their newer models, sadly that doesn't help you. 

Personally, I would go about the RMA as soon as possible. You shouldn't have any trouble given how easy the issue is to fix with the right tools. I suppose you could also try taking it in to a Tech and seeing if it will be quicker/cheaper to have them remote flash the chip for you. It won't void the warranty or anything so may be worth a shot if you can find someone with the tools to do it.
Back to Top
Aurumvorax View Drop Down
Newbie
Newbie


Joined: 16 Jun 2018
Status: Offline
Points: 42
Post Options Post Options   Thanks (0) Thanks(0)   Quote Aurumvorax Quote  Post ReplyReply Direct Link To This Post Posted: 19 Jun 2018 at 10:57pm
Originally posted by Xaltar Xaltar wrote:

Damn, I was hoping that would work.

So we know: 

1. The corruption is not coming from stored data in the UEFI
2. The drives themselves are not the problem
3. BIOS updates did not solve the issue
4. The problem persists even with no boot media connected

At this point I am going to go ahead and say you need to contact Tech Support or your place of purchase and start working on getting an RMA. If the BIOS ROM was removable you could have ordered a new BIOS chip but sadly the Gaming K4 has it's BIOS soldered to the board.

5 pages of troubleshooting with no solution Unhappy



Damn. Haven't got an answer from ASRock yet, and today arrived my new Vega 56 Hug
Would you suggest sending the board to the reseller now or wait for another couple of days? Maybe someone with the same problem stumbles across this thread?

Back to Top
Xaltar View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 16 May 2015
Location: Europe
Status: Offline
Points: 24713
Post Options Post Options   Thanks (0) Thanks(0)   Quote Xaltar Quote  Post ReplyReply Direct Link To This Post Posted: 19 Jun 2018 at 10:37pm
Damn, I was hoping that would work.

So we know: 

1. The corruption is not coming from stored data in the UEFI
2. The drives themselves are not the problem
3. BIOS updates did not solve the issue
4. The problem persists even with no boot media connected

At this point I am going to go ahead and say you need to contact Tech Support or your place of purchase and start working on getting an RMA. If the BIOS ROM was removable you could have ordered a new BIOS chip but sadly the Gaming K4 has it's BIOS soldered to the board.

5 pages of troubleshooting with no solution Unhappy
Back to Top
Aurumvorax View Drop Down
Newbie
Newbie


Joined: 16 Jun 2018
Status: Offline
Points: 42
Post Options Post Options   Thanks (0) Thanks(0)   Quote Aurumvorax Quote  Post ReplyReply Direct Link To This Post Posted: 19 Jun 2018 at 10:16pm
Originally posted by Xaltar Xaltar wrote:

Hmm, interesting.....

If you haven't tried already, pull power from the system, take out the drives and pull the CMOS battery. Place the clear CMOS jumper in the clear position and leave it like that over night. In the morning, put the clear CMOS jumper back in it's default position and replace the battery.

This should clear the RTC and any other non user addressable stored data in the UEFI (hopefully including the boot info).

Let us know if that sorts it.



I read your post this morning at 5:30 AM, and was following your advice immediately.  I returned from work at 3:30 PM, which gave it a total time of nearly ten hours. Times are CEST, I'm German.

Sadly, this didn't work either:



Again it's just a power cable, a display port cable and an USB keyboard that are plugged in.


Back to Top
Xaltar View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 16 May 2015
Location: Europe
Status: Offline
Points: 24713
Post Options Post Options   Thanks (0) Thanks(0)   Quote Xaltar Quote  Post ReplyReply Direct Link To This Post Posted: 19 Jun 2018 at 4:20am
Hmm, interesting.....

If you haven't tried already, pull power from the system, take out the drives and pull the CMOS battery. Place the clear CMOS jumper in the clear position and leave it like that over night. In the morning, put the clear CMOS jumper back in it's default position and replace the battery.

This should clear the RTC and any other non user addressable stored data in the UEFI (hopefully including the boot info).

Let us know if that sorts it.
Back to Top
Aurumvorax View Drop Down
Newbie
Newbie


Joined: 16 Jun 2018
Status: Offline
Points: 42
Post Options Post Options   Thanks (0) Thanks(0)   Quote Aurumvorax Quote  Post ReplyReply Direct Link To This Post Posted: 19 Jun 2018 at 3:57am
Originally posted by Xaltar Xaltar wrote:

With no drives connected and a bootable USB drive inserted, does the boot menu still look corrupt?

I am no expert on this but if memory serves the UEFI boot data is written to the drive, if that data is corrupt then it can cause this issue.

If your corruption clears with no drives connected then try reinstalling them one at a time and see if you can identify which one contains the corrupted data.



Thanks for looking into this. I made two new screenshots:



This is the F11-Menu just now, no drives, no USB, no network. Just a power cable, display port to monitor, and an old PS/2 keyboard.
Had to plug a USB-Pen to save the screenshot of course, but did so after the menu loaded.



Here's the boot section. As you can see, there are now drives connected. Nothing shown but the UEFI.

Stern Smile
Back to Top
Xaltar View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 16 May 2015
Location: Europe
Status: Offline
Points: 24713
Post Options Post Options   Thanks (0) Thanks(0)   Quote Xaltar Quote  Post ReplyReply Direct Link To This Post Posted: 19 Jun 2018 at 2:39am
With no drives connected and a bootable USB drive inserted, does the boot menu still look corrupt?

I am no expert on this but if memory serves the UEFI boot data is written to the drive, if that data is corrupt then it can cause this issue.

If your corruption clears with no drives connected then try reinstalling them one at a time and see if you can identify which one contains the corrupted data.
Back to Top
 Post Reply Post Reply Page  <12345 7>
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.109 seconds.