Originally posted by: Smilin
You'll have to forgive me a bit. I never deal with the home version of XP but this should all apply anyway:
You can do a "repair" of the current installation. This will swap out all the files in your windows\system32 folder with ones from your original CD but leave all subfolders alone which preserves your registry, start menu etc. You'll have to re-run all service packs and critical hotfixes and in rare circumstances it can cause some problems especially if some other software like CD-burning software has changed a system32 file.
It would be nicer to actually find out what that bugcheck is and just fix it. If you can get the bugcheck info I can tell you what to do.
To get a bugcheck you can do one of several things:
1. Do a parallel install...just do a full install from CD but specify a folder other that C:\windows (Yes it's safe to do in the same partition). Boot to the new install, open the system hive from the damaged registry (C:\windows\system32\config\system) with regedit and change HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl\AutoReboot to 0x00000000 then reboot to the damaged install and wait for the bluescreen. Post the first 4 lines here in the forum.
2. Use the recovery console (boot with a 2000 CD/XP Pro CD to get there) and grab the most recent file from c:\windows\minidump. The file is 64k and should fit on a floppy so you can email it. Private message me for the address.
Something you might want to check: boot to a recovery console and see if you have write permissions to the root of C: ...just rename a file and then back again to check. This is a pretty common bugcheck that occurs at the portion of boot you are describing. If you were able to successfully copy over ntldr and ntdetect this probably won't apply though.
Just a word of warning to all you folks out there:
Don't use FIXMBR or Fdisk /mbr casually on a damaged drive. If you are missing the end of sector marker on sector 0 and you run one of these you'll just notice a lot of disk activity as it zero's out every byte on your drive! It takes rare circumstances but it can happen.
Satoshi, If you have a free Microsoft support incident that came with your OS now would be a good time to use it. I'm not sure what the hold times are like for the home users but once you get through they'll stay with you until it's fixed.
If you can get to that stop code or get me a copy of a memory dump I can get you working. If not, the repair mentioned above is a reasonably good route to take...if it works in "home".
Smilin
