I got the same error about the missing/ corrupted NTFS.sys file. In my case I have just setup a new modem and rebooted. But while rebooting I also connecting an additional HDD. So am not really sure what is causing the problem.

Also am unable to repair coz the installation process aborts aborts with an error stating an "Error at line 4".

Ne ways will try your suggestions guys... n promise to update this site tomo.. to let ya know if ne of them worked.

Thanks,

I've just started havinf this problem on my laptop. I know that some have chalked it up to bad RAM, but I haven't added any RAM since September of last year. The problem only started popping up in June of this year, and it's not consistent. Sometimes I get caught in a "press "r" to repair" cycle, and other times, I can hard boot it and it starts up fine (for a while).
Ultimately, last night, in a fit of desperation, I restored to my factory image (using the restore disks). Somehow, the problem reappeared immediately. Any thoughts?

Okay guys.. herez what I inferred my problems..

1. I was getting the same problem if I tried restarting either XP or 2003 with my MODEM connected. If the modem was plugged out.. the OS started and then when I plugged the modem in all would be fine

2. To overcome this problem I installed Win 2k on the m/c, n now modem or no modem I get the error "..press r to repair"..

so buddies the problems can be caused either by conflicting hardware (which could be anything.. n not just u'r RAM).. or by conflicting software

I'm not sure that my problems can be attributed to a hardware or software conflict. As I indicated in my previous post, the problem popped up after I did a clean install of my entire OS...after loading the factory image, I installed only one item, a driver for my wireless LAN module. The driver (and LAN module) came directly from the computer manufacturer.

The only other "non-factory" hardware or software was some additional RAM which I installed about 9 months prior to any problems.

Okay...looks like I've proven myself wrong. I removed the 512 Mg Ram card I had installed months ago, and the problems I've been having seem to have disappeared. I'm cautious about saying that the RAM was definately the problem, but it is looking that way. I can thank this thread for pointing me in the right direction.

I still don't understand why the RAM would be fine for months, and then act up. It can't be a software-hardware conflict, because I scrubbed the drive. But then, I thought I knew what I was talking about before...

I am recieving the same error message reguarding the missing or corrupt NTFS.sys, except I am not switching from a different filing system, I have simply done a clean install because of an incredibly illusive spyware program I couldn't remove. I do have a Maxtor drive. Is this just a faulty drive? If so, Western Digital is my new friend.

Just so everyone knows... I've heard a lot of acclaim on this thread about Western Digital drives being, basically, the gold standard drives. Well, I'm just putting in my two cents about them not always being this rock solid. I had a WD drive that worked fine for 2 months then died. And I mean DIED... it audibly became loud. Usually hard drives die because of a minute bastardization of the read/write head or something else macroscopically insignificant that causes the drive to fail. But the rotating mechanisms failed... a real manufacturing problem. And no, this thing had not suffered any shocks, whether mechanical or electrical.

And BTW I have this exact problem with ntfs.sys giving me trouble and setupdd.sys not loading of the XP Pro CD. It happened to start an hour after I physically attached a serial scanner, not even plugging it in yet to AC. Of course, detaching the scanner didn't fix it, that would be too easy. So off to the PC133 modules I go. I'm gonna try booting it with what I consider the bare minimum for the XP CD to load. One RAM module, the video card, the CD drive, and the CPU. Not even the hard drive in question. Not even the front-panel's LED connectors, buttons, and the tiny PC speaker. If it still doesn't work, I'll spend $15 instead of $150 on therapy by purchasing a sledge hammer.

So I removed one PC133 256MB module and my computer was dead as a doornail. I replaced it and took out the other one, and it works perfectly. Not only did it load the setupdd file from the CD, but i took out the CD and reset the computer just for the hell of it, and low-and-behold even the ntfs.sys error went away. So the bad RAM not only didnt let setupdd load, but caused ntfs to be read wrong. I did a system restore in XP to the day before for good measure.

BTW this thread is a prime example of why the internet can truly be an educational tool and not just a tool for playing with your tool. (pause for laughter) This thread is over a year old and has helped a lot of people. Kudos.

Following upon my previous posts, since removing the extra 512 Mb card from my laptop (it came with 256), I haven't seen the "missing ntfs.sys" problem at all. I did a fresh install of the OS, and all has been, for the most part, fine. I say for the most part, because I am getting a new error message, saying that the program referenced an instruction which referred to memory at _____, which could not be "read". So it sounds like there may be a problem with the "factory" 256 Mb RAM card. So I'm left to wonder, if there was something wrong with my "aftermarket" RAM, could that have caused a problem with the original RAM card. Alternatively, I suppose I should consider the possibility that some external cause, such as heat, caused a problem with both cards.
Has anyone had any experience with this?

I took a look at everything that was posted here previously. I am a technician and have dealt with numerous issues regarding MAXTOR hard drives since its the cheap HD of choice by our vendor. So my first assumption is HD when I ran across this problem. the RAM thing still makes NO sense to me. However, After careful observation of my motherboard I noticed 3 capacitors that have popped. After replacing the motherboard. BAM... it worked!! Just a thought you might want to consider. JAMMM