Hardware

Ask something
Question Locked

ntfs.sys and 0x00000024 BSOD

0 helpful
13 replies

by glostah

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

OK, I'm not a noob to this at all, so please read this entire post before answering, because I have already tried all of the obvious answers.

I had a machine that went into a constant reboot cycle,rebooting no matter what when it hit a certain point in the boot cycle (it think it was when it loaded mup.sys. It turned out in the long run the computer had a bad RAM slot (#1), but that was only after trouble shooting for a while and installing a new system (XP sp 2) on a new hard drive. The machine is running OK now, but it seems like it may be on its last legs - and I think it's the mobo.

The problem is with the hard drive that was in the system. It's a Seagate Barracuda 7200.7 40 Gig. It was running fine with winxp pro xp2 (with all the latest patches) until the reboot cycle problem.

No matter what I do with the hard drive, it will crash any system it comes in contact with no matter how it is attached.

I always get the same BSOD with the error 0x00000024, and a message stating that there is a problem with my ntfs.sys.

Here's what I've tried so far, all with the same result:

-> Booting from windows xp cd - crashes at 'Starting Windows'

-> Boot to safe mode - crashes immediately

-> Boot to safe mode with command prompt - crashes immediately

-> Last know good configuration - crashes immediately

-> Boot using Bart's PE - crashes halfway through boot

-> Attaching the drive as a slave on the IDE to a different computer with a clean, running system (XP sp2) as master

-> Attaching the drive using a USB HD housing to a number of different machines running XP SP2. When the machine reads the drive the whole system crashes.

This is totally weird to me and I was wondering if anybody has ever had the same issue.

Additionally can anybody tell me if there is a way to skip the ntfs.sys while booting for just that drive? Or some way to isolate the drive that I am not aware of?

Thanks in advance for any help!

13 replies

by rob miners

Seagates Disk test Utility and run it. What it finds will let you know whether or not you can keep going. It will probably show the drives in red. That indicates a currupt file system. If it comes up clear download this.
http://tinyurl.com/2s8vta
Either create a bootable floppy or cd.
Try and and run dskchk C: /f it should ask to unmount the volume before proceeding. Yes to unmount.
Might help. WINPE is a lot more powerful than Bart PE but is only avialable through the Action Pack. It runs independent from the OS.

by glostah

you missed an important fact in my post - any computer the drive was attached to crashed, so there was no DOS or command prompt and I couldn't boot from a cd if the drive was connected.

by glostah

Basically I lucked out. I brought the disk to my office where I was running a Windows 2003 server and a Windows 2000 workstation.

I connected it to the windows 2000 workstation via usb and of course it crashed. To my surprise when I connected it to the Windows 2003 Server, it didn't crash. Weird thing was that the disk was not immediately recognized by the system.

What I had to do was open the disk management console. The disk was visible there, was reported as 'healthy' but there was no drive letter. All I did was right click the disk, selected 'change drive letter and path' and assigned it a new drive letter, after a few minutes of waiting the drive appeared and was completely readable.

I have no clue why this would work on a Windows 2003 server and not on a wimdows xp machine, but I thought I would document what happened anyhow.

by rob miners

what was the power supply wattage on the 2000 PC and the 2003 machine?

PS. Glad you solved it that type of problem can be a real pain.

by glostah

They were older machines though, so I would think they would both be 300-350, or even lower.

After I ran a chkdsk /r, I ran both spyware and virus scans. While nothing was found by the scanning softwares, I did find and empty folder in C:/ root that was sort of suspicious, looked up the folder name and found that it was from a virus, but there was nothing in it. I assumed it was created by a virus and was either caught or removed by the virus real time scanner. I didn't make note of the name, but, in hindsight, it may have had something to do with the corrupt ntfs.sys.

by pablo_aguilera_carvallo

Hello, I've just tried what you have said here. But my Windows 2003 server doesn't recognize the hard drive, so I can't fix it. Any suggestions?.

by gotomile2255

Hi, I am having the exact same problem with my HDD. Did you ever figure out how to solve this error: ntfs.sys and 0x00000024 BSOD

Thanks Jason.Cairns @ gmail

by w2ktechman

It states that it was fixed.

Otherwise, please post a new question

by gotomile2255

I was able to gain access to my HDD by connecting it to a different operating system (vista and OS) on my other computers. I was wondering if you were able to fix the error. Or just copied all your data and reinstalled the operating system again. I'd really like to figure out how to repair the error, now that I have access to the HDD. Any suggestions would be greatly appreciated. THANKS

by glostah

In hindsight, I think that the problem was a partition issue because the Windows server could see the disk but there was no drive letter. To solve this I think your problem is going to be finding a system that runs Windows Server 2003. It was my experience that WS2003 was the only system that could handle the disk without crashing and 'repair' the partition, which is what I assumed happened when I reassigned the drive letter.

I tried just about everything before that - check out my original post for the info on what I tried.

Good luck. I'd be interested in hearing about the rest of your experience!

by gotomile2255

I was able to connect the HDD to my Mac and get some of my files off. I'm missing some of my files (not sure what that means). I was also successful in connecting it to my another computer running Vista. I'm just working on trying to figure out how to repair it, now that I have access to the HDD, any suggestions. THANKS

by gotomile2255

I connected my HDD to my computer using Vista and ran CHKDSK and then put the HDD back into my laptop and started it normally and it worked! Thanks, my day just got a lot better.

This discussion is closed to new replies.