Crucial M4 SSD

[BearCat]

Has anybody tried the new 010G firmware? Crucial states there may a problem with UEFI bios's. I can't find anything directly related to R4E or R4F though.

[hsm06]

Many people believe that 010G Firmware not support UEFI ??? ...
Are you sure he refers to is the Firmware~

In fact, due to the Windows under the updated firmware does not support UEFI BIOS,
Under Windows update firmware program does not find the SSD can not be updated,
Reboot after the update does appear once could not be loaded M4 SSD Boot update information, (he only once not each boot appears ...)
But do not worry you can still press Enter to enter the operating system.

UEFI BIOS update the M4 firmware, please use the Manual Boot File for Windows and Mac to update,
Crucial refers UEFI will not find SSD for the update under Windows Update does not support UEFI-BIOS ....
Cause not to say update 010G Firmware UEFI will not find SSD.


Crucial :
UEFI-based Systems: During validation of this firmware update "we noticed instances where our update tools do not recognize the SSD with some systems using UEFI." The target device is not recognized as an updateable device during the reboot process. If this happens, the firmware update will not occur, and you’ll retain the firmware version you started with. Windows will then restart normally. If this sequence occurs, you cannot upgrade to this firmware version at this time, but you’ve done no harm to your system (or your data).

[Phillyflyer]

Thanks for posting the screenies....Here are screenies of the Samsung 830 128GB in Raid 0 that I am currently using vs the Crucial M4 256GB in Raid 0 on the X-79....The 3rd screenie is the OCZ Vertex 4 128GB in Raid 0 on the Asus Maximus Extreme Z-68:

[Baalberith_NL]

UEFI can be evaded by either using an bootdisk, or much easier, putting the install file on C: drive and then executing it.

[Nodens]

This is how I understood this as well. The only problem is with the updater not the drive.

Baalberith_NL wrote:
UEFI can be evaded by either using an bootdisk, or much easier, putting the install file on C: drive and then executing it.

Never ever run a drive firmware update from the drive itself. Most of the updaters won't let you and even warn you about it. Just use the manual method Crucial is providing while making sure you boot into legacy mode by selecting the option from the boot menu.

[Baalberith_NL]

The update is non-destructive, and stated by Crucial placed on C: drive. This is needed for the BIOS to find the primary disk after executing the update and nessecary reboot.

[Nodens]

Well according to Crucial's guide PDF you run the updater from Boot cd or usb stick and not from the drive itself.
http://www.crucial.com/support/firmware.aspx

Select Crucial M4 and click "Guide" under Manual Boot. For the Windows Update tool it doesn't matter where you run it from (again according to the equivalent Crucial guide). But flashing anything under Windows is a bad idea anyhow (unless there is no other available option). It is a rule of thumb to never flash a device from the device itself. If the update is destructive or non-destructive is irrelevant.

[BearCat]

Yes it is possible to successfully install this firmware by whatever means. But if you check the Crucial forums you'll find people are having detection problems even after installing it properly. Sometimes it takes a couple of reboots. Sometimes it takes a couple of days. But their SSD will start to "drop out". Not everybody, but enough to call it a problem. I would wait till their done building the updated version that is more UEFI friendly.

[Nodens]

Roger that BearCat. Sounds like a good idea not to update to this one.