Disclaimer - This may have already been discussed. It is 2 month old news, but I searched for a thread on the topic and couldn't find one. Starting this thread because I panicked all day, thinking that my computer was screwed. Since late last night I've been getting a BSOD, and on a warm reboot the drive wasn't found. A cold reboot fixed the problem, only for it to happen again around an hour later. As it turns out there's a problem in the M4 0001, 0002, and 0009 firmware that causes this problem after 5134 hours of use (it really is that specific). Apparenltly after this time it reports back to S.M.A.R.T. with invalid data, causing the crash and causing the drive not to be recognized without completely killing the power to the system. Although the firmware was released two months ago I only reached the magic 5134 mark last night, and so was completely oblivious the problem - "Oh, another firmware update, I'll bother with that later" - and spent the whole day troubleshooting. Hopefully this post will help someone avoid that. Firmware version 0309 is available from - http://www.crucial.com/support/firmware.aspx
Thanks and rep for posting Vipers. The issue was posted about a while ago tho the title did not mention the firmware iirc, it did have a link to the update in the last page. Thanks again
where I work we sent a PC out with this drive in and they said it keeped blue screening after a quick Google and found this we wasn't happy :/ its a big bug to have with a SSD edit: its a coding problem or something like that
My friend has two Crucial M4s in RAID-0 and will probably be approaching the power on hours bug soon. Will the updater be able to address the drives in RAID-0 or will I have to plug them in separately and rebuild the RAID? Edit: Found this bit in the guide:
I went to my friend's house to update his SSD firmware when we first heard about this, at the time we couldn't get the update to run. :/ So whatever happens now, we have to do it, as I know he's approaching that time.
Hmmm ive got my m4's in raid 0. I hadnt heard of a power on bug though? Either way I will be doing a bios update to my board soon so I will take the opportunity to update the firmware on my drives at the same time.
I just updated min there. I didn't think it effect mine since it was a new one but it turns out it does. I just ran the file, it restarted and flashed the new firmware. Easy as pie.
Luckily I read about this whilst waiting for my M4 to arrive, so it got flashed before it was even formatted.
Like I said earlier, me and my friend had a bit of trouble getting the ISO to boot from a CD, more people had the same problem. Lucky Crucial brought out an .EXE version of the firmware- much easier to use.
Hey up. Just noticed another M4 update, 000F. Corrects a few issues. Oddly this time i decided to try to use that new auto detector updater thing. It said i dont have any ssds that need updating. Ooop, what about the 2* 512g ones in my computer, dont they count? Looks like i will be updating the good old reliable way of boot from cd, never failed me before on my m4s, even on a marvel port under sata3, which it doesent reccomend. anyway, just letting you know. available from crucials site.