Help!!! Massive Problems!

[M4LFUNCT10N]

Okay this completely sucks. The computer I was trying to fix earlier this week is still having problems!

So... we've replaced now...

HD with a Seagate 80gig Barracuda
Mobo with a P4 Gigabyte Titan
Processor P4 1.8 with 800fsb
Video card is a 32MB AGP
etc etc etc..

So... we had memory problems before.

Now each time it's going through the XP setup it crashes.

First error was with the:
ntfs.nfs

Next:
cdfs.nfs

Next:
acpi.sys


I can't even reformat the damn thing! WTF is going on????

[Itsmeee]

I'd run a memory tester again. It still sounds like memory issues. That can often be fixed as easily as putting your memory in a different DIMM. Actually that would be my first try. Put the memory in DIMM 2 instead of 1. Then try 3. Then go back to 1. Also make sure your bios is configured properly. FSB, for both cpu and mem. That could cause issues.

[M4LFUNCT10N]

Will do... I'll post my results in a minute..

[M4LFUNCT10N]

Windows Setup




The file ntfs.sys is corrupted.

Press any key to continue.

[Itsmeee]

well you can try repairing your install of windows. I'd keep fiddling with the memory. Best if you get this (http://www.memtest86.com/) memory testing program and let it run for half an hour or so. It'll find any problems with your ram. If its good to go then you know its something else.

[M4LFUNCT10N]

Why the hell do some computers setup incredibly smoothly..... and yet others will take forever running into tons and tons of problems???? I just don't understand! This is acting like my old computer that I setup 10 years ago...

Okay so here's another error.

"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: Ftdisk.sys

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory option such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.

Technical information:

***STOP: 0x00000050 (0x884CAB5C, 0x00000000, 0xF84E4383, 0x00000000)

*** Ftdisk.sys - Address F84E4383 bast at F84C9000, DateStamp 3b7d8419

[M4LFUNCT10N]

Okay, let me elaborate. I don't have an operating system installed. These errors are happening while I'm going through the XP setup.

[tivac]

Try a different XP cd. It sounds like some of the files being copied off of your current one are corrupted.

[M4LFUNCT10N]

I've got/tried 3 different discs, NONE have scratches or imperfections, all have been used before to install XP. One is a retail CD, and the other two were burned from ISO's that were free copies obtained through college courses(fully legit). Same problems with each disc. I'm going to pull a CD-rom off of one of the new computers I've built and see if maybe the CD-rom is dead. Other than the video card, the CD-roms are the only things that remain from the old computer.

[Itsmeee]

http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/prmd_stp_ccgm.asp

I'm fairly sure it has to do with the memory. Its either that or a horrid virus.

[M4LFUNCT10N]

Ok, both times I've messed around with this, the first time with the old computer and now with the new setup, I've been using Centon ram purchased from Circuit City. On top of that, the ram came in a plastic clamshell case like many other cheap products, but NOT in an anti-static bag. Do you think that maybe they have a bad batch of ram? Should I tell my friend to return the ram and go buy some ram from Compucare?

[Itsmeee]

the clamshell is standered on whatever ram you unless its oem in wich case it comes in anti static. But no matter what ram it is, it can still be bad. Even stuff like Giel and kingston or corsair can easily come with just a teeny bad spot or just not like your PC. I'd deffinatly try it because that really sounds like the problem.

[DiscoDave]

Agreed.

[M4LFUNCT10N]

About the clamshell.... I've NEVER bought ram before that wasn't in an anti static bag also. So you're telling me that it's common practice not to use anti static bags? That's crazy...

[Airstotle]

I am no authority, but when I set up my current system, I had all the same errors come up. It was because I wasn't using the right memory. ie 2100 vs 2700 etc. I went to 2700 DDR and everything went smooth. Just a thought.:shrug:

[Airstotle]

And BTW all my said errors were during the installation of XP.

[M4LFUNCT10N]

I'm using 2700.... But I'll make my friend pony up for some better stuff.

[Excessive]

Originally posted by M4LFUNCT10N
About the clamshell.... I've NEVER bought ram before that wasn't in an anti static bag also. So you're telling me that it's common practice not to use anti static bags? That's crazy...

No its not crazy. It is not uncommon for ram to come in a plastic box. What do you think that anti-static bag is made out of?

[Itsmeee]

Originally posted by M4LFUNCT10N
I'm using 2700.... But I'll make my friend pony up for some better stuff.

it may just be that chip your usuing doesn't like your mobo. I'd seriously test it with memtest and and see what it comes up with. XP is VERY finicky about memory especially during installation.

This happens a lot, even when you've just switched your memory to another slot it sometimes happens. You may try resetting your bios, and doing the switch trick I mentioned above. Faster or different brand memory may work but only because its a different stick of memory not because its faster or a different brand.

[Airstotle]

Out of curiosity, how did it come out? Everything fine? Or still on hold?

[Dr. Deezee]

I'm envisioning a taped up motherboard with a glued on case. XD

[M4LFUNCT10N]

It's back together. New mobo, ram, HD, Processor. Had to downgrade the ram to 2100 for it to work. Once he got it installed, he put the 2700 ram back in and it's working great.