Windows doesn't start Ntfs.sys

  • Thread starter Thread starter bpiela
  • Start date Start date
B

bpiela

Hello, I have an out of warranty Dell Dimension PC that I upgraded the memory
recently. The PC worked fine for a few months. Now, it no longer boots.
After the Dell splash screen, it immediately shows a message stating

"Windows could not start because the following file is missing or corrupt:
System32\Drivers\Ntfs.sys"

I looked this message up and found a couple of ideas. First, I checked the
memory by running memtest 1.70 against it. It came back with no errors.
Next, I actually attempted to repair the file. I booted off of the XP CD and
replaced the Ntfs.sys file. No change. I still get the message.

By changing the file, it makes me think that perhaps it is not a hdd issue
because the new ntfs.sys file would have been at a different block on the
disk. What are the odds that that block is bad?

Not sure what to try next. Any ideas would be greatly appreciated. Should
I try to reseat hardware and reconnect internal cables??

Thanks in advance.
 
Maybe?
"Windows could not start because the following file is missing:
\system32\drivers\ntfs.sys" error message in Windows XP Service Pack 2
http://support.microsoft.com/kb/887675/en-us

bpiela wrote:

> Hello, I have an out of warranty Dell Dimension PC that I upgraded the memory
> recently. The PC worked fine for a few months. Now, it no longer boots.
> After the Dell splash screen, it immediately shows a message stating
>
> "Windows could not start because the following file is missing or corrupt:
> System32\Drivers\Ntfs.sys"
>
> I looked this message up and found a couple of ideas. First, I checked the
> memory by running memtest 1.70 against it. It came back with no errors.
> Next, I actually attempted to repair the file. I booted off of the XP CD and
> replaced the Ntfs.sys file. No change. I still get the message.
>
> By changing the file, it makes me think that perhaps it is not a hdd issue
> because the new ntfs.sys file would have been at a different block on the
> disk. What are the odds that that block is bad?
>
> Not sure what to try next. Any ideas would be greatly appreciated. Should
> I try to reseat hardware and reconnect internal cables??
>
> Thanks in advance.
 
Back
Top