But, there is a huge difference between the Sandforce issues and what you are talking about. You are talking about overclocking which by definition is trying to run the hardware outside the limits the manufacturer promised you when they sold you the hardware.
not really all that different when you consider that many who have issues on these platforms ARE actually overclocking(otherwise, why buy an unlocked processor, right?) and are subsequently lumping any little glitch into the Sandforce mess. I've seen dozens and dozens all around the net who adamantly denied that it could possibly be the mobo/cpu(and yes.. some even swapped these SSD's in and out like you too and came to that same assumption). Guess what?.. they later realized that there are many variables added with overclocks and ultimately find out that it was not actually the SSD's(or even HDD's as some never even had SSD's installed) fault in the end. Just a mass assumption going on that any instability HAS to be the SSD. Many find otherwise, is the point.
OK now, so I change out the OCZ Vertex 3 with another SSD or HDD changing nothing else and my system becomes stable and it is my drivers, Bios settings, MB, etc. that are causing the problem?
I don't quiet follow your logic!
yeah, you and hundreds of others out there apparently. Read the mobo mfgrs forums(even the other SSD mfgrs forums) to realize that not all with similar symptoms to these are even using SF-2281 controlled drives to begin with. Again with the assumptions and lumping of issues.
Ever stop to think that maybe some have not implemented the latest sata specs appropriately? Why did Intel push so hard to implement specific APM features into the sata3 specs and then end up disabling some of those very same features on their own drives?
Even more interesting is the timing of these particular fixes when Intel is about to release their SF controlled drives. Who'da thunk that Intel had that kind of power? Major sarcasm intended there. Fact is that all the other workarounds that were implemented by the few percent of users who could not find stability no matter what firmware revision they tried.. were able to actually work through the issues. Of course there were(are) still those out there who did not find stability no matter what they tried with any firmware revision.
We can play ping-pong all day long but the reality is that if an OROM, a new IME driver, or forcing the registry to see the port the SF SSD is connected to.. can bring about stability?.. how can that be entirely the firmwares fault? So, in the end here?.. everyone is just working around everyone else's workarounds is all that it really amounts to.
In a nutshell.. there are and have been continuing issues with these newest platforms and the sheer volume that the OROM's, drivers, and even Windows hotfixes, have been progressively modified should be enough of a clue to see it. If you don't?.. then you must not be reading enough.
When even an HDD gives issue, c-states are slowing transfers using various SSD controllers, or ram has to be completely swapped to another mfgr to regain system stability?.. there are certianly some other underlying issues that have absolutley nothing to do with Sandforce going on here.
2600K on a MIVE-Z :thumbsup: Stock Voltage, 4.5GHz IBT stable.
good for you... but if you visit the mobo mfgrs forums you'll surely see some who are not so fortunate. It's pretty well known by now that sub-1 Volt idles are giving many issues and forcing static VCores or using the correct offsets can make a world of difference. Hopefully X79 will make use of many of these mistakes and make those upgrades a bit less painful for some who jump to them right away.