Windows XP Pro will not run after SP2 installed

[starwars7]

Hey guys, I recently installed SP2 for on Windows XP Pro (everything seemed to go fine and it asked me to go ahead and restart) and now the computer goes to BSOD after the windows logo comes with the blue bar running across the bottom.

I've got data on there that I'd like to save. And came up with one option:

I figure if I have to I can take out the hard drive and install it into another PC as a Slave, then hopefully I could gain access to the drive and copy the data.

Does that sound like it would work? Any other/better ideas on how to go about fixing this?

Thanks!

 

[dawks]

That will work fine, provided the second system is WinNT, Win2K, WinXP, or WinServer2K3, if your XP Pro system is using NTFS. And that the files were not encrypted with NTFS encryption (most likely they were not - just mentioning that).

Can you boot into safe mode? Hit F8 right after the BIOS screen, an choose Safe Mode, and the option to avoid any drivers and such.. If that works, you might be able to uninstall SP2 via Add/Remove.

 

[starwars7]

Originally posted by: dawks
That will work fine, provided the second system is WinNT, Win2K, WinXP, or WinServer2K3, if your XP Pro system is using NTFS. And that the files were not encrypted with NTFS encryption (most likely they were not - just mentioning that).

Can you boot into safe mode? Hit F8 right after the BIOS screen, an choose Safe Mode, and the option to avoid any drivers and such.. If that works, you might be able to uninstall SP2 via Add/Remove.

Thank you for the reply, I tried the F8 function and it did not allow me to start in safe mode. I did have the option of running off the CD Rom though.

The other PC is running Windows XP Home, anything that I should be careful about when I hook up the Pro HD to the other system? I know to adjust the jumpers, I just hope that the system boots into XP Home and doesn't try to boot off the XP Hard Drive.

 

[Evander]

I've had to do this before. Don't worry, it will boot your master c: drive before the slave d: drive unless for some very odd reason your bios is set differently (which you can adjust if need be).

But BEFORE do any formatting try the following, it saved my ass once. Normally xp has the system restore feature but since you cant enter safe mode here's the way how to manually restore. It might work for you, certainly worth a shot (a copy\paste of what a fellow atecher told me)
Go into the following folder:
C:\System Volume Information\_restore{71835D45-16FD-4262-BA4A-8B6C0540FEBD}\RP8\snapshot

(Yours may be RP55, for example, but the point is, go into that folder, to a recent restore point from when things worked - look at the dates - and file the SAM, software, security, and System files)

Go to c:\windows\system32\config and back up those 4 files into c:\windows\system32\config\backup.

Copy those four files from c:\system volume .... to c:\windows\ssytem32\config.

Find and rename all files that this patch changed on your system. We'll assume that's just the file it renamed as .original, so find out where it put the file and replace it with the original.

Reboot and let us know what happens. You're essentially putting a backup registry back into place. If the problem was with the registry, that will fix it.

 

[Fingolfin269]

Anything specific in the BSOD message? Have you tried to boot off of your CD to a command prompt and run a chkdsk?

 

[pontifex]

i had something similar. the error in my message pointed to my ram being bad (according to MS). took a\out the ram, put different in, diff. configs. nothing fixed it. i was able to uninstall SP2 by going into safe mode.

i'm not sure what fixed it in the end but i think it was conflicting drivers for my video card. i had some old nvidia drivers that i never uninstalled when i would upgrade to the newer ones. wiped those out and it worked after that.

 

[starwars7]

Originally posted by: Fingolfin269
Anything specific in the BSOD message? Have you tried to boot off of your CD to a command prompt and run a chkdsk?

I'm afraid that I can't actually write down the BSOD message, it only flashes for about a second.

I'm glad to hear that running the broken OS HD as a slave should allow me to gain access.

Evander: The suggestions you gave as far as going to those folders etc.... I'm guessing that I should do that to the Broken OS HD while I have it loaded as slave?

 

[Evander]

that's right. I recommend you get your files first, then give the procedure a shot (if you have no other options for restoring). also you'll probably find the sys vol folder is protected, see below to gain access:

Windows XP Professional using the NTFS File System on a Workgroup or Standalone Computer

In Windows Explorer click [Tools] [Folder Options]
Click the [View] tab, click [Show Hidden Files and Folders]
Clear [Hide protected operating system files (Recommended)] check box.
Click [Yes] on the change confirmation box and click [OK] to exit.
Right-click the System Volume Information folder in the root folder.
Click [Properties] and select the [Security] tab. Click [Add]
Enter the name of the user you are allowing access to the folder.
Click [OK], and then click [OK].
Double-click the System Volume Information folder to open.

 

[episodic]

I wouldn't install sp2 on a well used sp1 install. I've found it is a large headache 50% of the time. I would do a fresh slipstreamed install or simply update sp1 and leave it sp1 - I use sp1, and have not found any drawbacks.

 

[Cdubneeddeal]

Your system is screwed. I've had this happen twice now. Before you installed SP2, did you install something else that needed a restart? Were you doing anything on your computer at the time? Whether it be browsing, listening to music, anything. I've come to find out that SP2 installs are very touchy. Accessing the hard drive at all during the whole installation process cause corrupt installations everytime. Now I just disable my screensavers and let the install go about its merry way with no interruptions.