Quote Originally Posted by Tony View Post
voodoo thread?

LOL, you guys may need to start thinking the host may have something to do with the bsod's or its something that the host does and the drive does.
Innuendo blaming everyone (including end users) and the dog is not helpful and just comes over as an attempt to deflect the problem away from SF2xxx products.

Quote Originally Posted by Tony View Post
Also, I just posted a blurb about talking to Asus, they are stuck on Orom 10.5 and lock down MEI, GBT and MSI are not locked and do not lock down and have far fewer issues with uefi with newer Orom (11 series for example) and note Intel have moved all sandy Bridge boards to 11 series Orom also..

funny how 11 series was supposed to be for X79 boards only
More innuendo with no substantiaition ...oh let me guess NDA

I have updated the firmware on my V3 whenever f/w versions have been released. I ran the endurance app for 7 days straight (~168 hours). I have installed Win 7 and Win 8 in my main PC without any tweaks whatsoever. I’ve installed the V3 as an OS drive in two different laptops, again with zero tweaks. I have used sleep in all instances.

Not a single problem to report. SF2xxx drives seem to either work or not work regardless of the configuration.

Despite the fact that some drives appear to work OK the potential for data loss, combined with the fact that neither SF nor any of the vendors know what the problem is makes the situation unacceptable. Forget trying voodoo, in my view SF2xx products should be recalled.