XP Home Boot Loop

[i2omani]

I would like to ask if someone had a boot loop issue with Home XP...How did you fix it?


I am running into this and i can't figure it out, and i don't want to do Repair install because I am not sure which SP the computer is running, as I have XP Home SP2 CD!

I ran into this before and when i used my SP2 CD to do the repair, I was not able to active it with COA, because it turns out the it was SP1....thats what M$ told me! any help please will be appreciated.

P.s: it will not go to safe mode, will not go to last known

 

[abe]

Hi
first get the computer to stop bootlooping using the instruction found in a great website i found called technibble

http://www.technibble.com/how-to-di...r-bsod-if-you-are-unable-to-get-into-windows/

once you have done that and can see the bsod stop code post here for more help ir use google to try fixing it.

Abe

it may be something simple to fix using chkdsk or similar

 

[Pc Fixed Right]

you can always use a live cd to figure out what service pack the computer is running.

 

[purple_minion]

Is this really any issue? I mean the service pack and a repair install? I would assume the wrong version like using a pro cd instead of home or something, but you need the right service pack? I just recently did a sfc /scannow that replaced some files and it hasn't complained yet. I'm microsoft genuinely interested as this would put a kink in computer repairs. (That was a bad joke I admit)

 

[TimeCode]

Is this really any issue? I mean the service pack and a repair install? I would assume the wrong version like using a pro cd instead of home or something, but you need the right service pack?

This is absolutely an issue. I've had repair installs go horrible wrong because of a wrong service pack or even too many updates within the SAME service pack. I don't even do repairs anymore because I've had too many issues.

 

[Chris]

I run into this issue quite frequently. I have found the following to be very effective:

1. Run recovery console off the XP CD (it doesn't seem to matter which version or service pack).
2. Run FIXBOOT.
3. Run CHKDSK /R.
4. Run FIXBOOT again for good measure.

Then reboot the system. The OS might scan the hard disk, and if it does let it. It should then start with no problem. Hope this helps.

 

[usacvlr]

you can also use the winubcd to replace the registry with an earlier snapshot

 

[purple_minion]

This is absolutely an issue. I've had repair installs go horrible wrong because of a wrong service pack or even too many updates within the SAME service pack. I don't even do repairs anymore because I've had too many issues.

Well, I never heard anyone mention that on here. Does that mean you need to keep a million cd's then for each version/service pack? How do you do it.

 

[i2omani]

0x00000024(0x00190203,0x8337B008,0xC0000102,0x00000000)

0x24 is related to ntfs.sys

using liveCD rename the %SystemRoot%\System32\Drivers\Ntfs.sys file to Ntfs.old, and then shut down the computer (this action prevents the Ntfs.sys driver from loading).

Restart the computer, and then run the following command on the corrupted NTFS volume:
chkdsk driveletter: /f

After you use the Chkdsk tool to repair the corrupted NTFS volume, rename %SystemRoot%\System32\Drivers\Ntfs.old to Ntfs.sys, and then shut down and restart the computer.

*Will try this and let you know what happed!

if anyone got a different route, please let me know.

 

[abe]

0x00000024(0x00190203,0x8337B008,0xC0000102,0x00000000)

0x24 is related to ntfs.sys

using liveCD rename the %SystemRoot%\System32\Drivers\Ntfs.sys file to Ntfs.old, and then shut down the computer (this action prevents the Ntfs.sys driver from loading).

Restart the computer, and then run the following command on the corrupted NTFS volume:
chkdsk driveletter: /f

After you use the Chkdsk tool to repair the corrupted NTFS volume, rename %SystemRoot%\System32\Drivers\Ntfs.old to Ntfs.sys, and then shut down and restart the computer.

*Will try this and let you know what happed!

if anyone got a different route, please let me know.

why not use the xp disk to get to recovery console and run chkdsk fromthere.

Abe

 

[purple_minion]

why not use the xp disk to get to recovery console and run chkdsk fromthere.

Abe

Or UBCD and run it on the drive. What is the source of this advice he's going to follow?

 

[abe]

Or UBCD and run it on the drive. What is the source of this advice he's going to follow?

its an old microsoft article that was quoted on yahoo answers.

Abe

 

[TimeCode]

Well, I never heard anyone mention that on here. Does that mean you need to keep a million cd's then for each version/service pack? How do you do it.

First I try to fix it through UBCD4Win, then I pull out ReImage. If after those 2 it still doesn't work, it is a copy and nuke scenario. Of the probably 15 times I've used ReImage, it has only failed 1 time and it has NEVER made the system worse. I can't say the same for the repair install though. It has thoroughly trashed systems before.

 

[i2omani]

tried to use the recovery console from an original Xp Home SP1 and the only option available were chkdsk /r chkdsk /f was not available. i got 25% complete and then a message that says there were portion is unrecoverable.

When i go home i will connect the HDD to my laptop and do chkdsk <drive letter> /f

 

[netxm]

usually "chkdsk /r" and then "fixboot" help. Run SMART test to see if HDD not failed completely, if so recover data and get new hard drive.

 

[vontreigo]

HP or Compaq with AMD chip?