Changed motherboard on Vista 64-bit SP2 install. Anyway to repair the OS?

compudocs

[H]ard|Gawd
Joined
Oct 5, 2009
Messages
1,212
Okay, I just changed out the motherboard from a dead GF8200 AM2+ based motherboard to a 6150 based AM2+ motherboard and I need to find a way to fix the OS to make it boot.

The OS is Vista Home Premium 64-bit with Service Pack 2. Anyone have any clues?

The system is an HP m8530f and the mothebroard I'm trying to use is from a Gateway FX 7020.

===
===
===

I tried running the startup repair and it says that an issue was found that could not be resolved yet the report says all of the tests passed and that the OS booted.
Here is what I got after running the startup repair :

Problem event: startuprepairv2
Problem Signature 01: AutoFailover
Problem Signature 02: 6.0.6001.18000.6.0.6001.18000
Problem Signature 03: 6
Problem Signature 04: 393222
Problem Signature 05: 0xf4
Problem Signature 06: 0xf4
Problem Signature 07: 0
Problem Signature 08: 2
Problem Signature 09: WrpRepair
Problem Signature 10: 6.0.6001.2.1.0.256.1





I tried booting into safe-mode and debugging-mode and the system still BSOD's

The bios for the Gateway 6150 based mothebroard has no AHCI setting so I cannot tell if it's running in AHCI or not. It does see the Hd in the bios and in the Windows Vista setup.

I tried running the " sysprep /generalize " command thru CMD in the windows setup but it says the sysprep command is not recognized.


===
===
===

Realized I had to switch to the sysprep folder and launching sysprep using the following commands :

x:\windows\system32>c:
C:\>chdir windows\system32\sysprep
C:\windows\system32\sysprep>sysprep /generalize /oobe /reboot

This however did not work :(
 
Last edited:
Best bet is to just reformat. Or are you trying to get data off the old OS? If so I would use something like a linux live cd to grab whatever you need. Doing a repair install with Vista disk may work, not sure.
 
I'm trying to leave all of his programs intact as he said he really doesn't want to go through all of the hastle to get everything reinstalled and reconfigured.

If I can help get the machine up and running without a reload that would be ideal but if not I would like that to be a last resort.
 
same chipset? are the hdd settings the same between the 2?( ACHI for example?)

only time I had troubles is when I replaced a MB and it was accidently set to IDE instead of native mode for SATA...
 
Boot to the CD and select the advanced options, then repair and it will scan for issues preventing the OS from booting and repair them.

If that doesn't work, boot to a cmd prompt from the install CD and run a sysprep /generalize
 
If the SATA mode on the motherboard is different from the old one to the new one, that's likely the problem.

I've moved installs from AMD to Intel, Intel to AMD, Intel Core 2 to Intel i7, and AMD 959 Athlon x64 to AM3 generation Athlon x64. As long as the SATA mode was set correctly, all they had to do was boot to detect all the other hardware, and re-activate. Other than having to perform a couple of reboots to install new hardware and the subsequent re-activation, they went easy as pie.
 
K, tried all the suggestions to no avail. Added info to first post on what I've tried and info I got back from reports.
 
That's why you should sysprep before changing motherboards. Sure, most of the time, it will work without sysprep, but then again there is that one time...
 
That's why you should sysprep before changing motherboards. Sure, most of the time, it will work without sysprep, but then again there is that one time...

Replaced the old mothebroard because all the SATA ports died :( Not an option.

Didn't know I had to change to the windows\system32\sysprep folder to launch the sysprep command but still no go.
 
Last edited:
You can use Adaptive Restore in Paragon Backup 2010 to adjust an install to a new motherboard. It'll recreate the HAL, and inject new chipset drivers into an existing install.
 
Ugh, just reformat the damn thing. I'll never understand why people are so lazy that they just reinstall hardware/drivers on top of old hardware/drivers for years and years. Backup whatever is valuable to you, and just do a complete reformat. Do things right the first time. With all the time you're wasting on trying to get random things to work, you could have backed up and reformatted.
 
If it was me, I would probably be driven to fix it. Reformatting is not how a real man does things. A real man upgrades a Tandy 2000 and jams that 10MB hard drive with DOS 5.0 installed into a new Lian-Li along with a 5870 and a 1000W Corsair PSU.

Actually, a real man just syspreps it.
 
If it was my computer I would try to fix it by any means necesary first then if al else fails reload it. Sadly, this is not my system and reloading is really not an option I was given unless the OS cannot be repaired.

For $50 Paragon is worth a shot. $50 will be well worth the time saved in the futyure with all the other vista install I can repair instead of reloading :) Basically pays for itself.
 
When changing the motherboard to a different model, best thing to do is reinstall the OS, this goes for any operating system even linux.

I suggest you load up a linux live cd, copy as much information onto an external drive, and then format/install.

If you don't want to do that, then buy the same exact model, but since it looks like you've made changes, your best bet is to copy data/formate/install.

EDIT:
A real man would have been prepared by backing up his data and expecting to reinstall, or have bought the same exact model motherboard. Haha.
 
EDIT:
A real man would have been prepared by backing up his data and expecting to reinstall, or have bought the same exact model motherboard. Haha.


On the first point. My friend is a bit, how do you say . . retarted? Told him this many many manymanymanymany times. On the second point, are you really willing to pay $100 + for an OEM motherboard when you are offered a way cheaper way out? Also, where the hell is the fun in that?
 
Back
Top