Hey all... I have a huge problem with the build I made last week so I'm going to try and give you all the information I have and hopefully someone can help me!

I had the system all set up with no problems and it was running fine. Updated all the Windows files and downloaded some programs. My Arctic Cooling 7 fan/heatsink arrived so I took some time to put that on (was working perfectly according to SpeedFan) and also to throw some Y-connectors on so I could get all the fans working. Okay, everything still fine. About 3 days later, I was playing WoW and bam... WoW throws an error at me (error 141, corrupted file - as I would find out later)... and while I was looking at that error BAM... BCOD out of nowhere (watchdog.sys was mentioned on the screen). Okay... that was a little odd.

Eventually, I reboot and get back in to Windows and run WoW's repair utility which tells me that too many files are corrupted and that I should reinstall... okay... ran the Uninstall Utility... BAM... BCOD again (PFN_LIST_CORRUPT). Then on the reboot, Windows decides that it should run the Chkdsk untility and starts telling me how some files are corrupted and something about badly linked attribute records and how its fixing them... okay. I get into Window again... Firefox apparently goes corrupt as I cannot open it without an error... Windows Notifications are popping up all over the place telling me how this file or that file is now corrupt, many of them obsecure random files. So... I run AVG Virus scanner... nothing except that it tells me 5 or 6 of my system files have been changed recently. More corrupt file notices and I'm pretty much backed into a corner here... I turn off and boot up into the Hard Drive Disk utilities... no errors on any scans. I decide to wipe the HD and reinstall Windows, but during the Install apparently some of the files it tried to copy off the disc aren't working or aren't really WindowsXP files even when I know they are... thus I cannot finish the install.

Okay, so, at this point I'm a little miffed. I go out and buy a new CD-ROM drive and a new HDD (taking the other ones out). Install both of those using new SATA cables. I go out and borrow a friend's XPpro CD and I start to install that... This time, it tells me that it cannot copy some files, but after I retry, it changes its mind and copies them and the installer finally finishes... Computer restarts and during the boot-up before even the WindowsXP logo comes up... BCOD (0x0000004F) and happens everytime. Frankly, I can't believe it, how is this even possible?? I wipe the partistion and try my XP Home CDs... same can't copy error comes up but when I switch between the CDs, it finds a way to get them all off and the installation completes and computer restarts... loading past the POST test and... restarts again... into an endless loop of restarts.

Guys, I'm on my last rope here. I'm not gonna have any hair left by the end of this if I can't get this computer working. I don't see how it could be the CD, CD-ROM drive, or the HDD because I tried multiple ones and different brands too!


My beginning setup:

Raidmax Smilodon $90
http://www.newegg.com/Product/Prod [...] 6811156062
Gigabyte GA-P35-S3L $86
http://www.mwave.com/mwave/viewspe [...] ia=BA24072
E4400 @2.0Ghz $119
http://www.mwave.com/mwave/skusear [...] ia=BA23789
2GB Super Talent DDR2 800 $94
http://www.newegg.com/Product/Prod [...] 6820609026
EVGA 7600GT $75
http://www.newegg.com/Product/Prod [...] 6814130062
Lite-On 20X $32
http://www.newegg.com/Product/Prod [...] 6827106070
200GB WD $55
http://www.newegg.com/Product/Prod [...] 6822144416


And I replaced with..

500GB HD Maxtor
Samsung DVD-RW

My first guess would be RAM... if you ran boot a memtest cd and run that and see if you get any errors. memtest86+

/nod chookman.

Download and burn memtest86+. It should boot up and work. It's a very small program and it'll tell you if your RAM is bad. Now just because it might give you a million errors doesn't mean your ram IS bad. Just that the RAM test failed. If it does fail RAM is a good place to start. But don't run out and buy new RAM until you have proven it's your RAM. Try using just 1 memory stick at a time if both fail. When you do the test let it runs until either it fails or 3 full scans. Ideally I start it, let it run for an hour, and if it hasn't failed yet I go to bed and let it run all night.

Also, I think you were a naughty naughty boy! You bought that slick case and used the power supply that was built in didn't you? You didn't list a power supply. I'd try a spare power supply if you have one. It's probably made by the lowest bidder, hence I don't trust it! If it is the power supply, invest in a nice one. I use Seasonic personally.

Okay... I ran the tests on both memory modules and then each one individually... one of them had no errors at all (used the same slot for consistency's sake)... so I guess that means I have a bad memory module!
Wow, what in the heck could cause it to go bad so quickly? I just finished putting this computer together for the first time a little over a week ago. I'll just have to run on one module for now until I get a replacement.


ANd yeah... well, this is my first build and I really didn't realize that I should have gotten a new power supply... that's the first thing on my list to replace because the one they included is just a mess.

Good to hear you got this sorted.

As for it "going bad" youll find that something will either go early or late nothing in between. Just a bita bad luck on yourside.

Excellent... I just can't believe that bad memory caused all those problems... I guess I learned something new today.

Thanks Chook and Cyber... I finally feel at peace with the world.

When a computer works, life is good. When they don't, all hell breaks loose in the universe!!! What a shame that one of the memory sticks went bad. They look like very nice and have good timings (CAS4)!

There won't be these kinds of forums if we didn't have these kinds of problems...It wouldn't be life if it didn't suck at sometime eh

Everything gets written to ram, so bad ram causes all kinds of wacky problems.

Here is an excellent power supply relatively cheap. Notice the original retail price on Newegg.

Silencer® 610 EPS12V Power Supply

Newegg's price

Awesome! Fixed it right up. RMA that bad stick and you'll be set. Glad that your fix was an easy one. As for why it failed so fast the world will never know. It could have been ESD from you handling it, it could have been shipped from the factory that way. The factories' tests are pretty thorough, but it doesn't matter if it works unless it works at your home.

As for the PSU, keep it for now since it seems like it's not causing a problem. But I'd start saving and replace it as soon as possible. No geek in their right mind could resist playing with their new toy even if the power supply sucked . Get yourself a UPS while your at it. It's about as important as the PSU.

Im not entirely convinced its the ram, i am having similar corruption, at least on everything that has a hash or CRC *** with it. The only thing we have in common, the ONLY thing, is our motherboards, we both got the same board from mwave. I kept my memory (which im not entirely sure is good, even though it passes memtest86+) over from my last system and Im getting this problem. Could a motherboard cause these problems? Acknowledging that it is far more likely to be memory, but seeing as how both of us have this problem... let me know if replacing the RAM fixes it please.

Well, it could be that the motherboard is demanding on the RAM, and is therefore causing errors that make it appear the RAM is bad. RAM speeds are very strict nowdays. You get something like 5.5 inches from the cell of memory to the memory controller. If the pathway is too long maybe it's causing problems. Could be interference from adjacent pathways during normal system operation too.

I wonder how MANY splitter the OP used..6 fans on some slitters on one line might make it flake too.