System32\Drivers\Ntfs.sys error on booting!

Smalltownboy · 21 May 2007 at 09:11

I've turned my pc on this morning to find this error

:Windows could not start because the following file is missing or corrupt::

:System32\Drivers\Ntfs.sys:

You can attempt to repair this file by starting Windows setup using the original CD-ROM.
Select 'r' at the first screen to repair.

Ok so i grab my installation CD and try to boot from CD, but i'm still coming up with the same error ,even when booting from CD. I have googled this problem al leading down the route of a failed hard drive. So i'm asking has any encountered this problem before and what the possibe answer could be?

Amd Athlon 64 X2 4200
Asrock 939 Dual - Sata2
2048MB DDR400
Hiper Type-R 580W

Jaffa_Cake · 21 May 2007 at 09:16

I think you must have done something wrong.

Googling the error came up with this from several different sources.

http://www.computerhope.com/issues/ch000876.htm

Smalltownboy · 21 May 2007 at 09:21

Jaffa_Cake said:
I think you must have done something wrong.

Googling the error came up with this from several different sources.

http://www.computerhope.com/issues/ch000876.htm

No i have seen thas page i just dont know what to do because i can't even get to the windows installation part i just get that error.

t31os · 21 May 2007 at 09:51

That page gives you information on other things it might be.

How about trying 1 stick of memory at a time?.....

Smalltownboy · 21 May 2007 at 09:57

I've tried the memory by taken 1 out and booting it up and vice versa with the other stick. Everything seem's to be ok as it's reading 1024mb on boot up. It's annoying because it could be anything by the looks.

misterPK · 21 May 2007 at 10:18

Have you got more than one hard drive?

I think, cant remember for certain, that I had this error a few weeks back. I have a SATA drive and an ancient IDE drive that I had just formatted. I unplugged the IDE drive and it worked fine.

PK!

Smalltownboy · 21 May 2007 at 10:25

No i have only the 1 drive it's a 200gb Maxtor 6V200E0] Would a failure of the drive cause this sort of error? I'm sorry but i'm no that tech minded what are the usual signs of a knackered HD?

Smalltownboy · 21 May 2007 at 17:11

Hello just reporting back to say the problem still exists. Can anyone help?

Ray.uk · 21 May 2007 at 17:17

Stating the obvious but have you changed the boot sequence to CD first

Smalltownboy · 21 May 2007 at 17:21

Yes i've been into the BIOS and changed the sequence in which the pc boots up.As the boot from CD message appears i hit a key and i come to the same message.

bloodiedathame · 21 May 2007 at 17:26

Try setting the BIOS to only boot from the CD rather than giving it the option to boot from the HDD. So the only boot option in the sequence is the CD ROM.

Smalltownboy · 21 May 2007 at 17:34

a.hay said:
Try setting the BIOS to only boot from the CD rather than giving it the option to boot from the HDD. So the only boot option in the sequence is the CD ROM.

Tried, disabled all bar the CD drive nothing.Most likely a hardware issue there does'nt seem to be an answer here.I don't have a second desktop setup to try an eliminate the problem i.e bad HDD or Memory.

Rroff · 21 May 2007 at 18:14

OK

This error is pretty nasty - and its quite likely other files on your OS installation are corrupt too...

Theres only 2 ways to fix this...

(1) (reccomended) You need to find a copy of the ms server 2003 install disc - MS used to have a trial version you could download and burn but Im not sure if its still available... from this disc you can get into the recovery console and run chkdsk - which will allow you to then recover from your normal windows disc... if you can't get hold of the server 2003 disc then you can try a windows 2000 disc but this doesn't always work...

(2) (not reccomended) a linux live CD that has ntfs tools (or similiar set of recovery discs) that allow you to mark the disc as dirty and run a disc scan.

NOTE: You can not reinstall windows from an XP disc with this problem, neither can you get to safe mode or the recovery console, neither can you put the drive in another machine running windows XP (or any other OS supporting NTFS) as the moment you try to mount that disc it will cause windows to fall over.

EDIT: Should be able to get the trial version of server 2003 here: http://www.microsoft.com/technet/windowsserver/evaluate/trial/default.mspx aslong as you have access to burn a CDR of this it will fix you up in no time - for some reason server 2003 has relaxed ntfs requirements that allow you to work around this error whereas XP won't.

Rroff · 21 May 2007 at 18:20

This problem can occur due to a sudden reboot or freeze in windows, but it can also be a pointer to a failing HDD or problems with the RAM - if your lucky you can just boot off the server 2003 CD, run chkdsk with the repair flag and then try booting as normal, if the disc itself isn't damaged you should be able to boot up, if other files are corrupt as well you will get errors while windows boots up and probably halted with a can't start user interface error. You should be able to then pop the windows XP CD in and do a repair install (a full reinstall would be better tho)...

Sorry if my posts aren't very clear I'm a bit busy atm and typing in a hurry.

Smalltownboy · 21 May 2007 at 19:26

Thank You Rroff your time is much appreciated. I ill try this option now to see if it works!