Forum Home
Press F1
 
Thread ID: 75679 2007-01-07 04:43:00 Is this problem terminal? boochild (11733) Press F1
Post ID Timestamp Content User
513470 2007-01-07 04:43:00 Hi there

First post, so please be gentle .
The symptoms: HDD won't boot giving BSOD stop error Ox24 - NTFS file system error .

The cause: Received virus warning regarding ntfs . sys file, and foolishly agreed to quarantine this file . At least the time line would suggest this .

If I try to boot using this volume, then stop error occurs . If Recovery console is attempted via XP CD (repair or replace the ''problem'' file), then once again BSOD with same error . If I boot from a different volume, with this drive attached via USB, as soon as it is switched on, then BSOD .

Where to from here?

I have all the data, well almost all backed up, so this isn't an issue .

Have looked at posts regarding this error, but other suggestions require recovery console, or being able to see the volume .

XP SP2
drive is SATA 250gb

Thanks in advance . 		boochild (11733)
513471 2007-01-07 04:49:00 Try this (support.microsoft.com) Speedy Gonzales (78)
513472 2007-01-10 08:06:00 Thanks for the reply .
I may be a little slow on the up take, so more assistance would be great .

The link to the Support pages above, works on the premise of booting from a FAT32 drive, renaming the ntfs . sys file and being able to access the problem NTFS drive and checking it, without the driver loading .

All sounds good . Have a FAT32 volume only connected,and a renamed ntfs . Then Windows , automatically recreates the file .

This means the NTFS drive with an issue still gives a BSOD . I have it as an external drive currently, as soon as it is switched on and found, Windows restarts .

Sorry, as I said, may be a lottle slow on the up-take . Still unable to access the drive .

Hope someone is able to assist and point out the error of my ways .

Thanks 		boochild (11733)
513473 2007-01-10 20:36:00 You say data recovery is not an issue so why don't you simply reformat this drive and re-install? Either way, there is grief, but at least the outcome is more certain with a reformat. linw (53)
513474 2007-01-10 20:42:00 I agree, format and go .
Except, everytime the drive starts - I either get the stop:0x24 error or, it will cause a reboot .

Data isn't critical, formatting would be the best, just need to get to a place where this can happen .

Forehead a little bloodied from bashing head against monitor .

Thanks 		boochild (11733)
513475 2007-01-10 21:37:00 And r u doing a clean install??

If u r, and its still crashing, the only way to fix it would be to connect it to another PC as a slave. And then format it.

Or take it off USB and put it in the case. Or get another USB cable. 		Speedy Gonzales (78)
513476 2007-01-10 22:42:00 Okay let me take a step back .
The drive with issues was formerly the primary drive . I have since installed a second HDD with a FAT32 partition in a hope of a result, see the MS Support link above .

The drive is SATA, and does not appear to have jumpers to set Master/Slave - is this correct? If it is connected directly, BIOS see's the drive, and boot order detects the installation on the FAT32 drive . Okay so far . Boot the system and it will reboot during startup .

My problem is, for want of a better word, stability . I can't access the drive through recovery console to try and format it - it gives an error 0x24 . And I can't boot and see the drive .

So, back to my original question, is it toast?

Thanks 		boochild (11733)
1