Took an old HD out of a clients machine, and replaced MB, memory, CPU, etc. Now, as soon as i get past the POST and before windows loads up I receive the Windows troublehooting screen (safemode, safe mode w/ networking, last good) as soon as I select an option the computer reboots. Switched the HD with a fresh one and was able to boot fine. Was wondering if there was a way to fix my clients HD without formatting the information. Am running WinXP home edition.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Windows Reboots
- Thread starter RangerRip
- Start date
When the hard drive that is suspect is in a machine you could try running ChkDsk /r from the Recovery Console and see if that can fix any problems.
HOW TO: Install and Use the Recovery Console for Windows XP (Q307654)
You could also have a look at the FixMbr command while there.
Your hard drive manufacturer will have free diagnostic software capable of thoroughly testing the suspect drive. This software will run from a bootable floppy.
HOW TO: Install and Use the Recovery Console for Windows XP (Q307654)
You could also have a look at the FixMbr command while there.
Your hard drive manufacturer will have free diagnostic software capable of thoroughly testing the suspect drive. This software will run from a bootable floppy.
could it be as simple that something about the new hardware/old drivers is preventing xp from finishing booting so that it can redetect devices?
maybe if you yank the drive, put into another pc (or use recovery console) and manually restore the default system hive, it will boot and run plug and play detection?
see this (despite not getting the systemCED error, this can be used to restore the default hive):
look for the "restore default hive" section. This is a different way of approaching the ms-kb link bcastner provided about migrating to new hardware. Not sure if my suggestion is a good resolution to the problem or not, however.
one other issue comes to mind: does XPhome's hardware change re-activation issue come up in this scenario? I would believe you would probably have to reactivate XP if the hardware changes were significant enough...
maybe if you yank the drive, put into another pc (or use recovery console) and manually restore the default system hive, it will boot and run plug and play detection?
see this (despite not getting the systemCED error, this can be used to restore the default hive):
look for the "restore default hive" section. This is a different way of approaching the ms-kb link bcastner provided about migrating to new hardware. Not sure if my suggestion is a good resolution to the problem or not, however.
one other issue comes to mind: does XPhome's hardware change re-activation issue come up in this scenario? I would believe you would probably have to reactivate XP if the hardware changes were significant enough...
- Status
Similar threads
