x299 i9 Gaming Pro BIOS 2.xx loosing bootmanager

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I am running my setup now for a few years without any real issues, until I got to the 2.xx BIOS updates.
The last FW version I am able to run is 1.90.

The setup: Fatal1ty X299 Professional Gaming i9
Intel Core i9-7900X 10 core CPU.
64GB DDR4.
3x Samsung 960 EVO NVMe M2 SSD's:
   2x 500GB in RAID0 for OS.
   1x 1TB for storage.

This is running fine on BIOS 1.90, but when I upgrade to 2.00 or 2.10 I start having issues after a few boots.
After the upgrade I setup the BIOS like I did on the 1.90 BIOS.
It shows the Windows Boot manager in the BOOT menu as default which is on the RAID0.
After that it boots fine into Windows 10 x64, but after that when I reboot within a few boots it looses the Windows Bootmanager setting in the BOOT menu and only shows the 1TB NVMe as boot selectable.
The Intel Rapid Storage menu shows the RAID0 partition fine and shows it as bootable but I am unable to select this in the boot menu.
I know when this is happening because the AsRock logo and BIOS options on the bottom right remains on screen during the boot and locks up after a while.
When I press F2 or DEL in the beginning it will go to the BIOS but it takes longer before it opens the UEFI BIOS.
If I wait too long it just hangs, seems like it is scanning something and somehow crashes and can't find the correct bootmanager in the NVMe RAID0 drive.

What is happening?

As soon as I flash BIOS 1.90 back and set it up the same way everything works great and keeps the Windows Bootmanager setting in the boot menu in the BIOS.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
SDeath Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 08 Oct 2017 Status: Offline Points: 5	Post Options Post Reply Quote SDeath Report Post Thanks(0) Quote Reply Topic: x299 i9 Gaming Pro BIOS 2.xx loosing bootmanager Posted: 08 Jul 2019 at 6:49pm
	I am running my setup now for a few years without any real issues, until I got to the 2.xx BIOS updates. The last FW version I am able to run is 1.90. The setup: Fatal1ty X299 Professional Gaming i9 Intel Core i9-7900X 10 core CPU. 64GB DDR4. 3x Samsung 960 EVO NVMe M2 SSD's: 2x 500GB in RAID0 for OS. 1x 1TB for storage. This is running fine on BIOS 1.90, but when I upgrade to 2.00 or 2.10 I start having issues after a few boots. After the upgrade I setup the BIOS like I did on the 1.90 BIOS. It shows the Windows Boot manager in the BOOT menu as default which is on the RAID0. After that it boots fine into Windows 10 x64, but after that when I reboot within a few boots it looses the Windows Bootmanager setting in the BOOT menu and only shows the 1TB NVMe as boot selectable. The Intel Rapid Storage menu shows the RAID0 partition fine and shows it as bootable but I am unable to select this in the boot menu. I know when this is happening because the AsRock logo and BIOS options on the bottom right remains on screen during the boot and locks up after a while. When I press F2 or DEL in the beginning it will go to the BIOS but it takes longer before it opens the UEFI BIOS. If I wait too long it just hangs, seems like it is scanning something and somehow crashes and can't find the correct bootmanager in the NVMe RAID0 drive. What is happening? As soon as I flash BIOS 1.90 back and set it up the same way everything works great and keeps the Windows Bootmanager setting in the boot menu in the BIOS.

Xaltar Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 16 May 2015 Location: Europe Status: Offline Points: 27803	Post Options Post Reply Quote Xaltar Report Post Thanks(1) Quote Reply Posted: 08 Jul 2019 at 10:04pm
	To report a bug with the UEFI I would contact Tech Support: https://event.asrock.com/tsd.asp When things like this pop up there is not much we on the forums can do to help unless it is just a setting gone awry (I doubt it in your case). By the sound of it the latest updates are not playing nice with your RAID array and hardware, that will need a BIOS fix. Tech Support will be able to help you.


SDeath Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 08 Oct 2017 Status: Offline Points: 5	Post Options Post Reply Quote SDeath Report Post Thanks(0) Quote Reply Posted: 08 Jul 2019 at 10:58pm
	Thanks Xaltar! I thought maybe somebody else seen these problems and knows a quick fix, if there is one. But couldn't find anything similar on the forum. I'll contact support and see if there have been anymore reports, and hope we can find a solution. With the volnerabilities fixed in the new microcodes I'd like to have the latest BIOS versions. Thanks again!