Firmware-update: Crucial M4 070H

Crucial heeft nieuwe firmware uitgebracht voor de solid state drives uit de m4-serie. De update is alleen bedoeld voor de sata-modellen en moet dus niet voor msata-modellen worden gebruikt. Versie 070H brengt geen kritische verbeteringen en Crucial merkt deze firmware dan ook aan als optioneel. Het bijwerken van de firmware kan direct vanuit Windows 7 en Windows 8. Gebruikers van een ander besturingssysteem zullen een boot-cd moeten aanmaken. Versie 070H brengt verbeteringen voor Windows 8 en de nieuwere UltraBooks, details kunnen in de release notes worden gevonden.

Firmware Update Notifications

Firmware 070H is recommended for anyone currently running 040H or previous firmware releases. It includes incremental improvements and refinements over these versions which may improve the overall user experience.

Like recent firmware versions, version 070H has improvements over versions 000F which are specific for Windows 8 and new UltraBook systems, although systems running Windows 7 and other operating systems may also see improvements. Any m4 firmware version will function normally in Windows 8, even without these performance improvements.

The following is a summary of changes between 040H and 070H, which are independent of operating system:

• Resolved a power-up timing issue that could result in a drive hang, resulting in an inability to communicate with the host computer. The hang condition would typically occur during power-up or resume from Sleep or Hibernate. Most often, a new power cycle will clear the condition and allow normal operations to continue. The failure mode has only been observed in factory test. The failure mode is believed to have been contained to the factory. This fix is being implemented for all new builds, for all form factors, as a precautionary measure. The fix may be implemented in the field, as desired, to prevent occurrence of this boot-time failure. To date, no known field returns have been shown to be related to this issue. A failure of this type would typically be recoverable by a system reset.

Additional details can be found in the firmware guide.