URGENT: Mobo BIOS updated giving BSOD (after replacing mobo & cpu)

lfhalppst

Reputable
Jan 28, 2015
5
0
4,510
I replaced my mobo and cpu then, as per the instructions on the mobo's user guide, I used the USB Bios Flashback utility. (I would have just used the included DVD, but I realized after the hardware changes that my disc drive wasn't compatible so I wasn't able to connect it.) The instructions indicated that if the lights flashed a specific way then it meant the BIOS Flashback was not operating properly, which didn't happen so I assumed it was done right.

When I tried booting for the first time, I got a blue screen with the following:

0x0000007B 0xFFFFF880009A9928, 0xFFFFFFFFC0000034, 0x0000000000000000

When I restarted, it suggested I try System Repair, but that didn't resolve the issue. I've also tried the following so far, all from suggestions on other threads:

- Checking if the USB is in NTFS mode since I read it shouldn't be (I saw it's listed as FAT so I take that as a no...?)
- Checking to make sure SATA controller is set to ACHI or ACPI mode (it was)
- Checking if the bios version was the latest one (it was the newest one listed under Bios here http://www.asus.com/us/Motherboards/M5A97_R20/HelpDesk_Download/ )
- Loading default settings in the BIOS menu

The issue is it's failing to boot and I keep getting a bsod.

I realize I probably should have just attempted to turn on the computer before updating BIOS, but I had been just following the guidebook and thought it would be easier that way... : / Any ideas? I'm pressed for time and need my machine running for daily commitments.

Details:

Asus M5A97R2.0
AMD FX 6300
Win7 64bit
 

RealBeast

Titan
Moderator
You may need to do a clean reinstall if the motherboard is significantly different from your original board. The bios update is unlikely to be the cause of your problem if you have set all of the bios settings to what they were prior to the update.

Try doing a safe mode startup to see if the minimal drivers loaded allow you to get started without a BSOD.

What was your old board model?
 

lfhalppst

Reputable
Jan 28, 2015
5
0
4,510


Gigabyte GA-770TA-UD3 (Socket M2) was the old one.

For some reason I'm not getting the option to start in safe mode. I get a Windows Error Recovery black page with only two options: Launch Startup Repair or Start Windows Normally (which leads to the same bsod). Not sure what I'm doing wrong. If it helps, the steps I took were to tap F8 hoping to get Advanced Boot Options > Safe Mode, which I didn't. I was asked to Select Boot Device, chose my hdd, then got the black page mentioned above.
 

RealBeast

Titan
Moderator
If you cannot get to safe mode by holding F8 and then selecting safe mode, you should go ahead and do a clean install now.

If you have data that is not backed up elsewhere that you need, you can try to access it by using a Live Linux that will run on a USB stick or CD like Puppy. The other option would be to install Windows to a different disk drive and then attach the current drive after the install and get the data off then.

Since you cannot boot, you cannot do just a repair install.
 

lfhalppst

Reputable
Jan 28, 2015
5
0
4,510


Thanks so much for your help so far.

Luckily the one thing I did right was back up everything onto my external before I changed anything so I can get started with a clean install immediately. I'm currently waiting on the installation files to finish loading onto a USB stick. I figured since I'm starting fresh it would be a good opportunity to just go for Windows 8.1 instead of Windows 7 -- that shouldn't create additional problems, should it?

Will update this thread if anything changes. Thank you again.
 
bugcheck 0x7b is INACCESSIBLE_BOOT_DEVICE
if you just flashed your BIOS, check the mode that your SATA controller is in.
IDE or AHCI
the mode must be the same mode as when the drive was formated.
Often the defaults for older machines are IDE when you actually have them formated as AHCI. Just change it and do a reboot to see if you can boot.

if it is in the correct mode there are other causes of this error that are normal
and do not mean your drive failed. For example:

your devices may have been reassigned drive letters. It gets triggered when you add another device with a primary boot partition. The system guesses witch drive to put first. if it guesses wrong your actual windows image will be on a different drive than the default c: you would boot a repair image, and reassign the drive letters back to the correct settings. Often, it is just a matter of removing the drive letter assigned to what was a hidden partition.

for example you might have
drive c = small 200 mb partition
drive d= your large windows drive
you would go to your drive c, remove the letter assignment and then go to drive D, then assign it to drive C and reboot.

there are other ways to fix this using a repair disk and the command
bootrec.exe command
maybe take a look at this https://tweakhound.com/2012/11/13/how-to-fix-the-windows-bootloader/
 

RealBeast

Titan
Moderator
Sure if you want to upgrade to 8.1, now would be the time to do it. I would probably wait and use Windows 7 until Windows 10 is released in a complete form this summer or fall (the upgrade will be free from Windows 7 or8).

 

lfhalppst

Reputable
Jan 28, 2015
5
0
4,510
Running into another problem now. I tried re-installing, but when I went to switch the boot order to USB I found it wasn't an option. In other words, there was only 1 option and it looked like the hard drive. Tried plugging in the USB stick in other slots as well just in case and still didn't get picked up. This is what I had used: http://windows.microsoft.com/en-us/windows-8/create-reset-refresh-media Any ideas? I have both Windows 7 and Windows 8 on a different machine as ISO files so either way I don't particularly mind, just not sure where to go from here if the USB option isn't popping up in the boot menu.

EDIT: Okay weird... I tried again to see if the SATA options were causing issues, as per one of the posters suggested. Changed the setting, still couldn't boot. Changed back. This time the USB stick was recognized in the boot order options for some reason, which is strange because it's essentially the same as when I had tried changing the boot order earlier tonight. Anyways, installing Windows now and hopefully things will run smoothly now.
 

lfhalppst

Reputable
Jan 28, 2015
5
0
4,510


Hi and thank you for your input.

I don't know what mode it was in when the drive was formatted, sorry. :( I'll try changing it to other options and see if I can boot.

In regards to the second point, (possibly dumb question incoming) can that happen if you only have one drive? This machine hasn't had additional devices with a primary boot partition, as far as I know. Well, other than USB sticks used to update BIOS or install an OS but I assume that can't interfere when it's not actively connected...?
 
the default mode for the SATA controller can get changed when you do a BIOS update, older machines might use IDE mode while more current machines are more likely to use AHCI mode for the SATA.

I would just go to BIOS and try to boot under both modes and see if your machine can read the drive correctly in one or the other mode.

yes, you can also get the other problem with a one drive. When the drive is set up, it will make a small partition first and it will not assign a drive letter to it. Later if you do something to the drive the drive letters can automatically be reassigned.
this can make that small partition become drive c: and your DVD drive becomes drive D and your last windows partition would become drive E. Then when you boot, the BIOS will go to the first partition to get the boot loader, and read the file. The file tells the system to load windows from the C: drive but the actual files are now on the E: drive because of the drive letter reassignment.

most of the time you boot on a repair disk with command prompt and try to find where your files are actually at.
that is
run the command
dir C:
dir D:
dir e:
dir F:
and see if any of those drives are there and if one of them has windows on it.
if you can read the drive files then the SATA mode setting in the BIOS is set correctly
and you need to fix the drive letter assignment.