Users over on Crucial's
support forum have been complaining about a strange error that manifests on certain M4 solid state drives (SSDs) after precisely 5,200 hours of use. It appears to only affect the 64GB models, with affected drives kicking Windows systems into a BSoD with an error code that reads 0x00000f4. Crucial acknowledged the error exists on a "small number" of drives and said it's working on a firmware fix. Here's the official statement.
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.
Through our investigation, we have determined the root cause of the problem and will be releasing a firmware update that rectifies the situation. We are currently running through our validation and compatibility process. Once this process is complete, the firmware will be made available to our customers. Although we understand the desire of some people to start using unreleased firmware now, we want to ensure that our solution works across multiple chipsets, systems, and operating systems before publishing the release code. We are currently targeting the week of January 16th, 2012 to publicly release the new firmware update.
We understand the impact that this is having on some users right now and apologize for this inconvenience. We appreciate your continued support, feedback, and patience as we finalize code and resolve this issue.
In the meantime, users waiting for a fix can direct their browser to Crucial's Firmware Update Notifications
thread and bookmark the page.