![]() |
|
#21
|
|||
|
|||
Microsofts suggestion did not work!I also have a Maxtor 120 GB harddrive. I also have the ntfs.sys corrupt or missing error. I did what Microsoft suggested by renaming the ntfs.sys file and then adding from my MSFT CD but it did not do the trick.
Any suggestions? Quote:
|
|||
|
#22
|
||||
|
||||
|
sorry to say it mate but the only sollution i had was to reformat - luckily all was not lost as i had previously "ghosted" my hd.......... i stronly recomend anyone buy norton ghost as it is a life saver and wil always prevail...oh and the fact is norton r best, so u cn be rest assured ur pc is in safe hands.well as safe as a pcs can get!
__________________
HOOD |
|
#23
|
|||
|
|||
|
Quote:
I had this problem also, and was not able to enter the windows setup. I switched ram chips and that did the trick. I logged into the recovery console, followed the above steps and BAM windows was back on line. I replaced the original ram and it still worked. Thanks! |
|
#24
|
||||
|
||||
|
Hello Ozz1113,
This thread is certainly not dead! MANY people find this thread DAILY (just look at the page views count for this thread!). So adding relevant information to this [unresolved] thread is always something we encourage and welcome. Thank you... you've earned yourself some REP! __________________
J de Silva Learning Journal | GIDForums™ | GIDNetwork™ | GIDWebhosts™ | GIDSearch™ |
|
#25
|
|||
|
|||
|
OMG, you're right. I actually found this thread while searching for the problem on msn. I just saw the view count now, 12.5k!
Thanks again for the post, that saved my dad's pc. |
|
#26
|
|||
|
|||
|
In my case it was simply because the ram timings were too tight, try something like 7-3-3-2.5 and see if it helps. I wouldnt recommend panicing and reformatting, it's more than likely not a HD or corrupt file problem. It could be caused by simply adding cheap ram that cant do tight timings. Maybe even up the timings to 7-4-4-3 or something of the like if you paid 30 bucks for a stick of crap and thought you got a deal.
|
|
#27
|
|||
|
|||
|
Quote:
Check your motherboard book. I bought new ram and had all kinds of problem. I learned that you can only run DS (doublesided) and SS (singlesided) ram in certain slots, in certain order, My book showed a graph on which slots could hold which type of memory and in which order. BTW I came here looking for answers to the NTSF.sys problem, and found it. I removed one ram chip from my son's computer, and now it boots. Thanks |
|
#28
|
|||
|
|||
|
Quote:
GF |
|
#29
|
|||
|
|||
|
Quote:
Pc |
|
#30
|
|||
|
|||
|
I don't know how successful this may be, but perhaps you could test your computers memory. There's a util, aptly names memtest, which runs in dos and should verify isf it's a faulty dimm. Link: www.home.earthlink.net
Best run it from a dos boot disk. GF |
Recent GIDBlog
Accepted for Ph.D. program by crystalattice
| Thread Tools | Search this Thread |
| Rate This Thread | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| .htaccess on Windows2k, and the trailing slash | Pedster2k | Apache Web Server Forum | 6 | 24-Jan-2004 18:32 |
| Missing NTFS | 1234567j | Computer Hardware Forum | 1 | 25-Oct-2003 06:09 |
Network Sites: GIDNetwork · GIDWebHosts · GIDSearch · Learning Journal by J de Silva, The