Jump to content

I bought a pc off of marketplace. When i tried to boot it up it game me the error restart and select proper boot device. I thought maybe he wiped the drive completely. 
i put my on windows ssd in it and same issue. However disabling CSM allow for it to boot into windows lock screen but then immediately  crash. Then its a repeating crash cycle until i enable CSM. 

 

Any idea on the issue?

 

aorus b450 pro wifi

2600x

both m.2 ssd

 

i cant update the bios (to any version) either bcuz i get the “invalid image file”  error. 
a reported fix i saw online was to remove the first letter from the file name. It was a B for me from B450…..  

didnt wirk for me. 

Link to comment
https://linustechtips.com/topic/1575332-roboot-and-select-proper-boot-device-error/
Share on other sites

Link to post
Share on other sites

Make sure the motherboard is the same as this one https://www.gigabyte.com/Motherboard/B450-AORUS-PRO-WIFI-rev-1x#kf

If not the BIOS files from there will not work.


Also most BIOSES will let you press F12 for a quick boot menu during startup. See if you then can select the right drive.

 

Also when i sell a computer i format the HDD so there is nothing on there. Maybe the seller did this too?

(It cant boot from a drive thats empty)

When i ask for more specs, don't expect me to know the answer!
I'm just helping YOU to help YOURSELF!
(The more info you give the easier it is for others to help you out!)

Not willing to capitulate to the ignorance of the masses!

Link to post
Share on other sites

Ok so i solved everything. 
the error “please restart pc and select the correct boot drive” was a bios issue. 
 

The current bios rev at that time was F30 and i could not update past that. so i backed up that bios on to a usb and (using another pc) looked at the file. 
I noticed that it was named “F30_Bios”. 
i download the F32 bios file from the gigabyte website, extracted it, renamed the bios file (NOT FOLDER) to “F32_Bios” and tried to update bios then and it worked. 
 

after that still got the same issue.

then i tried the reported fix. Which was to update bios to F32, which i did, and ALL the following updates including

f40

f41

f50

f51

f60

f61

f62

f63a

f63

f65

had to do them one by one which took me 1hour 30 mins. 
 

but in the end it fixed the problem so i say it was worth it. 
 

Note:
i did NOT install the “EC FW Update tool” that was suggested to do in the description of the F40 bios update(image attached). 
i found out online that this was causing weird issue for ppl so i left it. This affects 3rd gen ryzen users and me, having a 2600x, was safe from this issue. Anyone with 3rd gen ryzen might wanna take caution. 
 

i will update yall in a weeks time for if it hold up and all
 

IMG_2971.jpeg

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×