• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

PC keeps rebooting before XP loads ... please help

Flack

n00b
Joined
Jun 28, 2003
Messages
45
Hello,

I was installing a netgear wireless 4 port router on my PC. I boot down, made the simple ethernet connections and tried to boot back up. While i was doing this, the power in my building went out for a minute, and then came back on. Great timing...

So, I go to boot up, and the computer loads up to the screen that says windows failed to load properly, (WINDOWS XP). It gives me the choices of safe mode, safe mode with networking, last good config and normal bootup. Any one i choose, the Windows logo screen comes up, the blue bar makes two trips and then my computer reboots. (If i choose safe mode, a whole list of files runs down the screen, and then it suddenly reboots again). I have a hard time believing the netgear thing could have caused all this.

I changed my hardware back to the old setup, which worked great for a long long time before, but still i cant load windows, or even safe mode or nothing.

I went into BIOS and my tempuratures are fine, and all my fans are spinning properly. I thought it might be a PSU problem, so I tried to ease some juice by unplugging my dvd rom and cd rom drives, but still it has the same problem.

When the computer posts, it see's the hard drive, it shows its name and its size, but when I try to do a Windows XP repair, by booting off of the CD, it said that no hard disk is found. This could be due to the fact that I'm not using traditional IDE, but a SATA connection, and I'm not sure if I have to reinstall the drivers for windows cd to see it and repair it.

Does anyone have any clue about what could be causing this? It would be utterly disasterous if it was my harddrive, and I lost all my data.

I just cant seem to figure out what it is, and all of these freaking problems when installing a simple netgear wireless switch. I am about to throw this pc out the window. Seriously.

Any help would be greatly appreciated, and I could use all the help I could get.

Thank you

Flack
 
First of all when booting off a cd and raid or other type of drive controller you need to hit that F6 key and load the drivers.

If you can decipher windows abreviations then boot it into recovery console and disable the driver you installed. For example to disable an nvidia drivers you would type at the prompt

disable nv
 
Thank you for your help.

I seem to have narrowed down the problem a little more. When I install my Sata drivers after booting off of the xp cd, and try to do a windows repair, it crashes and says

Stop 0x00000024
Also, ntfs.sys error

So it seems something is wrong with the ntfs on my drive. Now, the microsoft solutions to this problem all involve successfully booting up, and running chkdsk /f ...
However, I cannot boot up successfully.

So, my question to you is, how do I boot into recovery console so I can do a chkdsk /f ?
A windows 98 bootdisk wont work becuase my drive is ntfs, and that is all I know how to do...

That is to say, how do I get a command prompt on windows XP when I cannot load windows or boot up successfully?

Thanks

EDIT: I know that with the window's boot cd, you can hit "r" to open the recovery console, but when I hit "r", after a little bit it crashes to a blue screen that gives me the aforementioned error.

So, is there a bootdisk method that can give me a command prompt or something like that?
 
Download the drive manufactures utilities software and run full diag's on the drivers.
 
Download the drive manufactures utilities software and run full diag's on the drivers.

Cant boot up windows, so cant run any diag's on anything... And I dont think drivers are the problem, ntfs.sys is, I believe...

Just can't get to a command prompt to do a chkdsk /p...

thanks
 
Flack said:
Cant boot up windows, so cant run any diag's on anything... And I dont think drivers are the problem, ntfs.sys is, I believe...

Just can't get to a command prompt to do a chkdsk /p...

thanks
You don't need an OS for them. They run from dos.
 
You don't need an OS for them. They run from dos.

Ahh, I see. Thank you for the advice...

The problem with that, however, is that I cannot get to dos. When I boot off of the cd, and try recovery console, the 0x24 error comes again.

Once I get to a dos recovery console, then I will run all the diags in the world and do chkdsk...
Just gotta find a way around this STOP ntfs.sys error...

As for the Bart PE boot off the cd thing, it looks very promising and I will definitely try this if my other ideas fail... thanks for the link!
 
Download the program on another system. Run the program, it will then create a bootable dos disk with there utilities on it. You won't be running this from recovery console but from a bootable floppy. I would like to make sure there isn't a hard disk problem before we go any further. You will most likely have to take the drives from a phisical raid setup to a single drive setup for testing.
 
I had that same code 0x24 problem, same type, reboots too. All I had to do was try another Windows XP CD. I was using an XP pro OEM cd and that screwed up things and I tried to revert to my other *UPGRADE* Xp Pro (non-OEM) and it worked through without a hitch.

-CHoLie.
 
Thanks for all the help guys, I wasn't able to get to a working computer sooner, but here is the update.

I tried to repair after going to setup, and then letting it detext xp and repair it, but the same stop error came up. Luckily, after a while of almost going insane, I fixed it.

What I had to do is make the 4 boot disks for win 2k pro (even though it was an XP problem). And on the first boot disk i had to comment out a line that loads the ntfs.sys drivers. This prevents it from loading and therefore there would be no stop error. Then I boot off of these four disks, go into their recovery console and do a chkdsk /p ...
All my data was saved and it boot up fine.

Then I backed up all my shit and formatted / clean installed the crap.
Thank God that saga is over, I seriously almost through it out the window... twice.

Thanks again
 
Haha, that's impressive (to even fix it, I would've never thought that). Anyone notice a correlation between Windows XP (and other Windows series) and the angry people throwing their computers out of the 'Window'? ;-)
 
Back
Top