Overclock corrupts OS?

[veggz]

Is it possible for an overclock to corrupt the OS and prevent it from loading? I had an incident yesterday that forced me to reinstall my entire HD and was wondering whether OC'ing may be to blame.

 

[richardrds]

yeppers, if you push it too hard you could corrupt the bus and data that your HDD is using. This is why it is important to have working AGP/PCI locks, and SATA locks on your mobo!!

 

[stevty2889]

Yes, an unstable overclock can corrupt the OS. All it would take is a couple of memory errors, writing to incorrect spots on the hard drive, or if you had SATA drives, and no SATA lock, overclocking the SATA bus can also cause data corruption.

 

[veggz]

Ah.. good to know thanks for the replies. I have a DFI UT NF3 250GB MB, do you guys know if that has SATA locks on all 4 drives, just 3 and 4, or not at all? I am a bit wary of OC'ing again since this entire ordeal has just been a big hastle reinstalling everything. If my OS is installed on my SATA drive can I overclock safely without worrying about something like this happening again assuming it is hooked up to a port with a lock? Or is the possibility still there?

 

[icejunkie]

Same board as me. Also wondering if it has AGP/PCI/SATA locks? Also, should I set AGP to 67 or leave it at 66? Thanks...

 

[Tarrant64]

I think it needs to be at 67. You should check the forums. I believe zebo or someone has a post on how to do this. The DFI is the best board for OC'ing, so if your having problems it must be related to something not being set right. It does have AGP/PCI locks, and as from what i've seen, the SATA should not corrupt at all either.

 

[JBT]

According to Anandtech's review of the DFI board IF you OC you should use ports 3 and 4.

 

[imported_NoGodForMe]

That's why most use Memtest to make sure everything is stable.
It boots from a floppy or CD. When you get errors in memtest, back it down a little, run a few passes, then boot into your OS.

 

[Jhatfie]

I did not corrupt my OS, but I corrupted my 2nd hard drive the other day when testing my A64 3000+. Hit 2.88ghz, but my memory was running beyond it's stability limit and caused my system to crash. Upon reboot, my D drive was corrupt and unusable.

 

[veggz]

Well I'm playing it safe now, I got Norton Ghost, Prime 95, and Memtest, switched my SATA drive to port 3, and backed off a little on my OC. I had no idea overclocking could screw your HD so badly. And what is this with setting AGP to 67 instead of 66? Why do you do this and does it make a difference?

 

[n7]

I believe it's because technically the AGP bus is at 66.6 not 66, so 67 is the next up which activates the lock?

I could be wrong though.

 

[CKTurbo128]

Yes, a very unstable FSB overclock can corrupt the OS. Like NoGodForMe recommended, you should test the overclock in Memtest86+ for stability before you ever boot into your OS. I once made the mistake of not doing that and corrupted my Windows XP installation, which could not be fixed, except by doing a reformat. 🙁