• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Win 7 Changed motherboard on OEM box) Blue screen ?

Markfw

Moderator Emeritus, Elite Member
OK, So a friend asked me to fix this box. The original OEM ECS motherboard, just over a year old, died, I ordered and installed a Gigabyte GA-G31m-S2C. It boots fine (sort of) and I get one of two screens. Tries to start win7, and bluescreens, or of after that I says auto system boot repair, it shows a graphics screen forever, then says it can;t auto-repair, and looking at the log its a driver issue.

DUH..... In XP, a change like this, you just put in the driver CD after it boots, install new drivers, and you are up after one more reboot. So with 7 ?????

Help. Not an idiot, except about win7 (see sig, I am a mod)
 
Hey Mark,

I'm just going to speculate but it is quite possible that on the way to original mobo finally dying it may have corrupted the OS installation so badly that it is beyond just a simple "fix/repair with the OS disc".

That said, I have personally never tried to upgrade a mobo without reinstalling the OS from scratch so I'm of little use to you in terms of giving you any insight into whether or not this is normal behavior for Win7.

I do use Win7 though, but it was a fresh install from XP when I upgraded to SSD.
 
DUH..... In XP, a change like this, you just put in the driver CD after it boots, install new drivers, and you are up after one more reboot. So with 7 ?????
You've been lucky. Many times, swapping a mobo out from under and XP install, results in bluescreens, and requires, at a minimum, a repair install ontop.

This time, with Win7, you were not so lucky. It's time for a re-install.
 
"and looking at the log its a driver issue."

That would tell me the fix is drivers, not a re-install.

So the question is, how can I install drivers without being booted ?
 
It has nothing to do with XP or Win 7.

When you did exchange like this before you where lucky that the chipset were probably close enough and the generic Chipset's drivers installed and adjusted to the new system.

This time you had No such luck.

The regular process to ensure success in motherboards transitions is to Backup with software like Acronis TrueImage Universal Backup.

Then Ghost back the backup.

The Acronis Universal Restore has the capacity to adjust to the new Chipset.

😎
 
This computer belongs to an 80 year old friend, or a friend of mine. The friend is paying for the hardware, I am doing the hardware fix, and was going to try and do the drivers. I have no software disk. This is OEM. (emachines) Also, if I put my P35 board in there, it boots all the way to the login screen, but with the G31, it bluescreens.

As for being lucky with motherboard swaps, I guess I should buy lottery tickets. With XP, I have done literally hundreds, and I can't think of one where a re-install was required (however, a few did require a repair install, usually when changing from IDE to sata or back)
 
DUH..... In XP, a change like this, you just put in the driver CD after it boots, install new drivers, and you are up after one more reboot. So with 7 ?????......With XP, I have done literally hundreds, and I can't think of one where a re-install was required

Done tens of thousands, and Windows 2000, XP and Vista / Win7 are all pretty much identical in this respect. If your storage controller can't be loaded from the system registry hive, the box will BSOD. It's been this way since NT4. Only to get around it is boot from a removeable storage controller like a RAID card, and then move the card to a new PC. I've had limited succes with post image tools like Acronis fiddling with the registry.

Oddly, moving from Intel chipset drivers to Nforce won't cause a problem (or the other way around). You can forget VIA to Nforce though, or even Intel to a newer Intel chipset.

Win98 allowed you to get away with this because windows could use a universal IDE driver and get you started. Hell, you could build a Win98 image on a laptop and ghost it to workstations and it would fire up.

You need to stay within a chipset family to insure the OS will boot on a different board. I'm not a huge expert on Win 7, but I don't think this baheviour will change.

My suggestion would be to get a MB with the same chipset, or punt, get a new HD, install Win7 on the new drive, and migrate his data. If somebody knows a way around this with Win 7 do explain.
 
Last edited:
@Mark

My experience is exactly the opposite I rarely managed to get a clean switch of Motherboard with Win XP, and I get a lot of success with Win 7.

I switched few months ago between P35 to G31 no problems with the same HD loaded with Win7 Ultimate.

Objectively there is a reason that win 7 does it better. I.e., Microsoft made it its business to include more inf files in the core system files, and make sure that there is better transitions with Win7 than it use to be with Win XP.

That brings us back to the Luck factor.
beer-wink.gif



😎
 
Last edited:
Done tens of thousands, and Windows 2000, XP and Vista / Win7 are all pretty much identical in this respect. If your storage controller can't be loaded from the system registry hive, the box will BSOD.

I've done millions if not billions of motherboard swaps. Top that. 😉
 
It really does depend a lot on the chipset. Sounds like you need a clean install.
 
@Mark

My experience is exactly the opposite I rarely managed to get a clean switch of Motherboard with Win XP, and I get a lot of success with Win 7.

I switched few months ago between P35 to G31 no problems with the same HD loaded with Win7 Ultimate.

Objectively there is a reason that win 7 does it better. I.e., Microsoft made it its business to include more inf files in the core system files, and make sure that there is better transitions with Win7 than it use to be with Win XP.

That brings us back to the Luck factor.
beer-wink.gif



😎

The old one is a mcp73vt-pm (GeForce7050 / 610i (MCP73V) and if I use my p35 chipset dq6, it will boot to the login window, but if I use the new board that fits the case, the G31 chipset, then it bsods. Could I boot the P35, and will it let me install g31 drivers ?? Then swap motherboards to the g31 ?

And I did get my friend to get the win7 disk from her friend. Is there a repair install for win7 like XP ?
 
Intel has the inclusive Chipset packages.

Try to boot the P35 and install the latest inclusive drivers that you can find on Intel site, it might add the chipset's drivers to the inf pool.

You can also try to unpack the Drivers onto a flash drive.

Then boot the current G31 from the Win 7 install DVD some where in the process you can choose repair and ad the drivers form the flash drive.

Probability of success Not very high.

---------------------

If you still have the P35 functional install.

Get True Image Home 2011 Plus, http://www.newegg.com/Product/Produc...-024-_-Product

Install the TrueImage plus on a good computer and make a Boot CD of it (it is part of the programs tools),

Back up with the TrueImage Boot CD the P35 onto External drive.

Then Boot the G31 with the Acronis CD and Recover the P35 image using the Plus option onto the G31 HD.

If you have a network you can BackUp and recover the image using a networked computer rather than an external drive.

If every thing that you have now is still OK (no corruptions) you have 99% probability that in less than an hour (depending on the sizes of the HDs) you will have a functional G31 computer.


😎
 
Unless you uninstall all of the old mobo drivers before hand and do a very very good job of cleaning up the mess it leaves behind, swapping out a mobo will break your Windows install almost every time.
 
Back
Top