Windows Bluescreen after Updating BIOS

Associate
Joined
30 Jun 2012
Posts
199
Location
Village of Hessle, Hull
Ok so i decided to update my bios and downloaded the latest version from Gigabyte. Old version: FA new: FD.

It was my first attempt at updating BIOS. I downloaded it and @BIOS selected to update from file and selected the new bios file. After it had finished updating I rebooted to find Missing OS. After a quick google search i found that all i had to do was select Raid again in bios. However when starting windows shows up after 10ish seconds a BSOD appears for a split second.

Any help?

MOBO: GA-870A-UD3
RAM: Kingston Value Ram 1333mhz
CPU: AMD Phenom II x4 965 Black Edition

*Update* After some google searches i found i should load failsafe defaults in bios this didn't help same blue screen. I also found that under standard CMOS features my HDDs are not showing up . Used to be IDE Channel 0 Master and 1 Slave. All that show now are my DVD Drives and yet on boot up it finds my raid setup.
 
Last edited:
Flashing the BIOS has most likely wiped all the settings and you have now loaded the defaults, so that will of as well. So you probably just need to go back through all the options and double check them.

As you have loaded fail safe defaults it is unlikely that it'll be much to do with any kind of CPU or MEM overclock settings (but check them all anyway), it's probably more to do with some piece of hardware being enabled/disabled that wasn't before, or some usage setting such as the RAID setting you mentioned earlier for your storage, or similar on another device.

Does the BSOD stay up long enough for you to see what the error is?

Can you get into safe mode and check the event logs to try and see how far into the boot process it gets? Check the last few entries in each log from when it blue screens.

If you can get into safe mode and can't read the BSOD from earlier as it reboots too quickly change the setting in safe mode so that it doesn't reboot on error.

Looks like your mobo has Qflash, so try re flashing the BIOS with that instead.

Also looks like it supports dual BIOS, so see if you can still boot to Windows ok on the backup BIOS. But I wouldn't be tempted to flash the backup BIOS with out fixing the other first encase you end up not being able to boot from either.
 
Thanks for the quick reply, The error does not stay up long enough for me to read it and upon trying to boot up into safe mode I still get the BSOD. Tried using Qflash but upon selecting update bios from drive i get No Drive found.
 
Are you using a fat16/fat32 formatted USB stick?
As that is what is normally needed and to be safe just put the bios file on it on it's own in the root of the drive. Also try it in different USB slots from a cold boot.

You could also try clearing the CMOS and loading default settings again. Manual will show how to do this on your board.

You could try a boot CD like Hiren's or UBCD4WIN and if you can get one of those to boot up you should be able view the event logs or copy them off to view elsewhere. You should also be able to edit the registry to change the reboot on blue screen setting. But it depends how comfortable you are with doing that.
 
Just reflashed using Qflash corrected BIOS Settings. Again when on Starting windows it BSODs but this time it did it within a 2 second time frame not the old 10 seconds : /. Il try using a boot CD and attempt to view the event logs.
 
Aha, when pressing F8 to get boot options there is the option: Disable Automatic Restart on system Failure will look at error log
 
Ok Error: A problem has been detected and Windows has been shut down to prevent damage to your computer.

If this is the first time blah blah blah

Check viruses etc.....

Technical Information:

***STOP: 0x0000007B (0xFFFFF880009A9928, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x000000000000000)
 
Apparently this error means windows is having trouble accessing the HDDs? Ive rechecked my Bios settings and all seems ok, I have flashed the bios back to it original setting and still no luck.
 
Used to be IDE Channel 0 Master and 1 Slave.

That's a bit funny, if you're using RAID isn't it? Anyway, if it detects your array (the 2x 750gb Seagates?) and gets to that point then should be fine BIOS/drive wise unless AHCI features anywhere in there?

Or have you got an SSD on top of the array, or another volume?
 
Last edited:
ok, so that is something to work from. How many drives you do have in the PC and how were they/should be set up?

You mentioned you had to select RAID, so if you are running a RAID volume have you checked the RAID BIOS settings?

And then check/change the HDD order.

It may just be that the drive order has changed in BIOS, so even though the boot drive seems to be correct it could be trying to load something that has been installed on a different drive that is now not where it expects it to be. Though I would've still expected safe mode to work.

Looks like you've googled that error already, so you'll see at least that there seems to be a lot of things you can look into.

Booting off the original install CD and doing a repair install might work, or an in place install/upgrade if really running out of ideas but I'd probably leave that for a bit and just concentrate on the BIOS for a while longer.
 
That's a bit funny, if you're using RAID isn't it? Anyway, if it detects your array (the 2x 750gb Seagates?) and gets to that point then should be fine BIOS/drive wise unless AHCI features anywhere in there?

Or have you got an SSD on top of the array, or another volume?
No SSD on the array or another volume.
 
I've Checked over the Raid Setup and everything seems ok to me. Shows Raid 0, 2 Drives what sata ports they are connected to etc. Going to try booting off the Original Install CD and doing a repair like you suggested.
 
Went through repair on Disk, had to load SATA Raid drivers for it to find the OS it did a system restore and same thing BSOD
 
Turns out I cannot access CMD On my windows disk. When i select the option to use repair utilities startup repair instantly kicks in and I can't stop it. Looks like i may have to look at a system reinstall. Well this will be the last time I try to update my BIOS -_-
 
Last edited:
I think swapping from IDE mode to AHCI usually causes a similar bsod, its finding the hard drives otherwise it wouldn't boot far enough to load an error. Maybe the bios updated the default drive setting from IDE to AHCI and it needs swapping back to IDE to make it boot?

I don't understand what setup you are using to boot from though, it's not very clear from the previous posts :( How many drives do you have? are they in a raid array? are you trying to boot from a raid array?
 
After Carefully looking and going through my manual on bios settings and re setting it up Windows finally boots successfully! The Problem had laid in my bios settings all along. Thanks for the help Guys :)
 
Back
Top Bottom