- Oct 10, 2000
- 15,965
- 1
- 0
I've had my duron 800 @ 1000 since I got it. Always ran win2k on it and it never even once hicupped or burped. Temps were OK and I could stress the machine with 3d apps/games and benchmarks and it was always rock solid.
Formatted hard drive, clean installed winXP and immediatly had 2 problems. One was the very occasional blue screen at boot up, and the other is explorer.exe crashing in file manager. Non of the typical freezing and hard crashing in windows usually related to overclocking too far. Just for the hell-of-it, I did a complete clean install again just to make sure it wasn't a fluke, but the same problems existed.
I finally clocked the chip back to it's default and the occasional blue screen at boot went away for good, but still had explorer.exe crash in file manager every once in a while (more of a neusence than anything else, but very annoying).
Finally did yet one more clean install, this time the install was done without the chip being overclocked at all, and wah-la! Everything is perfect. Nothing crashes anymore anywhere!
I should have known better than to install the OS while the chip was o/c'd but there was absolutley no previous indication that the chip was clocked too high.
The moral to my story: Even if you have had no problems with your o/c'd chip in the past with a different OS. Do not rule it out as the root of problems with a new XP install.
I'm just posting this in case it is usefull information to anyone who might be having similar problems.
Formatted hard drive, clean installed winXP and immediatly had 2 problems. One was the very occasional blue screen at boot up, and the other is explorer.exe crashing in file manager. Non of the typical freezing and hard crashing in windows usually related to overclocking too far. Just for the hell-of-it, I did a complete clean install again just to make sure it wasn't a fluke, but the same problems existed.
I finally clocked the chip back to it's default and the occasional blue screen at boot went away for good, but still had explorer.exe crash in file manager every once in a while (more of a neusence than anything else, but very annoying).
Finally did yet one more clean install, this time the install was done without the chip being overclocked at all, and wah-la! Everything is perfect. Nothing crashes anymore anywhere!
I should have known better than to install the OS while the chip was o/c'd but there was absolutley no previous indication that the chip was clocked too high.
The moral to my story: Even if you have had no problems with your o/c'd chip in the past with a different OS. Do not rule it out as the root of problems with a new XP install.
I'm just posting this in case it is usefull information to anyone who might be having similar problems.
Facebook
Twitter