Ok, I'm just having one problem with Windows 2000, albeit a fairly large problem. For some strange reason Windows 2000 decides to reboot itself at random times, usually after a few hours of operation. 98SE didn't have this problem, although I know the OSes are totally different, if it had something to do with my overclocking, I would think 98 wouldn't be stable either, so I ruled that one out for now.

Pupstah,

I wouldn't rule out overclocking just yet. I think W2K is much less tolerant of timing issues that arise out of overclocking than Win9X. Why don't you try running at "warp 1" in W2K and testing to see if the random reboot goes away. I know it's not what you want to hear, but I think it's the likely cause. I've seen eight overclocked dual-boot systems personally so far that ran Win9X or WinME flawlessly (or as flawlessly as those operating systems allow) but which either rebooted or blue-screened in W2K. (The BSODs were apparent driver failures that went away as soon as the overclocking ceased.)

Regards,
Jim

Hmm, I was informed on another messageboard that the reason it reboots automatically is because I had that setting on when it does a memory dump during a Blue Screen O' Death. Now to figure out what's causing the BSOD... I was informed that I could be advanced power management, so I turned most of that stuff off in the bios. It could also be because I was running my PC133 ram at CAS2 when its only rated at CAS3 (although, I don't know about this, its rated for 133, but my memory bus is only running at 100). Anyway, next time (if there is one, I turned the CAS to 3 and turned APM off) It will show a BSOD and I will write down what it says.

Pupstah,

Yes, that's true. If you had the setting checked to reboot in response to a system failure, that's what it would do. Since you didn't mention a BSOD in your original message, I just took it for granted that you meant a reboot "out of the blue", so to speak. My bad.

;-)

That type of random reboot is usually due to memory errors or power supply issues in my experience, hence my suggestion to back off on the clock speed.

If you get a BSOD I'd like to see what it was. Also, have you checked the Event Viewer for error messages, just in case there's a hint of something in there that happens just before these BSODs? Sometimes you can get a clue from those logs.

Regards,
Jim

Well, it's been three days now, no BSODs... It may have been solved by any of these three things I did.

1. Changed ram timing to CAS3.
2. Turned all APM stuff off.
3. Installed new SBLive drivers.

And I do remember something, this problem used to happen on my old motherboard as well. I'm not totally ruling out the problem yet, maybe after it runs for a good week or so, then I'll say its stable, but it looks good for now, been through games of Diablo II, NFS5, and Red Alert 2 with no probs.

That's good news. Hope to hear that this condition continues.

Regards,
Jim