• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

New hardware - BSOD

Y

YoMoma

Limp Gawd
Joined
Jun 21, 2005
Messages
201
Ok folks you can see my old hardware setup in my sig.
I've essentially overhauled my PC components with all new/current standard components, but my 1TB Samsung Spinpoint hard drive was reformatted a month ago. So it currently has Win 7 Pro installed and all the rest of components are new.
Here are my new components...
1 Asus Maximus VI Hero Mobo
2 Intel Core I7 4770K LGA1150
3 EVGA GEForce GTX 760
4 PC Power and Cooling Silencer Mark III 850 watt power supply
5 Corsair Vengeance LP DDR3 16 GB SKU- CML16GX3M2A1600C10B
6 new cheap optical drive.
Aftermarket CPU cooler and new PC case.
Both drives are using Sata 6GB ports on the mobo.

Problem is (keeping in mind the use of my formatted hard drive) I was expecting to plug and play all this hardware and just needing new drivers for the new equip.
Well, when The PC starts to load windows, 2 seconds into loading I get a BSOD. I've even tried to reformat by setting optical drive as the 1st boot drive and I got as far as inputting my Microsoft code in., then BSOD.
I've looked up the error code on my BSOD and seen a few comments from others that they said old drivers were conflicting with the new hardware.
I'm posting the error code here in hopes someone can help. I've been dealing with this prob for over a week now.

Error code - 0x0000007B (0xFFFFF880009A97E8, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)

Sorry if this is the wrong place for this post, but I can't find a better relevant forum on this site.
Thanks for any help.
 
My obligatory rant of seeing something not done correctly: You should always do a clean install of Windows when changing the motherboard from one model to another (swapping for an identical board is OK). Some people here will tell you it's not necessary, but I think it's a bad idea. There's no scenario where not reinstalling is superior to reinstalling.

If you insist on doing it this way, I can say I'm almost certain the blue screen has to do with the storage controller. Go into the BIOS and change storage controller to IDE. That should at least get the system to boot. At that point you can try using one of the various registry edits or other methods to change back to AHCI.

After you're back in Windows, reinstall all the new drivers. Once that's done, follow this guide and delete all of the grayed out devices that are no longer in the system (there will be a lot, probably 20-30 things).

If you used a tool (restore to different hardware or P2V) you can swap the motherboard and it should work. But if you don't use a tool, you should clean install. When you think about all the work that's necessary to swap without reinstalling, wouldn't it just be easier to reinstall and do it right?
 
Last edited:
this is a terrible way to do things, you should RE-install windows or you are opening yourself up for issues in the future. If it was a similar chipset MAYBE it would be ok, but your coming from a 3 series board. CMON MAN
 
I got no problem with a reinstall, I've even tried to but once I put my Microsoft code in and windows tries to start/install I get the blue screen again.
I could maybe make up a bootable USB drive or possibly take out my hard drive and install into a different PC, try to install windows then throw it back in my PC?
Should be some way of doing this without having to resort to buying a new unformatted harddrive.
But wouldn't I run into the same set of problems if I took out the drive and place into my bro's PC to install windows onto it?
 
YoMoma said:
I got no problem with a reinstall, I've even tried to but once I put my Microsoft code in and windows tries to start/install I get the blue screen again.
I could maybe make up a bootable USB drive or possibly take out my hard drive and install into a different PC, try to install windows then throw it back in my PC?
Should be some way of doing this without having to resort to buying a new unformatted harddrive.
But wouldn't I run into the same set of problems if I took out the drive and place into my bro's PC to install windows onto it?
Click to expand...
You don't have to wipe the drive. You could shrink the partition, create a new partition, then move the data you want saved to the second partition. Then when you reinstall Windows, only delete the first two partitions while leaving the 3rd intact. But of course, having a spare drive to back up to should be what you do. If you don't, burn stuff you want saved to a DVD (that's what I used to do before I could buy extra drives).
 
I've got my sh*t backed up to a external hard drive.
Just ready to reformat now.
Main problem is why I get blue screen trying to install windows from my DVD drive.
 
YoMoma said:
I've got my sh*t backed up to a external hard drive.
Just ready to reformat now.
Main problem is why I get blue screen trying to install windows from my DVD drive.
Click to expand...
Download Memtest86+ and run that a couple passes to see if there's a memory issue. Even brand new, memory could be at fault.

Also, did you check the controller mode in bios? Is it set to AHCI?
 
bigdogchris said:
Download Memtest86+ and run that a couple passes to see if there's a memory issue. Even brand new, memory could be at fault.

Also, did you check the controller mode in bios? Is it set to AHCI?
Click to expand...

I believe the controller is set to AHCI.
Is it possible to run mem test even if I can't get to windows?
 
Haven't made the boot disk yet but I did swap around my 2 dimms, used one at a time in different slots with no change in the blue screen
 
Try without controller on AHCI. If you did your setup non-ahci it will bluescreen on boot.
 
The error code "0x0000007B" is indicating a HDD access issue.
Try another Sata cable, another sata port, make sure its not set to Raid in the BIOS someplace and just AHCI,
 
dbwillis said:
The error code "0x0000007B" is indicating a HDD access issue.
Try another Sata cable, another sata port, make sure its not set to Raid in the BIOS someplace and just AHCI,
Click to expand...

Yes trying to boot ahci on a non-ahci setup would give you that ;)
 
That's exactly what was going on. I didn't realize if a hard drive is formatted in IDE that it will stay that way unless you use a registry hack or reformatt. My drive was last formatted while connected to the old Mobo via IDE cable. My new Mobo does not have such a connection. This is why I didn't check this setting earlier.
Going to reformat today. Should I leave it on IDE or do I need to use AHCI?
Not planning on using a SSD just yet.
 
YoMoma said:
That's exactly what was going on. I didn't realize if a hard drive is formatted in IDE that it will stay that way unless you use a registry hack or reformatt. My drive was last formatted while connected to the old Mobo via IDE cable. My new Mobo does not have such a connection. This is why I didn't check this setting earlier.
Going to reformat today. Should I leave it on IDE or do I need to use AHCI?
Not planning on using a SSD just yet.
Click to expand...

You don't need to reformat the ide/ahci is an OS issue. Your OS now boots using IDE and crashes when AHCI is activated.

But best bet is to reinstall your OS using ahci from the get-go. Sometimes registry change + reboot/setting bios back to ahci on next boot is all it takes YMMV.
 
You must log in or register to reply here.
Back
Top