What's wrong with the Crucial M4 010G Firmware and why hasn't it been fixed ?
About a week or two ago Crucial released a new firmware update for the Crucial M4 SSDs, the firmware update is 010G. Last week I updated my M4 towards that firmware as I was still running the old firmware that could crash at 5000 used hours of the SSD ( a known and fixed problem). If it ain't broke, then don't try to fix it, however with that 4000 or 5000 something used hours bug in mind I figured, it is time to update the firmware. With a backup in place I re-flashed the SSD, all data was still there which made it a lovely silent upgrade. But ...
Once I posted about the firmware there was word in our forums that some Guru3D users had the problem that after a reboot or a certian while the SSD was missing from the system and BIOS.
Hunting down the issue I learned that it actually is a massive problem. The Crucial forums are invested with users complaining about this. The root of the issue is that the new firmware has a problem with UEFI based BIOSes (the new flashy GUI based BIOSes). If you have a motherboard with UEFI in combo with the 010G Firmware chances are pretty good that at random after a reboot your SSD is missing -- non detectable in the BIOS. So the secondary scenario would be at power loss or a system crash, this could drop the SSD from your system and it will not be recognized in the BIOS anymore.
Today after running this firmware upgrade for over a week it was my turn, I had a system crash and after a hardware reset, the SSD was gone rogue, missing while not detectable in the BIOS.
There are steps you try to recover the SSD. Windows desktop users follow these steps.
- Connect the SSD towards power only. Once you have the drive connected and sitting idle, simply power on the computer and wait for 20 minutes. We recommend that you don't use the computer during this process.
- Power the computer down and disconnect the drive for 30 seconds.
- Repeat steps 1 and 2 one more time.
- Reconnect the drive normally, and boot the computer to your operating system.
This method so far has worked for some and not for others, me personally still trying to revive the SSD. If you are able to revive the SSD and thus are using a EUFI BIOS based motherboard, then drop down towards firmware 000F which I made available at that link.
We are clueless as to why Crucial is still serving this Firmware actively at their website.
Posts: 6804
Joined: 2008-03-06
I blindly updated my 128 M4 wich i have in my desktop computer...luckily i have a "older" motherboard ,so until now the SSD acted normally and i keep my fingers crossed that it stays so.
But i have another M4 in my laptop wich i leave with the actual firmware.
Sorry to hear this Hilbert,i hope that all your data is ok.
Junior Member
Posts: 10
Joined: 2006-02-27
Yeah, however, that's not an obvious option on the site for the 010G update... The only thing that shows is the windows update (.exe), when you select windows as your OS... I guess it shows other options if you select OSX, but as noted, that's not an obvious option.
And yeah, stay away from this firmware if you're on an UEFI BIOS... I had to use a non-UEFI bios PC to downgrade via bootable USB to 000f-- the bootable usb mehtod wouldn't wouldn't recognize the SSD on my UEFI bios, even after the BIOS recognized it after a sucessfull power cycle...
Senior Member
Posts: 904
Joined: 2008-06-02
I only just upgraded my firmware to this after thinking it was time to change from the firmware with the 5000 bug. It has been running for a week and luckily no problems.
but i think i will revert back to an older firmware
Senior Member
Posts: 9295
Joined: 2006-10-29
This reminds me so much of OCZ Vertex 2 and Vertex 3 :/ . i went trhu so much pain with the old sandforce its unbelievable. I hope Crucial comes with a solution very fast , thats no fun.
Posts: 22219
Joined: 2008-07-14
Hilbert, sorry to hear about the issue with your Crucial M4. I've avoided updating mine thus far and guess I'll be holding off until Crucial gets THIS sorted out.... Thanks for the heads up.