Last year, I posted asking for help because of random reboots I was experiencing after installing a new motherboard, replacing one which had accidentally lost a capacitor. The problem turned out to that the RAM timings were set wrong. However... I fear the first motherboard's demise may have affected my hard drives... When I first installed the new MB, I got occasional BSOD's, (except these used the Tahoma font, and didn't have the same header as the standard BSOD) during bootup. The screen would flash out so quickly I could never quite read what it said. Thinking the capacitor incident had damaged my hard drive, I replaced it with my slave drive, and did a fresh XP install on it. The first time I tried to install it, it also gave me that non-standard BSOD. After a second try, the install went through. Throughout the year, I've experienced occasional random reboots. They sometimes happened while playing a game, or sometimes by doing something as simple as trying to access the history files in my Yahoo Messenger. Other times, trying to run a Quicktime movie in full screen would do it. In fact, trying to install Quicktime in the standard directory is a surefire way to make the system reboot. I had to install it on "Crogram FilesQT6", which makes me think maybe I do have an accute case of bad sectors. Anyway... Last month, the random reboots increased a lot, it wouldn't be odd to have it happen five times in a day. I uninstalled the latest video drivers I had (which Windows hadblamed for one reboot), and all seemed to be well, though I'm still not sure they were directly related. Yesterday, my chipset fan died on me, and after I put the system back together after replacing it, it booted up fine but treated most of my hardware as if it was new. Fine. I let it reinstall drivers for most components, but it didn't install the driver for my network adapter. I got out my drivers disc and tried to install it manually. It wouldn't "see" the XP driver file. I ran the setup utility, which caused the system to reboot immediately after it was finished. Then... The system wouldn't recognize my slave drive, and wouldn't even finish the bootup sequence (sometimes it would flash the BSOD and reboot, other times it would get as far as the welcome screen, other times it would simply go blank). When it does boot up, it's not long before it fails again. At some point, it went back to identifying my network card as new again, and this time it did install the driver that came with XP. The system is pretty old (Athlon 1.4 Ghz, 256 MB RAM, GeForce 2 MX card), but I simply can't afford to buy a new one right now. I'm thinking I'll have to buy a new HD, but I thought I'd ask here first, in case anyone has any other ideas as to what may be causing this problem. Thanks in advance for any help.