AMD to Intel, what did I do wrong?

[GnatGoSplat]

I had an AMD Sempron 64 2600+ socket 754 on an nForce4 4x motherboard (Asus K8N4-E Deluxe).

I replaced the motherboard with an Intel Core 2 Duo E4300 (oc'd to 2.4GHz) on a Foxconn G9657MA motherboard. G965 chipset.

I had Vista Ultimate installed on the AMD board and did NOT want to reinstall the OS and all my apps. However, the G965 board absolutely refused to boot. I got a BSOD right away. Vista DVD could not repair my installation, the automated repair process said the problem was caused by a driver. Here is everything I tried:

1. Removed ALL nVidia drivers.
2. Made sure HD drivers were the "Standard Dual Channel IDE" Microsoft drivers.
3. Made sure VGA was "Standard VGA Controller".
4. I even uninstalled apps that seem to install drivers, like Acronis and VMWare.
5. Tried uninstalling anything referring to AMD in Device Manager.

No matter what, it kept doing a BSOD.

I am aware a clean install is always best, but I am stubborn and have not had this kind of trouble swapping motherboards in the past. I once went from ViA K8T800 to nVidia 430 on Windows 2003 that did the exact same thing, but removing all the ViA drivers and changing everything to the standard Microsoft drivers allowed me to boot with the new chips and everything was fine. I've also gone from WinXP on a ATI XPress200 to nVidia 6150SE before and that was just a simple matter of uninstalling ATI drivers, booting with the nVidia board, and installing nVidia drivers. nVidia to Intel for some reason seems especially difficult.

I am just asking for future reference. I DID end up backing up my documents and doing a clean install... and a month later, I STILL do not have the machine back to the way it was. :frown: I really don't enjoy clean installs no matter how much people recommend them.

 

[f4phantom2500]

if you don't want to do a clean install then you should be prepared to deal with their inherent problems, which is why i, and others, recommend them. i always reinstall whenever i change out a motherboard or a hard drive (assuming the new drive will be my boot drive of course; i won't just back up the old drive to the new one).

 

[covert24]

bad decision as this only works when changing out the mobo of the same socket architecture and not the CPU also. Just reinstall dude and stop trying to beat around the bush.

 

[VirtualLarry]

I had a similar problem going from an Athlon XP2000+ on a KT400 mobo, to an Intel E4400 on an 865PE mobo. Only my problem was different, no BSOD, just a total refusal to boot, wouldn't load the 2nd-stage bootloader. This was for W2K SP2 and XP SP1 both. I had to do a repair install with both of them, but it worked in the end. Don't know why Vista wouldn't do the same for you.

 

[postmortemIA]

uniprocessor to dualprocessor without re installation= very bad

First, your HAL driver won't get changed, and with old one you won't get far.