My first problem with W2K

[jkersenbr]

Well, it finally happened. After 6 weeks with absolutely no complaint, Windows2000 barfed.

I got a new CPU today and installed it. Booted up -- no problem. Overclock -- booted up no problem. Shut down for dinner. Come back after dinner. System hangs before brining up the login screen.

So I tried a fast emergency repair. No difference.

So I reinstalled a backup image. Now it works.

What happened? Is 2000 really this stupid regarding CPU changes? Just looking for some info.

Thanks.

 

[SoyBoy004]

overclocking alone could be the problem. check your ram, voltage, and cpu speed. perhaps its unstable.

 

[jkersenbr]

I seriously doubt it.

I purchased a slot 1 SL3V5 550e tested to 770 with default voltage and guaranteed to 733 with default voltage. I bought it with heatsink and fan attached.

At the time of the W2K brain fart I only had it running at 605.

This CPU is solid.

 

[themadmonk]

Yeah but if after Recovery you are still having problems, the odds that it is OS based has just been reduced drastically.

 

[jkersenbr]

But it is running (now) without problems since I restored from my backup. Doing the "emergency repair" is what didn't work...

 

[Dually]

w2k is a lot more picky about overclocking. It is inpart that it utilizes the cpu more than 9x. Just like Unix w2k doesn't like overclocking much.

 

[AngelOfDeath]

Well I can't exactly tell you what went wrong and why it did so, but my experience tells me that every time I change a hardware part in win2k the best thing to do is to reinstall . If I don't it makes all kinds of errors or become slow.

As I said it's only my experience, nothing more nothing less. But in the end it might be the fact that I just don't know enough to get past these problems whenever I install a new hardware part in to my computer

AoD

 

[owensdj]

jkersenbr, what probably happened is that your overclocking attempt corrupted something in the Windows 2000 install, maybe the Registry.

 

[Wik]

Win2K is very touchy with overclocking. If it is running now and continues to do so I would not worry about it. Owensdj is right that you may have corrupted a part of the OS. I have had it happen a long time ago but have not seen it happen in about a year.