Strange Boot Menu |
Post Reply | Page <12345 7> |
Author | ||
Aurumvorax
Newbie Joined: 16 Jun 2018 Status: Offline Points: 42 |
Post Options
Thanks(0)
|
|
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.
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. |
||
Xaltar
Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 24713 |
Post Options
Thanks(0)
|
|
All we can do is try to help, we can't solve them all sadly What matters is that we try
|
||
|
||
datonyb
Senior Member Joined: 11 Apr 2017 Location: London U.K. Status: Offline Points: 3139 |
Post Options
Thanks(0)
|
|
WE ARE FAILURES..................................... |
||
[url=https://valid.x86.fr/jpg250][/url]
3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
||
Xaltar
Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 24713 |
Post Options
Thanks(1)
|
|
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.
|
||
|
||
Aurumvorax
Newbie Joined: 16 Jun 2018 Status: Offline Points: 42 |
Post Options
Thanks(0)
|
|
Damn. Haven't got an answer from ASRock yet, and today arrived my new Vega 56 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? |
||
Xaltar
Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 24713 |
Post Options
Thanks(0)
|
|
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
|
||
|
||
Aurumvorax
Newbie Joined: 16 Jun 2018 Status: Offline Points: 42 |
Post Options
Thanks(0)
|
|
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. |
||
Xaltar
Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 24713 |
Post Options
Thanks(0)
|
|
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.
|
||
|
||
Aurumvorax
Newbie Joined: 16 Jun 2018 Status: Offline Points: 42 |
Post Options
Thanks(0)
|
|
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. |
||
Xaltar
Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 24713 |
Post Options
Thanks(0)
|
|
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.
|
||
|
||
Post Reply | Page <12345 7> |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |