Print Page | Close Window

Bug - AB350 Pro4 F11 boot menu corrupt

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=6633
Printed Date: 10 May 2024 at 9:55pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com


Topic: Bug - AB350 Pro4 F11 boot menu corrupt
Posted By: G-Force
Subject: Bug - AB350 Pro4 F11 boot menu corrupt
Date Posted: 19 Nov 2017 at 12:10am
The AB350 Pro4 has a really annoying F11 boot menu bug. I use my PC with both Windows and Linux, and I dual boot via the F11 menu so I don't have to deal with bootloaders failing after each Windows 10 update.

Anyway, the F11 boot menu visually corrupts itself and does not allow me to select an option when there are too many entries in the boot menu. I don't know how much entries, but I do know that when the CSM is enabled the menu just can't be used.

Workaround for now is to disable the CSM so there are only UEFI options showing. But in a case where I need legacy BIOS support this would not be an option.

Can ASRock please take a look at this and try to fix it? I think it has been a bug in more of your motherboards with the UEFI BIOS so I think it's time to fix it.

Thanks in advance.

Found an image online of the exact same issue, with a different board. For the AB350 Pro4, it's exactly this...





Replies:
Posted By: MisterJ
Date Posted: 19 Nov 2017 at 12:32am
" rel="nofollow - G-Force, this is a user forum and you are hard pressed to see an ASRock employee here.  I suggest this is a problem with your MB and recommend you open a support ticket and see if an RMA is appropriate.  I guess it is possible that another user would have your problem.  Here is something similar: http://forum.asrock.com/forum_posts.asp?TID=6609&KW=korean&PID=39354&title=x399-fatal1ty-temperature-sensors-wrong-stays-on#39354
Maybe some of the same characters.  Enjoy, John.


-------------
Fat1 X399 Pro Gaming, TR 1950X, RAID0 3xSamsung SSD 960 EVO, G.SKILL FlareX F4-3200C14Q-32GFX, Win 10 x64 Pro, Enermx Platimax 850, Enermx Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 2.00, 2xHDDs WD


Posted By: ScomComputers
Date Posted: 19 Nov 2017 at 6:12pm
This is what I have, but only since the new bios!
***x370 Gaming X***Bios 3.40***



Posted By: datonyb
Date Posted: 19 Nov 2017 at 7:05pm
" rel="nofollow -
on the taichi forum at overclockers a guy called chew (works alongside amd and is a tester for some asrock bios )

mentioned sometimes the bios updates are leaving traces of last bios inbedded
he has started using the dos flash method instead of internet/usb flash

but i think (cant recall 100%) he said its only when he was flashing 'back' to earlier bios

maybe this is a sympton of such traces from last bios ?


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

3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold


Posted By: ScomComputers
Date Posted: 20 Nov 2017 at 12:36am
" rel="nofollow -
I reflash the old(3.20) bios,and not fixed this problem...please help me how to fix it?
I now use the boot override in the bios.
:)


Posted By: MisterJ
Date Posted: 20 Nov 2017 at 12:59am
ScomComputers and G-Force, both of you need to open a ticket with ASRock Tech Support - ASAP!  Something is very bad wrong when the BIOS is getting corrupted when updated!  Immediate action is required!  Remember, this is a user forum and almost no one represents ASRock - I surely do NOT!  Enjoy, John.


-------------
Fat1 X399 Pro Gaming, TR 1950X, RAID0 3xSamsung SSD 960 EVO, G.SKILL FlareX F4-3200C14Q-32GFX, Win 10 x64 Pro, Enermx Platimax 850, Enermx Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 2.00, 2xHDDs WD


Posted By: Asingo
Date Posted: 20 Nov 2017 at 8:05pm
" rel="nofollow - I also have this on my x370 k4 since 3.20 bios update (2 month ago - didn`t thought that this is important). Should I try to update on newer bios and if it is still her I need to RMA board in my local store?


Posted By: ScomComputers
Date Posted: 20 Nov 2017 at 9:36pm
Asingo opens you a ticket with ASRock Tech Support - ASAP, I've already done it!
Wink


Posted By: Asingo
Date Posted: 20 Nov 2017 at 10:15pm
" rel="nofollow - Is it really necessary to do this ASAP and directly in Asrock? Since X370 K4 is EOL what board would they give me? X370 Gaming X which is worse that x370 K4? I was thinking that I RMA in my local store so that I can refund money or choose something other like x370 Taichi....

I have his problem around 1-2 month, what problem can can it cause? First I asked here about this long time ago but I did get no right answer how to solve it.


Posted By: ScomComputers
Date Posted: 21 Nov 2017 at 8:37pm
I'll send it back to the store and get the money back, that's it!
Tongue


Posted By: G-Force
Date Posted: 22 Nov 2017 at 1:39am
Latest BIOS update: no improvement. Even after reflashing. On top of that, it doesn't do anything with the order of boot items I set in the BIOS. This worked fine in the previous version.

I set it to 1: Linux Boot Manager, 2: Windows Boot Manager and 3: UEFI Shell. No matter what I do, it puts Windows and UEFI shell on the top of the list.

Anyway, I'm done with this buggy ASRock piece of crap. I will return it to the retailer tomorrow.

Lesson learned, spend a little bit more on a quality motherboard.


Posted By: SejoDrogba
Date Posted: 18 May 2018 at 9:32pm
Hi I can that fix it..Contact me per E-mail
sejo_drogba11@live.com


Posted By: andre117
Date Posted: 21 Jun 2018 at 10:10pm
It is probable not an UEFI Bios bug.

There might be an orphaned UEFI boot entry in your system that points to a location where it no longer exists.

Try this tool:

https://www.easyuefi.com/faq/en-US/Delete-UEFI-Boot-Entries.html" rel="nofollow - https://www.easyuefi.com/faq/en-US/Delete-UEFI-Boot-Entries.html

Check for orphaned entries and remove them (if you are still able too boot windows).
The same thing can be done under linux. See efibootmgr here.




Posted By: Asingo
Date Posted: 25 Jun 2018 at 4:50am
 I had that with my x370  K4. Only solution was to send it to RMA.


Posted By: Sohanuzzaman
Date Posted: 12 Jul 2018 at 3:42am
I have the same problem
Can you help me


Posted By: brewcrew87
Date Posted: 19 Aug 2018 at 12:34pm
Originally posted by andre117 andre117 wrote:

It is probable not an UEFI Bios bug.

There might be an orphaned UEFI boot entry in your system that points to a location where it no longer exists.

Try this tool:

https://www.easyuefi.com/faq/en-US/Delete-UEFI-Boot-Entries.html" rel="nofollow - https://www.easyuefi.com/faq/en-US/Delete-UEFI-Boot-Entries.html

Check for orphaned entries and remove them (if you are still able too boot windows).
The same thing can be done under linux. See efibootmgr here.



I know this thread is old, but I wanted to say thanks...  I had a corrupted value on my boot menu from this due to an issue I had when installing Mac OS on my PC.  I was able to use this to get rid of the erroneous Clover EFI and now I can quickly boot between OSX and W10 via the F11 shortcut (I could still go all the way into the BIOS and change the boot sequence the manual way).

Nice little tool that is for sure.



Print Page | Close Window

Forum Software by Web Wiz Forums® version 12.04 - http://www.webwizforums.com
Copyright ©2001-2021 Web Wiz Ltd. - https://www.webwiz.net