SandForce Random BSOD Firmware Bug Identified, Fixed

Toggle sidebar Toggle sidebar
Status
Not open for further replies.
Finally! If Indeed this solves this LONG standing issue, I would happily purchase a Sandforce based drive!
 
[citation][nom]gogogadgetliver[/nom]How could they fix this if they already fixed this? Sick of Sandforce and frankly I no longer trust them. I RMA'd.[/citation]
Don't be so paranoid : ) Look what happened to Sandy Bridge, its piece of electronic. Happens all the time.
 
I've owned a SF2000 Corsair Force 3 120 since June. I was relieved to see they finally have fixed the issue. My BSODS' and freezes weren't very frequent, but they did happen. Nice to know I can update the FW and not have to worry about this anymore! About freakin time!
 
[citation][nom]nikorr[/nom]Don't be so paranoid : ) Look what happened to Sandy Bridge, its piece of electronic. Happens all the time.[/citation]

If this was a one-off incident I would possibly be guilty of paranoia.

If I've experienced data loss, multiple return hassles, and multiple promises that things are fixed and I continue to have faith then I would be guilty of being a fool.

They are fast drives and I hope everyone enjoys them without problems. I'll sit out this round and skip the SF-2281. I'll revisit Sandforce once they have a proven track record.
 
I'll be happy if this actually fixes it. Luckily my BSODs haven't been too often--only gotten 2 in the 3 or so months I've owned it. But it will be nice to not have to worry about it.
 
Finally! I've been reading about those dreaded bugs for months now... I have been holding on getting an SSD partially for that reason...

So, the big questions here are:

1) Has anyone already tested this? If so, how did the drive fare?

2) Do SF-based SSDs finally replace the current "go with m4/Intel/Samsung 830" general rule of thumb people have been telling me for a few months already? Or are there other problems these SSDs have that might not grant them the top spot on price/performance/reliability?

Miguel
 
I would wait and see if it actually fixes the problem, and not just hopefully fixes the problem, since it's not as rare as they try to make it sound.
 
I read several other news reports. It is my understanding it is for a specific firmware bug. There is a possibility that not all BSOD's are caused by the same firmware bug. It is going to be another situation where it may or may not work. It just depends whether or not a user has an ssd with the correct firmware bug.
 
I wonder if this resolves the bug I experienced and reproduced 3+ times. On a nvidia 750i chipset board, any attempt to update the firmware on the ocz agility 3 and ocz vertex 3 max iops produced a BSOD until the nvidia graphics driver was uninstalled and using the generic vga driver. I really dont feel like risking the data on either SSD to find out though. SSDs updated fine w/o any issues on the Z68 based board.

Edit: I experienced the bug I mentioned above on firmwares 2.09 and 2.11. So far I haven't had cause to seek more recent updates and haven't looked into them since. I will tread lightly when considering the update.
 
There are several different causes, but this should address the two main ones. I don't understand what the hell sort of nonsense SF and it's partners have been talking up, but on my system and workload, the problems are repeatable, frequent, and evenly spaced.
 
Glad that got a fix... but its too late. I couldn't wait any longer and bought a Crucial M4 128Gb 2 months ago. Stability is critical on my laptop which is a combo business/personal rig and this fix has been a LONG time coming.

I was all ready to jump on the SF bandwagon, but now that I went Crucial I don't see any reason to change with as great as the M4 is.
 
[citation][nom]clonazepam[/nom]I wonder if this resolves the bug I experienced and reproduced 3+ times. On a nvidia 750i chipset board, any attempt to update the firmware on the ocz agility 3 and ocz vertex 3 max iops produced a BSOD until the nvidia graphics driver was uninstalled and using the generic vga driver. I really dont feel like risking the data on either SSD to find out though. SSDs updated fine w/o any issues on the Z68 based board.Edit: I experienced the bug I mentioned above on firmwares 2.09 and 2.11. So far I haven't had cause to seek more recent updates and haven't looked into them since. I will tread lightly when considering the update.[/citation]

Me too. My drive is working fine and I won't update until I'm sure it's safe to do so. I have had a couple of blue screens and some odd things at startup that scared the crap outta me like messages about not being able to find the boot record. But this is a typical windows experience for me, weird stuff happens from time to time.
 
[citation][nom]clonazepam[/nom]I wonder if this resolves the bug I experienced and reproduced 3+ times. On a nvidia 750i chipset board, any attempt to update the firmware on the ocz agility 3 and ocz vertex 3 max iops produced a BSOD until the nvidia graphics driver was uninstalled and using the generic vga driver. I really dont feel like risking the data on either SSD to find out though. SSDs updated fine w/o any issues on the Z68 based board.Edit: I experienced the bug I mentioned above on firmwares 2.09 and 2.11. So far I haven't had cause to seek more recent updates and haven't looked into them since. I will tread lightly when considering the update.[/citation]

Have you tried using the Linux tool ( easy Linux boot iso, just need a small USB drive to boot from )? Works wonderfully.
 
Nah. I only experiment with Linux on an aging laptop. Once I figured out to un-install the nVidia graphics driver, the update was nearly painless. Now, if needed, I just do the firmware updates on the Z68 board and don't have to mess with that nonsense (that board is currently being outfitted with wc setup so I can't play with the new firmware just yet).
 
[citation][nom]clonazepam[/nom]Nah. I only experiment with Linux on an aging laptop. Once I figured out to un-install the nVidia graphics driver, the update was nearly painless. Now, if needed, I just do the firmware updates on the Z68 board and don't have to mess with that nonsense (that board is currently being outfitted with wc setup so I can't play with the new firmware just yet).[/citation]

You dont have to install Linux... you realize that right? Its a bootable Linux image that exists on the USB key, and boots into a "live" Linux OS. You dont need to uninstall anything or swap drives around. You plug your USB key in and reboot your machine, catch it at boot-time and boot from the USB key. At the Linux desktop you run a script. Done. Reboot your machine, unplug your USB key and boot into Windows.

Mind you, thats not to say they should not be fixing the issue with the i5 750 setup, just saying there are alternatives that are easier to manage while waiting for a fix to that issue.
 
This issue is not critical by any stretch of the imagination. On a Sandforce-based SSD that is always under very heavy use 24/7 this BSOD issue happens maybe once every 6 months at most. Sandforce controllers have always been more reliable than any other brand since their introduction. Why in the world would anyone not want a Sandforce-based SSD?
 
[citation][nom]excidium[/nom]You dont have to install Linux... you realize that right? Its a bootable Linux image that exists on the USB key, and boots into a "live" Linux OS. You dont need to uninstall anything or swap drives around. You plug your USB key in and reboot your machine, catch it at boot-time and boot from the USB key. At the Linux desktop you run a script. Done. Reboot your machine, unplug your USB key and boot into Windows.Mind you, thats not to say they should not be fixing the issue with the i5 750 setup, just saying there are alternatives that are easier to manage while waiting for a fix to that issue.[/citation]

I do realize it. I have a gazillion live CDs and DVD installs, etc of all the most popular flavors and some lesser-known varieties. I actually exceeded my ISP's bandwidth cap one month.
 
[citation][nom]techguy378[/nom]This issue is not critical by any stretch of the imagination. On a Sandforce-based SSD that is always under very heavy use 24/7 this BSOD issue happens maybe once every 6 months at most. Sandforce controllers have always been more reliable than any other brand since their introduction. Why in the world would anyone not want a Sandforce-based SSD?[/citation]

Happened 3 times in the first week I owned it. Minor MFT corruption happened on the first two. Outright data loss on the 3rd.

So...
Yes, it's critical (as failing storage almost always is)
No, Sandforce is not more reliable ... you've been living under a rock.

Why would anyone not want one?
I dunno, why would anyone not want a Ferrari that has no lugnuts?
 
[citation][nom]compton[/nom]There are several different causes, but this should address the two main ones. I don't understand what the hell sort of nonsense SF and it's partners have been talking up, but on my system and workload, the problems are repeatable, frequent, and evenly spaced.[/citation]

Frequent here as well. Not trivial.
 
What we don't know is if this discovered Bug is one of many or the only Bug causing the BSOD in the SF 2200 series controllers.

Since Intel, Crucial, OCZ, Corsair and pretty much all SSD suppliers have one form or another of either reliability or compatibility issues, it's safe to say that consumer grade SSDs are still not ready for prime time if data security is important to you.
 
Status
Not open for further replies.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom