It’s true that SSDs tend to just die without warning, and most appear to fail when first powered on. However, failure rates are exaggerated to a large extent.
I closely followed the SandForce SF-2281 BSOD, and from what I saw, anyone who had a BSOD and happened to have a SF-2281 based SSD automatically blamed the SSD for the BSOD. I also followed the manufacturers support forums during this period, and most of these problems turned out not to be the SSD, but in actual fact a system stability problem or a driver based problem.
Most people still blame only SandForce for this problem, but I will stick to the facts here on how it was fixed, at least for the vast majority of SandForce users.
99% of these problems only manifested themselves on Intel based chipsets, AMD chipset users were almost untouched.
Several Intel chipset “SATA option ROMS” were updated, not only once, but it was more or less a monthly event. The same applied to the RST driver versions. This cured about half of the remaining problems.
Intel chipsets from P55 to Z68 had a power management bug, which still remains unfixed.
SandForce released several firmware updates to address the problem, with varying success. The big firmware fix for the BSOD problem came just after Intel launched the 520 series, which was also accompanied by another SATA option ROM update. Coincidence?
Here are some bugs with SSDs that I can name from the top of my head, most have been fixed by firmware updates.
Data corruption when the volume is nearly full. (Fixed with firmware 1.70)
Intel G1 and G2, bricked when a security password was applied (fixed)
Intel 320 series 8MB bug which reduced the volume to 8MB (fixed)
SandForce SF12xx sleep bug which sets the drive into panic mode, requiring the SSD to be replaced (still unresolved)
Crucial M4 5001 hour bug, when the SSD clocked up 5000+ the SSD would fail. (fixed with firmware update).
Crucial C300 and M4 LPM issues, which can cause the SSD to just drop out (in most parts fixed, but Crucial still recommends that LPM (Link power management) is disabled.
Samsung 830. When the partition is GTP, the Magician software corrupts the volume. (fix use MBR instead).
To finish and get some things into perspective.
Here is list of the SSDs I have, starting with the oldest first.
OCZ Core V2 60GB (JMicron) No problems.
OCZ Apex 120GB (JMciron) I have two of them and one failed. The other has no problems
Intel G1 80GB No problems
OCZ Vertex 120GB (Indilinx Barefoot) no problems
OCZ Agility 120GB (Indilinx Barefoot) No problems
Crucial C300 128GB (Marvell) no problems
OVZ Vertex 2 100GB (SandForce SF12xx) no problems
OCZ RevoDrive X2 240GB (4X SandForce SF12xx on a PCIe2 x4 card) no problems
OCZ Vertex 3 240GB (SandForce SF2281) no problems
OCZ Octane 512GB (Indilinx Everest) no problems on SATA3 but drops out of SATA2 on Z68 chipset.
Intel 520 240GB (SandForce SF2281) no problems on Z77 chipset, but drops out when connected as a spare on Z68 chipset.
OCZ Vertex 4 512GB (Indilinx Everest 2) Pre production sample was bricked by trying to flash production firmware) ooops The replacement has no problems once the buggy 1.4 firmware was updated.
SanDisk Extreme 120GB (SandForce SF2281) no problems