Crucial wrote:We are aware of an issue that is currently affecting a small number of users whereby their m4 causes their system to require a restart. This issue occurs after approximately 5,000 hours of actual “on time” use. Following the initial reboot, the system then requires subsequent restarts after each additional hour of use. However, the data on the SSD is unaffected and will not be lost due to this condition.
LiamC wrote:Intel, Sandforce and Marvell have all had bugs. Hell even mechanical drives still get them (hello Seagate). And despite what the slack-jawed knuckle-draggers rabbited on about, I much prefer the way OCZ dealt with the Sandforce bug than the Ostrich mentality adopted by others. If you know, you can prepare. If you don't know, you're screwed.
I am also sorry to hear that you are having issues with our Firmware page and if this is simply the reason you are looking to return the drive then you can follow the link below to our Firmware page and if you follow the instructions step by step you shouldn't have any further issues:
You don't have to switch to IDE mode. That's from the old instructions. All I had to do on my P8P67 was disable the sata 3 controllers in the bios and it found my drive. Didn't even have to move the sata port it was in (I guess the ports default to 2.0 when 3.0 is disabled???)
Derfer wrote:You don't have to switch to IDE mode. That's from the old instructions. All I had to do on my P8P67 was disable the sata 3 controllers in the bios and it found my drive. Didn't even have to move the sata port it was in (I guess the ports default to 2.0 when 3.0 is disabled???)
Lastly, how on earth can you say you preferred OCZ's handling of the sandforce bug? They pretended it didn't exist for 6 months. Crucial patched this in less than 2 weeks. This isn't like insider info here. Put forth a little effort and you'll find yourself bitching about a lot fewer things in life.
Users browsing this forum: No registered users and 2 guests