XP filesystem corrupt - force chkdsk?

From: David Barge (dabblah@yahoo.com)
Date: 03/18/03 

From: "David Barge" <dabblah@yahoo.com>
Date: Mon, 17 Mar 2003 20:37:02 -0800

Hello,

No dice. The blasted thing bluescreens before it gets to
the recovery console, with the same ntfs error, if I try
to launch it from the CD as if I try to boot straight into
it. It generates the bluescreen immediately after pressing
R (same thing if I create the 6 setup disks and try to hit
R from there). From the CD running the recovery console,
from another hard drive either trying to boot into it (the
other drive, just to get it to run a check of the
filesystem) or to the recovery console (on the other
drive), or from the original drive, the blasted thing just
crapps out with the ntfs error whenever any part of XP
tries to access this drive's filesystem.

Two things really pain me about this (aside from the
obvious system being crashed...). First is that the system
does not just force chkdsk when it encounters a fatal
filesystem error on boot (or that it does not just force
it on the next reboot...). The second is I can not find a
switch to invoke XP with in the boot.ini (on a boot
floppy) to force chkdsk.

>-----Original Message-----
>Boot to XP cd and when it gives you choices type R for
>recovery console... then you can type help and get
>information on what all can be evoked - chkdsk is one.
>You should be able to type chkdsk and it should run.
>
>>-----Original Message-----
>>Hello,
>>
>>I am not sure why (but I have a suspicion enabling
>suspend
>>mode on it is the culperate), but my personal system
>>crashed yesterday. At this point when I attempt to boot
>>it, the machine bluescreens shortly after loading all
>>drivers and shifting to the XP (Professional version, by
>>the way...) startup screen. It tells me ntfs.sys is
>>corrupt (joy) with a STOP 0x00000024 error, and I should
>>disable any backup software or antivirus software and
>run
>>chkdsk. Unfortunately, that is all it does, and nothing
>>more. I have been searching in vain for a way to force
>it
>>to run chkdsk when I can not get the blasted thing to
>boot
>>any further than that. My most creative attempt so far
>has
>>been to install XP on a seperate hard drive (without the
>>original offender being connected to the system at all)
>>and install the recovery console. Unfortunately, if I
>>attempt to boot the new installation of XP (either
>>normally, or into the recovery console) it gives up the
>>ghost whenever it tries to access the second hard drive
>>(now configured as a slave). This also happens if I
>>attempt to repair the installation using the install CD,
>>or launch the recovery console from the install CD.
>>Basically right after I hit the "R" key, it dies
>reporting
>>the same ntfs.sys error. If I attempt a new install, it
>>dies in a slightly different manner, but will not
>install
>>on the drive as it is currently configured. Of course,
>>since I can not boot into the blasted thing I can not
>get
>>my product id so i have no way of submitting this to no-
>>charge support either (not being one to have written it
>>down, something which I will change in the future...).
>One
>>other thing, I ran the low level hardware diagnostics
>>provided by the HD manufacturer and they reported no
>error.
>>
>>The one fortunate thing of all this is I do have a fresh
>>backup. The backup software was not installed on this
>>machine, however, but run via a network share. Though it
>>was one of the possible culperates mentioned by the stop
>>error, it does not make sense to me that it could cause
>>this.
>>
>>So to recap, XP Professional died. Reports STOP
>0x00000024
>>ntfs.sys corruption on startup. Can not boot into XP
>even
>>on a seperate hard drive in the system, or into the
>>recovery console. Is there a way given all that, to
>force
>>chkdsk, or do I simply have to low level format it and
>>start over? Thanks to anyone with info.
>>.
>>
>.
>