• 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.

SSD Overclocking

I can't think of anything I would want to overclock less. My two cheapo SSDs in RAID0 are maxing out the Southbridge already, and just imagine the data corruption.
 
I don't think its any different to any other component. If you overclock your RAM or CPU then you have a decent chance of silent corruption for files written the drive, which is happening all day long. You are already taking a risk with every file, I don't think that changes just because you are overclocking the storage itself.

What I will admit however is its a hard component to overclock. If you push the CPU too far you should see it in stability testing and hopefully no files are corrupted. But an SSD has to presumably already have the OS installed and then you start overclocking it and what happens?! Almost always we push past the limit to find where the limit is, with an SSD that could end up in a reinstall or silent corruption while we are trying to work out if its stable or not.

Despite those challenges it doesn't sound all that ridiculous, but I think the sentiment that its one component too far is going to be common amongst people, if nothing else because we haven't been able to overclock our storage devices at all so far.
 
I don't think its any different to any other component. If you overclock your RAM or CPU then you have a decent chance of silent corruption for files written the drive, which is happening all day long. You are already taking a risk with every file, I don't think that changes just because you are overclocking the storage itself.

What I will admit however is its a hard component to overclock. If you push the CPU too far you should see it in stability testing and hopefully no files are corrupted. But an SSD has to presumably already have the OS installed and then you start overclocking it and what happens?! Almost always we push past the limit to find where the limit is, with an SSD that could end up in a reinstall or silent corruption while we are trying to work out if its stable or not.

Despite those challenges it doesn't sound all that ridiculous, but I think the sentiment that its one component too far is going to be common amongst people, if nothing else because we haven't been able to overclock our storage devices at all so far.

I remember, back in Celeron 433 days -

Overclocking via the FSB also raised the PCI clock too (up to 41Mhz in my case), affecting the IDE controller. In that state I made a backup of all my files onto a second drive, formatted the sys drive and reinstalled Win98. Access the backup - the files were all there, but every single one of them was corrupt and unusable. A total loss. Hard lesson on overclocking and backup.
 
Back
Top