I'm 99.9% sure it's not the memory, please advise.

[Dustworthy]

Has short as I can tell this story, please bear with me:

MS6712 KT4V MB
AMD Athlon XP 2800+
512 (2x256) Kingston RAM (PC2700)

Windows XP Pro could not install. It would return 'cannot copy file' or 'file on HDD not a valid WINXP image' etc. I ran memtest86 to check the RAM which scored 75,000+ errors. I swapped out the RAM with known good Corsair XMS RAM (PC2700) I use in another system which also uses a ms6712 KT4V / Athlon XP 2600+. The problem did not follow the RAM which tested with 0 errors in the other system. The errors stayed with the 1st PC now with Corsair RAM. I've tried a couple different PSU's, two different hard drives, two install CD's, two CDROM drives and more IDE cables than you could shake a stick at. I even changed the vid card just on general purposes. I disable all the onboard stuff not needed to install WIndows. Mem timings are contorlled by SPD.

I reduced the FSB from 166 (333) down to 100 (200) and it tested with 0 errors. As I increase the FSB the number of errors grows exponentially.

I am reasonably convinced now that the problem is between the CPU and MB. I would like another opinion before I go any further. I only have one other CPU (2600+) that supports 333 mhz buss. It is busy in the other system but I suppose I'll end up pulling it out to try. Or is the MB the most likely suspect? Or am I just clueless

I would greatly appreciate any comments or suggestions.

[icecube]

I had a manufacured cd that would not install with the same sort of problems. The cd had been used before by me on his other system and worked ok. An XP pro disk of mine installed perfectly, I suggest you try another O/S cd first. Also check to see that the disk is clean and not cracked near the center. One bit of goo the size of a pin head can render a disk unusable.

On the motherboard, look for oozing capactors or one that has been knocked over .

Some of them stick so high up, that you can ruin the board just slidiing in a cdrom drive.

[Dustworthy]

Thanks.

I left out that after I discovered there were no memory errors at 100mhz FSB I tried to install XP and it was completely successful. So XP is now installed but it's only stable at a fsb below 266mhz. It runs at 266mhz but with frequent "program x has encountered an error and must be close". at 333mhz it blue screens and restarts just after POST. It won't go to safe mode either.

[icecube]

Try downloading the Belarc Advisor, here is a link



You might have a jumper set up wrong, this freebee will give you your cpu settings and part of the fsb reading and the bios version.

If everything is ok, it could be that you need to flash the bios with the latest update.

[Dustworthy]

Wow! OK I got it fixed. Turns out it was the CPU. I've never encountered this problem before with a CPU so it really kick my tail for a couple days. My new Athlon XP 2800+ absolutely will not run stable on a FSB above 200mhz (0 errors with memtest86+ at 200mhz). At 266mhz FSB I'd get about a dozen errors (one pass) at 333mhz fsb it returns thousands of errors.

To make a long story short I tried a 2600+ in this system and it worked flawlessly. At the same time I put the 2800+ in a different <known stable> system and the problem followed.

Thanks for your replies.

[icecube]

you still might check for a bios update for that motherboard. I've had several installs where you had to flash the board for it to see the newer faster cpu's.

[Dustworthy]

The bios version installed is dated 11/04 and is the most recent revision, thanks. I know what you mean though. I had to flash before changing the CPU in a system once. As a general rule though I flash a bios to the current version 1st thing when installing a new MB.

[icecube]

If you bought it as a 'boxed' cpu, you should be able to RMA it to the manufacturer.

Three year warrenty--with AMD. Make SURE that you tell them that it was installed according to specs with their fan.

You mention you used Arctic Silver and/or a better fan your warrenty is void