[dsenette]

is it still giving the same disk 0 error?

[Advertisements]

How dumb of me, I did not realize that we're on the second page of posts, just kept refreshing and getting no new replies...
This is the only error that I get, apart from not being able to access XP from HD nor the CD-ROM:

A problem has been detected and Windows has been shut down to prevent damage to your computer.
The problem seems to be caused by the following file: ntfs.sys

PAGE_FAULT_IN_NONPAGED_AREA

Technical information:
*** STOP: 0x00000050 (0xE1187000, 0x00000000, 0xF8F56E89, 0x00000001)
*** ntfs.sys - Address F8F56E89 base at F8EE9000, DateStamp 3b7dc5d0

I just ran the Dell Diagnostic from CD again, everything came back fine. Also, tried accessing the HD as a slave on another computer. That computer would not even boot to Windows when this drive was connected!

[pera00]

How dumb of me, I did not realize that we're on the second page of posts, just kept refreshing and getting no new replies...
This is the only error that I get, apart from not being able to access XP from HD nor the CD-ROM:

A problem has been detected and Windows has been shut down to prevent damage to your computer.
The problem seems to be caused by the following file: ntfs.sys

PAGE_FAULT_IN_NONPAGED_AREA

Technical information:
*** STOP: 0x00000050 (0xE1187000, 0x00000000, 0xF8F56E89, 0x00000001)
*** ntfs.sys - Address F8F56E89 base at F8EE9000, DateStamp 3b7dc5d0

I just ran the Dell Diagnostic from CD again, everything came back fine. Also, tried accessing the HD as a slave on another computer. That computer would not even boot to Windows when this drive was connected!

[dsenette]

http://www.microsoft...md_stp_ccgm.asp

that's the microsoft reference of that stop code...

what's the last piece of hardware you installed? besides the ram...

[pera00]

I saw that Microsoft reference as well. The last and only hardware that I installed was D-link wireless network card (PCI), I even removed it in hopes of getting the computer to boot up, no difference. When I think of anything else, the last time I was able to use the computer I had just downloaded the updates for Avast virus scanner. Short time later I had an Avast message on the screen saying that computer had to be restarted. I did not think anything of it and shut down the machine. At the same time I thought to throw in the memory modules that I had been wanting to try to install. So, I put in the two modules and rebooted, that is when my problems started...

[dsenette]

interesting coincidence.....can you boot into safe mode?

[pera00]

I wish, no booting to any Windows mode, it just keeps sending me back to that same screen with different boot options but will not boot to any of them. It is interesting that Dell Diag CD is readable from the CD-ROM but I still can't do anything with Win XP CD. It always hangs at that same spot with that ntfs.sys error.

[dsenette]

Stop 0x00000024 or NTFS_FILE_SYSTEM

is that the error that you get?

[pera00]

No, it is Stop 0x00000050 or NTFS.sys, see below for details:


*** STOP: 0x00000050 (0xE1187000, 0x00000000, 0xF8F56E89, 0x00000001)
*** ntfs.sys - Address F8F56E89 base at F8EE9000, DateStamp 3b7dc5d0

[dsenette]

that doesn't make sense at all.... an 0x50....is usually the PAGE_FAULT_IN_NONPAGED_AREA

an 0x24 is usually the ntfs.sys...

none of the things for the 0x50 are gonna help much because you usually have to get into safe mode...so lets make like it's an 0x24..hehe

boot from the xp cd...and get to the recovery console if you can...

once there type
chkdsk /r

and let that run..it should take an hour or so

[pera00]

Well, there lies the problem, I can't get to the recovery console using the XP cd. Once I try, that's when the error decides to pop on the screen:

"A problem has been detected and Windows has been shut down to prevent damage to your computer.
The problem seems to be caused by the following file: ntfs.sys

PAGE_FAULT_IN_NONPAGED_AREA

Technical information:
*** STOP: 0x00000050 (0xE1187000, 0x00000000, 0xF8F56E89, 0x00000001)
*** ntfs.sys - Address F8F56E89 base at F8EE9000, DateStamp 3b7dc5d0"

[dsenette]

ok...now that error is making sense..now that it's all put together...darned contraptions...

http://www.microsoft...hd_exe_duol.asp

that's your MS KB article...but..not gonna be much help since you can't boot

[pera00]

It is interesting that it says: "Faulty hardware, a buggy system service, antivirus software, and a corrupted NTFS volume can all generate this type of error." I guess that would fit the bill. So, what do you think I have, a slightly used, expensive boat anchor? Is there any way to force an access to the HD? Nothing seems to work, even the other computer disliked this HD.

[dsenette]

do you have a cd burner on the machine you're using right now?

[pera00]

Yes, I do.

[Doby]

dsenette has been doing a fine job and I think he's on the right track so I will let him continue but do you know what name brand HDD is in the computer?

I think you should try a low level format of the drive, manufactuers make tools to do this thats why I am asking and I think thats what dsenette maybe going to try.

Rick