Missing or Corrupt Ntfs.sys

By Dedlbug ·
Hi everyone. I have a computer that when boots, displays something similar to: "Following file is missing or corrupt \system32\drivers\ntfs.sys"

Googling shows tons of similar issues and possible solutions. Here is what I have tried so far:
1. recovery console - copied ntfs.sys from xp disk to hard drive.
2. ran CHKDSK /R
3. ran system diagnostics and RAM tests. Passed.
4. removed different RAM chips and tried to boot again. / checked cables.
5. launched Windows Repair to do an in-place re-install of the OS.

None of these steps has resolved the issue. I thought for sure launching the Windows Repair to re-install all of the OS files would fix. But upon reboot after copying the files, the same error appears.

Anyone have any ideas? I am leaning to hardware failure. Here are some specs. Note the RAID setup.

Dell Dimension E510
Pentium D Processor
2 @ 2GB RAM sticks
RAID 1 Mirror (160GB SATA drives)

Thanks =]

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Tested the HDD with vendor's utility?

by seanferd In reply to Missing or Corrupt Ntfs.s ...

I'd visit the vendor's site, and find the appropriate tool to test your drive in a RAID config.

Collapse -

Just in addition to the above answer

by OH Smeg Moderator In reply to Tested the HDD with vendo ...

If the drive fails the first test in the computer remove it/them fit it to another computer and test it/them again with it's makers Testing Utility. If it still fails the Drive is Dead and gone to Silicon Heaven but if it passes the second test the M'Board Data Lead or Power Supply is damaged and needs replacing.

If you do not have a direct link to your HDD Makers Testing Utility try here



Collapse -

Maybe Power Supply?

by Dedlbug In reply to Just in addition to the a ...

Ok, I ran the Dell diagnostics on the existing hardware and didn't find any issues. However, since it is RAID 1, should I be worried to run the diagnostics on different hardware? What about seperating the drives and testing them independently on different or same computer? It shouldn't mess up the mirror, right? (I mention this because I couldn't find a bootable diagnostic from Maxtor for the SATA drives. All I could find were Windows based diagnostics.)

That being said, I needed to get the data off the drives more than anything. After that, I could get rid of the computer anyway. So I disconnected one of the hard drives and booted the computer. It booted into Windows fine. So I shutdown, disconnected the drive and re-connected the other one. Computer booted fine. I did not try to re-sync the RAID and I may not, as the computer is probably trash at this point. But would that lead to maybe a bad Power supply?

Either way, I am good now. Got the data off and computer is out of my hands now. Thanks to both of you for the great advice...again. :) What do you think about my questions above though?

Collapse -

OK for Maxtor Drives you need Seatools for DOS

by OH Smeg Moderator In reply to Maybe Power Supply?

You can get it from here


Though you do have to scroll down the page a far way. The Dell Diagnostics are next to useless particularly with a RAID Array as they will not test the individual Drives but the Array. If one dive is going off it may not be shown till it fails completely and the R in RAID stands for Redundant.


Collapse -

I'm giving out Thumbs!

by Dedlbug In reply to OK for Maxtor Drives you ...

Who wants a thumb?

Seriously, thanks again. I would have checked Seagate's site eventually, but once the data was off, the project was over.

I agree with the Dell Diagnostics. I run them at times when I need to buy time for a bizarre issue, and sometimes they do detect failures...sometimes. Although I can't remember if I ever ran the Dell diagnostics against a RAID array. Usually against a single drive. Typically I will use UBCD for hard drive diagnostics, which contains the Seagate tools.

Would you recommend that hard drive diagnostics always be run on a single drive instead of in the RAID? Most of the time, I simply get lucky. RAID detects a failed drive, swap the drive and re-sync/rebuild.

Thanks again.

Collapse -

My personal opinion which may not be worth much anyway

by OH Smeg Moderator In reply to I'm giving out Thumbs!

Is that you should always use the Makers Testing Utility on a Single Drive when ever there is any question of a Drive Issue.

When it comes to RAID Arrays I never fully trust any Diagnostic Utility to actually tell me the truth as the RAID Controller comes into play when these type of Tests are done. It may not be an issue with some VIA or SIS Controllers but with Adapter Controllers you are wasting your time testing the drives as any faults will be hidden by the Array.

Not sure what the other controllers work like as I have never used one so I can not really say.


Collapse -

how to repair missing or corrut ntfs.sys

by techno_mark In reply to Missing or Corrupt Ntfs.s ...

Use the Recovery Console to replace Ntfs.sys
Pop in your CD into the computer and boot off the CD when prompted to ?Press any key to boot from CD?. When the Welcome screen appears, press R to select the To repair a Windows XP
installation using Recovery Console, press R option.

Next, type the number for the installation you want to logon to from the Recovery Console. You?ll also need to know the administrator password in order to get to the command prompt.

Next, type the number for the installation you want to logon to from the Recovery Console. You?ll also need to know the administrator password in order to get to the command prompt.
cd \windows\system32\drivers
ren ntfs.sys ntfs.old

This basically renames the current ntfs.sys file to something else so that we can replace it with a new one that hopefully is not corrupted. Now type in the following command:
copy cd:\i386\ntfs.sys drive:\windows\system32\drivers

Where cd is the drive letter for the CD-ROM drive that has you Windows XP CD, and drive is the drive where you installed Windows XP (most likely C:).
That?s it! Now go ahead and remove the CD and type quit. Go ahead restart your computer and see if you are able to log back into Windows!

Related Discussions

Related Forums