Updated BIOS, startup repair saying it can't fix the problem

Ian The Pineapple

Prominent
Jul 4, 2017
14
0
510
So I recently updated BIOS, thinking it was something you should keep updated every now and then (not sure if this is correct, I have seen some conflicting/vague sources.) The computer wouldn't boot so I reset CMOS. It POSTed, then Windows said it couldn't boot after a blue screen with a LOT of numbers flashed for half a second. It then said I could open windows normally, or it recommended using startup repair. So I used Startup Repair, and it restarted the system a few times now. It's been two hours, and after checking BIOS (it recognized both hard drives), I continued Startup Repair, and it now said it couldn't fix the problem. I'm thinking of using the installation disc for repairs.

Specs:
Intel i5 6500
MSI B150M Mortar (BIOS was updated to the most recent version for my board)
16 GB Corsair Vengeance RAM 2666mhz
WD Blue 1TB HDD
WD 320 GB HDD (not sure of the exact model, it's from an old Vista PC)
EVGA 430W PSU
GTX 1050ti

Thank you for the help!
 
Solution
The default Boot Mode after CMOS clear for that board is LEGACY + UEFI and the only other setting is UEFI only.

Another setting that could prevent booting is if Windows was installed as a 1-drive RAID under Integrated Peripherals, as changing to the default AHCI will cause a failure to boot (at least there's no IDE mode to worry about)
If a BIOS version is functioning properly - never update to a new version, unless you have a valid and compelling reason. The only time you should update is if a new BIOS version will support new hardware or become more stable, for example. You need a good reason to upgrade a BIOS because if you get a corrupted BIOS download or there is a power failure of any kind the BIOS update will fail and then your motherboard is toast, unless you can purchase a new BIOS separately, however, that is not always possible.

Often using the installation disk or the copy of Windows if you built a computer yourself, or if it is provided by a seller, will perform a proper repair.
 

Ian The Pineapple

Prominent
Jul 4, 2017
14
0
510
Thank you, I'll try the installation disc tomorrow.

The motherboard seems fine, BIOS boots up fine and it shows all my system components. I think I got lucky and only had an OS issue, I was worried my mobo died and may have taken hardware with it.

I will never again update BIOS without a solid reason, but sometimes we must learn the hard way.

EDIT: Is it possible that a broken BIOS could have killed a hard drive? I don't know if it happened but I have a lot of important stuff on my main drive, some of which hasn't yet been backed up.
 
A BIOS will not kill a hard drive. You may have to reset your BIOS. Enter BIOS and look for an option labeled something like this look for an option to "Restore Defaults" or "Load Fail-Safe Defaults".

Also, if Windows was installed with the BIOS set to UEFI you will have to enter BIOS and set the hard drive, or SSD to UEFI or Windows will most likely not boot.
 
The default Boot Mode after CMOS clear for that board is LEGACY + UEFI and the only other setting is UEFI only.

Another setting that could prevent booting is if Windows was installed as a 1-drive RAID under Integrated Peripherals, as changing to the default AHCI will cause a failure to boot (at least there's no IDE mode to worry about)
 
Solution

Ian The Pineapple

Prominent
Jul 4, 2017
14
0
510
So I decided to try unplugging my second hard drive, and the PC and Windows 10 booted up perfectly, everything is here.

My second hard drive has an old copy of Vista on it, should I delete the OS from that drive to prevent this in the future, or would that not work?

Thank you for the help, God bless!
 
Nope, just go into the BIOS after plugging it back in and change the boot order so the Windows 10 drive boots first. Even if you delete Vista but leave that drive as first to boot, Windows 10 will think it's on drive D and fail to boot just as before. Perhaps you installed Windows 10 with the Vista drive attached, as it should've booted right into Vista otherwise.