- Joined
- Mar 13, 2002
- Location
- The Big Easy
Ok here is the facts.
Had system running stable at 2.138 with 118fsb. Then had fatal error on hard drive. So, I thought the hard drive was bad. Call WD and they sent me out a new one, cause mine is under waranty.
Intstalled the new one, with my old WD as a slave. Transfered all my data. Decided I would try to overclock it again. Got to 118fsb and 2.138. Very stable, no heat probs. Let it run like that with both WD's for about 6 hours. Decided everything was fine, would uninstall the old WD and put in my IBM, which is just a backup drive. Shut down computer, pulled out the old WD and put in the IBM as a slave. Rebooted, FATAL ERROR, BLUE SCREEN. Had to bump my CPU back down to stock and reintall Windows XP.
Windows installed fine, now I am at stock speeds and everything is ok.
What could have caused this, btw the WD and the IBM are ATA66 7200RPM Drives.
Had system running stable at 2.138 with 118fsb. Then had fatal error on hard drive. So, I thought the hard drive was bad. Call WD and they sent me out a new one, cause mine is under waranty.
Intstalled the new one, with my old WD as a slave. Transfered all my data. Decided I would try to overclock it again. Got to 118fsb and 2.138. Very stable, no heat probs. Let it run like that with both WD's for about 6 hours. Decided everything was fine, would uninstall the old WD and put in my IBM, which is just a backup drive. Shut down computer, pulled out the old WD and put in the IBM as a slave. Rebooted, FATAL ERROR, BLUE SCREEN. Had to bump my CPU back down to stock and reintall Windows XP.
Windows installed fine, now I am at stock speeds and everything is ok.
What could have caused this, btw the WD and the IBM are ATA66 7200RPM Drives.