• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

why does my sata hdd get corrupt from o/c???

A

AssyrianKing

Member
hey guys it seems when i overclock my a64 3500+ to around +20 or more fsb (htt) my OS wont load stating my hdd is corrupt or something and dll files are missing. surely enough my sata hdd does get corrupted as i slaved it and some fodler dont open as they state there corrupted or lost, but the files are intact and recoverable with a program.

i have also herd about this corruption from another user with my same mobo. my sys specs are in sig.

also i want to know what setting to set my pci/agp locks when overclocking on my system? theres like 2 options > 66.66/33.33 or 75.4/37.7 i do not know which 1 to use? can someone explain the difference and what they do? thanx!!!
 
Your sata hdd probably does not like an overclocked pci bus. You should stick with 66/33 as those are the correct speeds for your agp/pci buses respectively. Of course, a number of k8t800 boards don't have working agp/pci bus locks, so using the correct setting may not help if the lock is broken. Make sure you are using the latest bios and cross your fingers 😉

Edit:
Here's the link that talks about which revisions have a working lock (hope you have revision 2.0).
 
Apart from the overlcoking of the BUS, even just overclocking CPU and/or RAM can cause filesystem corruption.

You have to know that a large part of RAM is used as a buffer cache for the filesystem. If you have random memory cells turn their contents behind your back due to memory corruption due to overclocking, then in worst case the information where a disk block belongs is corrupted.

That means when such a disk block in the buffer cache is written to the disk, then it is written to the wrong place. If you are unlucky, then the new place is where a directory or an allocation table lives and then you wipe all kinds of files you didn't even touch during your work session. If you are very unlucky, you wipe out disk blocks critical for mounting the filesystem, making the OS unable to access the filesystem at all.

Reminder: all that even if you don't overclock anything related to the disk itself (bus etc). Just "normal" memory corruption in CPU or RAM.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top