I actually removed the IDE drive from my Dell, complete with functioning XP installation, and put it into the AMD box, with no result.
Yeah, this definitely won't work. Even if your copy of Windows doesn't require Activation (which wouldn't stop it from booting anyway, it just wouldn't let it run if you didn't re-activate), you can't load an Intel install of XP on an AMD system. Mostly, it's the chipset drivers, but in that case the processor differences would probably crash it too. Actually, it won't even work if you move a nForce3 system to an nForce4 system (though usually nForce3 --> different nForce3 will work).
Yes, I unplugged everything I could, including extra USB sockets etc., so it would seem that it can only be the CPU or vid. card - or the power supply, except that the shop who checked it seemed to think it was ok. I'm just hoping it was the SATA drive...
I'm actually pretty well experienced with building AMD systems (I should be, I've built about 10 of them). If it were the Video card you probably wouldn't be able to get the system to POST (you'd just get a weird series of beeps and no BIOS). I've fried a video card or two in my time and they generally are just dead (or they won't work in games, but load windows fine). Power supply is possible, but if they checked it it's probably cool (plus, flaky PSUs tend to cause really RANDOM crashes, which would mean you'd probably eventually get through the XP install after a couple of tries, only to have it BSOD on you randomly when running). Could be a bad CPU I suppose, but I haven't seen or heard of too many of those floating around (AMD's QC is pretty good). A couple of questions...
1. Where did you buy the stuff? Particularly the CPU and Memory. Are they reputable? (There have been cases of bad merchants selling overclocked and/or fake Athlon 64's as the real thing).
2. What brand/model of RAM is it? It's really almost definitely RAM if you're satisfied that it's not the board. It could also just be a RAM <--> motherboard incompatibility. Bad RAM is all too common, especially the cheap stuff.
3. Are you REALLY sure the MSI board was broken too? I just ask because I am
right now having all my trouble with a Gigabyte nForce3 board. I usually buy ASUS (the talking ones mentioned above) but they didn't make a s939 nForce3 board (only a VIA which I will
not buy) and I have an AGP video card. I've heard since that both MSI and Gigabyte are notoriously finicky about RAM -- though not as bad as DFI.
4. What kind of video card exactly? There were some weird nForce4 install problems with some video cards, though those should have stopped you the first time you tried, not just this time.
I have had EXACTLY the problems you describe myself with bad RAM, random errors at all parts of the XP install (though sometimes they seem to always be around the same place).
The best thing to do would be (in my opinion) test the RAM, and if that passes, run Prime95 on the thing for a day or two.
Go here:
http://www.ultimatebootcd.com/And download the current version (3.3 -- basic is fine) and make one. Then...
1. Disconnect everything you don't need from the Athlon system, including hard drives, external devices, sound cards, etc. You want just the computer, RAM, Optical Drive, PS2 keyboard, video card, and monitor. Period (no, not even a mouse).
2. Boot to your BIOS and
load optimized defaults and Save and Exit. Go to the BIOS again (doing this separately is probably just paraniod) and go through the "Integrated Peripherals" section too and disable the LAN devices and Audio options. Lastly, make the CD-Drive your boot device.
3. Then boot the Athlon system up with the disc in the drive.
4. Once the Boot CD loads, hit F1 to enter the "Mainboard Tools" section. The way UBCD works is that you use the F# keys to choose an option, and then there's a way to page through different screens (I can't remember that command but it's like PageUp/Down or Enter or Space or something easy). Anyway, run Memtest86 (the non + version is fine) from the first page under Mainboard Tools.
5. Let it run for a LONG time (at least 6-7 passes, each of which is comprised of many tests -- I'd go to bed). If you have any RED errors show up in the bottom half of the window, you've got RAM problems (probably, though it could be the memory controller in the CPU or the motherboard is broken/incompatible). It still strongly indicates that the problem is RAM.
6. If it passes that, then I'd run Prime95 on it for a full 10-16 hours (that's the Mersenne Prime Test also on the first Mainboard Tools page). This doesn't have much of a UI in the Linux version included on the UBCD, but it works. Basically, you should see a list of different tests which say they passed and then start the next one. You hit Control-C to stop them, and then it will report if there were any errors. If there are, then this is a good indication that your computer isn't doing Math right (which really is it's primary function), which is often either the Motherboard (specifically the Northbridge) or the CPU. Sometimes it's the RAM too, but that's why I test the RAM first with Memtest. (BTW, this app is why I specified PS2 Keyboard and no mouse. It seems to dislike USB stuff intensely in the UBCD version. It works fine with PS2, but will crash if you have a USB keyboard or mouse).
Those two steps are always the first things I do when I build a new rig (but only after pulling my hair out with problems like yours on a bunch of builds). Get the hardware confirmed stable before you even put Windows on it and it can save a LOT of grief.
If you do those things and then post back what happened, I can probably give you some pointers on what to do next. If you do get Memtest errors, then you probably want to try having the stick tested on another, known-good machine (preferably using Memtest there too, maybe the nice PC shop will help). If not, but Prime95 fails, then I'd look at the CPU and Motherboard harder. If neither fails, then it could be just a bad drive.
Either way, Diskkeeper probably didn't cause it. That might have caused the filesystem to corrupt itself a bit, but it couldn't really have cause physical damage to the disk (not likely anyway).