RAM or Mobo?

[Dominion]

Hi - having a major problem

Abit AN8 Ultra
2x512 Ballistix Ram
AMD Venice 3200
500W Enermax Liberty
XFX 7800GT

Hi when i first built this i had a problem with BSOD - after a little reading i reseated the RAM into other slots and its been fine for 3 months or so. Even with heavy gaming in BF2.

I just bought another 2 sticks of RAM - same kind (2x512 Ballistix PC3200) inserted them (knowing there might be a reoccurence of the original problem). And yes BSOD. So i took them out but the PC still crashed with the original RAM. My windows installation got corrupted.

Using memtest i tested each one and only got errors on one stick - however after reinstalling and using the sticks that passed memtest, the windows install has again been corrupted beyond repair.

So mobo to blame?

I have put the RAM sticks in my works computer - do you recommend the Windows diagnostic tool over Memtest? With the windows tool it can tell you which module the faults are in - not sure how accurate that is though.

Thanks

[Dominion]

ok have tested RAM using both memtest and the windows memory diagnostic on my works computer. No problems.

However my home PC won't even post now. I used the one stick of RAM that was in my works computer to test it.

Looks like mobo was twitchy with RAM to begin with and has decided to completely pack up.

[Panama Red]

Did you record the exact message displayed with the BSOD? Would be nice to know what it said. Memtest.org is the preferred version to use for testing newer memory. That is Memtest86+. Corrupted XP smells of hard drive problems. I'd suggest testing your hard drive with the manufacturer's drive fitness software. Check the hdd brand and download the software from the manufactuer's site. Or you can consolidate all your testing needs and download the Ultimate Boot Disk. It has all the hdd testers and Memtest86+ plus a whole lot more.

[Dominion]

For the BSOD i had 2 types

One was a general warning - windows is shutting down to prevent damage, remove any new hardware etc, physical memory dump. (So i immediately suspected the new RAM)

The other said something like 'irq not equal'

******

Then when i booted i had windows config file missing and when i tried to repair it said it was unable to.

I will be doing an out the box from scratch rebuild.

If you take the CPU off will it stick to the heatsink or do you need to reapply heat compound?

[Panama Red]

If you take the CPU off will it stick to the heatsink or do you need to reapply heat compound?

Once the heat sink clamping mechanism is released, twist the heat sink back and forth CAREFULLY until it releases from the cpu. You'll need to clean the compound/pad off both surfaces and apply new compound or a new pad before reinstalling.

[Dominion]

Thanks. The seller sent me a list of instructions to follow but i will leave the CPU attached for the out of box test.

[Dominion]

ok quick summary after the above

*Tried to boot PC one last time but no post and error 0.4
*Pulled it all out and rebuilt - it worked. Even booted when before it had said it was corrupted.
*Tested 2gig (4x512) RAM with 2 passes of memtest, took just under 2 hours - no errors
*Tested Seagate SATAII 80gig with seatools - no errors using full scan BUT it reported errors in the file structure. used CHKDSK /P and there was errors, strange as it was fresh install. fixed using FIXMBR
*Now seems to be running with all drivers installed. However did freeze once on boot and i when back into repair console and ran chkdsk /p. again errors and fixed using FIXMBR.

I do feel like its going to crash at some point

I read this http://forum.abit-usa.com/showthread...=0.4+post+code

Seating new RAM flexs the board so you don't get a proper contact? hmmm

[glc]

Try chkdsk /r next time.

[Dominion]

yeah that seems a good command to remember thanks.

However still problems that go beyond chkdsk capablities.

I ran Prime95 torture test for 9 hours and got no errors. I ran memtest again for 8 hours just to check and got no errors. Thought everything was fixed and stable.

Rebooted later on and got 'windows can't load because config file is missing'.
Tried to repair and there was lots of files it could not copy or delete.

So maybe it is the HDD but Seatools gave it the all clear.
Maybe a corruption on the SATAII interface? Strange that HDD worked till i added new RAM. Or could still just be the mobo?

I will retest HDD with seatools and use my old IDE HDD for awhile and see if it gets corrupted.

[Dominion]

Been using my old IDE drive for abit and it works. Did some gaming in BF2 and no crashes. Its abit slow compared to the SATA though.

Ran Seatools again an no errors in the hardrives - again just the file structure on the SATA.

Right now i have the IDE as main boot with the SATA connected. Every boot its tries to run chkdsk on the Seagate to repair the file index - usually fails.

So i read that IDE and SATA access memory differently. If i can trust Seatools i have a motherboard problem. Will try and contact Seagate and see what they say though.

[Staren]

Have you tried moving the seagate to another SATA port on the motherboard? If it's stable there you might be able to rule out a bad port at least. Also, have you tried googling your RAM with the motherboard or the RAM with that hard drive? There might be a known problem. As a last resort, there is a hard drive tool called SpinRite at www.grc.com It's $89.00, but if all else fails it might be able to tell you whats goiing on with that drive.

[Dominion]

Hi - yeah tried all 4 sata ports with no joy and a fresh cable just in case.

Seagate have told me to RMA the drive even though it passed Seatools full diagnostic. As my IDE drive is working in the system they think its most likely the drive.

I not convinced as it all went crazy after i installed new RAM but i've nothing to lose so i will RMA the drive. Then can replace the mobo after depending on the result.

[nu_1]

Did you find out the source of your problems yet?? Solutions??

Most of your symptoms I also have, so Im interested. Im gonna have to open a thread and hopefully Ill get some help.

[gary_hendricks]

I still think it's a motherboard / RAM memory module problem.