Damaged NTFS volume won't boot.

[qwerty]

Could be corrupt mbr or bootloader or hosed/missing
system files.
Boot up with XP cd and run Fixboot command and see if
that unfudges your PC. Below is from Help and Support.

FixbootWrites a new partition boot sector to the system
partition. The fixboot command is only available when you
are using the Recovery Console.

fixboot [drive]

Parameter

drive

The drive to which a boot sector will be written. This
replaces the default drive, which is the system partition
you are logged on to. An example of a drive is:

D:

Example

The following example writes a new partition boot sector
to the system partition in drive D:

fixboot d:

Note

Using the fixboot command without any parameters will
write a new partition boot sector to the system partition
you are logged on to.
Related Topics

>-----Original Message-----
>This is a tough one.
>System was off this A.M. (I always leave it on) so I
>assume power failure last night.
>System would not boot. Comes to the splash screen then
>does a STOP: (some addresses) NTFS.SYS - (some more hex
>adddreses.
>
>After working with it for a while, I'm convinced that
bad
>indexes or something in the structure of the NTFS drive
>is crashing the NTFS.SYS.
>
>Can't boot in safe mode or run the Recovery Console
>because all of these modes attempt to mount the drive
and
>crash with the same error.
>
>I replaced the drive, loaded XP and the system works
fine
>(so It's not HW). I then made the bad drive D: and it
>crashes on boot when that drive is in the system, either
>on normal, safemode or recovery boot.
>
>I tried building an XP boot disk - but found that, due
to
>lack of enough space on a floppy, all that does is start
>the boot and switch to the HD. Like everything else it
>crashes when it mounts D:
>
>I need a way to run Chkdsk on that drive. I know that
if
>chkdsk is set to run on boot, it runs before the drives
>are mounted because I can force a check disk on C: and
it
>will run the check disk before mounting D: and crashing.
>But I can't get to D: to set the bad flag, I can only
run
>chkdsk on C. And I can't figure out where Windows sets
>the instruction to run Chkdsk on boot to see if I can
add
>a parameter to force it to check D:
>
>I wouldn't be fighting this so hard, but of course this
>drive contains some mission critical, unbacked up data.
>
>All suggestions welcome - I've searched the knowledge
>base all day and haven't found anything useful.
>.
>