• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Overclocking RAM too far = hdd data corruption??

Zxcs

[H]ard|Gawd
Joined
Sep 11, 2004
Messages
2,007
Well, after trying to push my opterons past 2.7ghz my computer froze and got permanent hdd errors which lead to me having to reinstall windoze. I repeated the same thing twice and the exact same thing happened.

I believe it is the RAM that is being pushed too far but I want to know whether RAM could cause data corruption on the harddisks, or whether it was the harddisks that were getting pushed too far. The data corruption happened without me even writing to the harddisks at the time the computer froze so that puzzles me a little. I am 90% sure its the RAM, but what do you guys think?

Also note: I doubt its the proccessors themselves, as they have sufficient cooling

Thanks, Zxcs
 
Ram sounds like a culprit. Have you tried clocking them at normal speeds? Don't forget to test with memtest too.
 
SATA drives hate to be ran over spec, I had the same problem when I started overclocking. If your mobo had a different set of SATA plugs that use a different controller, switch to those and you should be good to go.
 
Shroomie said:
SATA drives hate to be ran over spec, I had the same problem when I started overclocking. If your mobo had a different set of SATA plugs that use a different controller, switch to those and you should be good to go.

I'm sorry I don't follow you, are you talking about a 3rd party SATA controller? I am currently using the 3rd party one that comes with my mobo (the default is the nforce, I am using the silicon image).

EDIT: If it is the SATA, will putting a SATA raid PCI card in "fix" it? (I have a PCI lock). Also, will standard PCI cards work in a PCI-X slot?
 
The SATA's are on the PCI bus (I believe) which means they do get cranky when you overclock too high. I know on my MSI board, only SATA #3 & #4 are locked and able to use with overclock, but the first 2 aren't (don't ask me why, makes no sense at all why you would leave 2 unlocked). You might want to google SATA LOCK and ur board's model and see what you come up with.
 
the corruption isnt necesarily form the RAM OC....its that when the FSB is raised it also overclocks the PCI bus and thats where you are running into probs. Your ram might be fine (might not) at that speed but if your gettin data corruption its from the PCI bus being too high. All you need to do is make sure you have a PCI lock and ur fine assuming that ur using a SATA controller through a PCI slot and not an onboard SATA because those might not be lockable (they might be locakble tho, 2 of my 4 SATA ports are lockable on my MSI board). Im running at a FSB of 275 and i get no corruption because i properly locked my SATA ports
 
I have PCI/AGP lock. I have 6 SATA connections, so Im gunna search a little and if not I'll swap to the nforce SATA and see if that is locked.
 
It's just poor design imo... On Nforces it's the two on-board SATA connectors that are locked. On VIA boards it's the opposite, the Promise ones perform better when OC'd... No rhyme or reason to it unless I've always understood it wrong.
 
It was the HDDs, I moved them over to the nforce SATA controller and it fixed my problems, finally hit 2.75ghz on my optys.... now to unlock the memory divider on the nforce3 =)
 
Back
Top