Just installed a new 8KHA+ with Athlon 900 and 512 mb DDR. Everything was working fine until I started overclocking. I happily ran Sanda burn-in overnight, but when I rebooted, I got a blue screen with a corrupted WINNT\SYSTEM32\CONFIG\SYSTEM file. After much frustration with Win 2k emergency repair, I reloaded the system from scratch and Ghosted the partition.
Again, everything was fine until I cranked it up the clock multiplier to 10.5 and tried some more aggressive timings with the DRAM. Same story - burn-in and other programs ran fine until I rebooted and got corrupted system files.
Fortunately I was able to restore the partition with Ghost and was back up fairly quickly. All is fine now at standard settings, but where's the fun in that?
I just read the thread about turning off UDMA in the bios and will try that. Does anybody have any other ideas why disk would get corrupted by overclocking?
Again, everything was fine until I cranked it up the clock multiplier to 10.5 and tried some more aggressive timings with the DRAM. Same story - burn-in and other programs ran fine until I rebooted and got corrupted system files.
Fortunately I was able to restore the partition with Ghost and was back up fairly quickly. All is fine now at standard settings, but where's the fun in that?
I just read the thread about turning off UDMA in the bios and will try that. Does anybody have any other ideas why disk would get corrupted by overclocking?
Facebook
Twitter