I just upgraded mobo & cpu and now I can't get into windows

[BMdoobieW]

I just upgraded to a 2100+ and an EP-8RDA. My old config is my rig linked in my sig. I put the new mobo and cpu and hsf in and put my vid card and my promise ata133 card and other pci cards all back in to, but not necesarily in the same physical order as they were. I also added a 3rd hard drive and took out a cdrom drive. I turned on the computer, went into the bios, messed around in there, rebooted, got to the point where WindowsXP Pro would start loading and then it shut off and rebooted. This time when it got to the point where windows loads, it gave me a msg about windows didn't boot properly last time and to choose an option, but i can't choose anything other than normal boot because my keyboard won't resond. Anyhow, the countdown goes down to zero and then nothing happens. I rebooted a bunch of times. The first two times, after the coundown got to zero, something would happen, i'd get a BSOD for a split second, and then it woudl reboot. Now, as i wrote above, nothing happens when the count get to down to zero. Can anyone help me? (I'm writing from my laptop). Thanks!

 

[sgopal2]

I have a feeling that the XP anti-piracy "feature" just kicked in for you. Since you changed to a new CPU, XP automatically realized that something had changed.

I have no idea why it won't boot though........try taking out the extra HD and see if that helps. Otherwise you may have to reinstall XP.

 

[BMdoobieW]

Originally posted by: sgopal2
I have a feeling that the XP anti-piracy "feature" just kicked in for you. Since you changed to a new CPU, XP automatically realized that something had changed.

I have no idea why it won't boot though........try taking out the extra HD and see if that helps. Otherwise you may have to reinstall XP.

I disconnected the new hd and it didn't help. In theory, if I reinstalled my old mobo and put everything back the way it was hardware wise, do you think I'll be able to get into windows?

 

[Zepper]

It should work if you go back to the way it was, slot order and all. But no guarantees. This is a real PITA for people that play with their hardware. MS can keep XP. MS should have a paper in their knowledge base by now to tell people how to do this sort of thing. Go look for it.

.bh.
:frown:

 

[DAPUNISHER]

Try booting from the XP CD and running the recovery console, then run fixboot, and if needed fixMBR, I always run chkdsk too for good measure, HTH

 

[amdskip]

Originally posted by: DAPUNISHER
Try booting from the XP CD and running the recovery console, then run fixboot, and if needed fixMBR, I always run chkdsk too for good measure, HTH

Yeah, this is exactly what you need to do.

 

[SandLizard]

correct me if i'm wrong, but did you reinstall winXP?

i've been able to get windows to load before with a switch of a motherboard (without reinstalling), but it usually causes problems and grief that you do not want. i suggest backing up 'n' reinstalling. I was able to get the computer i'm working on into windows without failure, but in my experience, things just don't run that well (of course, i'm running win98 here...)

maybe with the newer versions of win this isn't a problem?

 

[Horsepower]

When I upgraded my mobo and cpu, I had to reinstall XP. Then when I went to register it showed an 800 number. I called it and they gave me an override.

 

[BMdoobieW]

Originally posted by: DAPUNISHER
Try booting from the XP CD and running the recovery console, then run fixboot, and if needed fixMBR, I always run chkdsk too for good measure, HTH

Ok, I'll try that. If that doesn't work, I'll install XP onto that new hard drive I have, move all my files off my current boot drive, format it, and then reinstall XP back where it should be.

Everyone who responded to my cry for help, thank you!

 

[DAPUNISHER]

Well from everything I've read and tried, and since you've changed to a different chipset that requires different drivers I think the course of action you plan is best. Just do a fresh install on the new HDD and use the import files and folders wizard to get what you need of the old drive then whipe and re-install XP on the old drive if you want an OS on it again. Evidently the deleting the Enum key trick doesn't work very well or often with NT based OS's, You've already tried the do nothing approach of just letting XP detect and install everything itself without success, It's too late to attempt any of the methods from inside windows unless the fixboot, fixMBR work and then, as was stated, it'll most likely force you to re-activate, and the Sysprep tool doesn't resolve problems with hardware changes according to MS technet.