Crucial Support Forums:
That doesn't sound good and the thread started back on December 13th, 2011. Yesterday, it appears that Crucial has figured out the issue and has a firmware fix for it in the works:I just started getting this error yesterday on my M4 128gb drive. I've had it for about 6 months or so. Basically I'd come home to Windows saying 0xc000000e and it's unable to boot. If I warm reset then I'd hit the same error, but if I power cycle then it would boot fine. After about 30 minutes or so I get a blue screen and the 0x000000F4 error.
and this later update: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. Once you hit the ~5000 hours of on time, the issue will happen regardless of how you use the drive.
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.
Crucial Employee, US
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.
I apologize for the inconvenience.