04-11-2012 11:46 AM - edited 04-18-2012 08:07 AM
Revision Firmware 000f is now available. If you are updating the firmware on the Crucial Adrenaline drive, you must uninstall the dataplex software before attempting the firmware update. Please visit the following link to download this firmware update:
http://www.crucial.com/support/firmware.aspx
Firmware Release Notes
Firmware for the m4 SSD is being updated from version 0309 to 000F. The m4 is updatable to this new firmware starting from versions 0001, 0002, 0009, or 0309 in a single step. If updating from an early version directly to 000F, all interim improvements will also be included (please see Release Notes for version 0002, 0009 and 0309 at crucial.com for details).
Changes between version 0309 and 0000F include the following changes:
• Improved compatibility with certain SAS expanders and peripheral RAID cards.
• Improved throughput stability under extremely heavy workloads.
• Improved data protection in the event of unexpected, asynchronous power loss.
This firmware update is recommended for all Crucial m4 drives currently in the field if the end user is experiencing any of these symptoms.
Please use this thread to provide feedback.
Solved! Go to Solution.
04-11-2012 11:53 AM - edited 04-11-2012 11:54 AM
Good job Crucial. ![]()
Just kinda reserving a post here in case we need to add any tips at a later date. ![]()
FAQs and Top Forum Solutions
Did a user help you? Say thanks by giving Kudos!
How do I know what memory to buy?
Still need help? Contact Crucial Customer Service
Remember to regularly backup your important data!
04-11-2012 12:18 PM - edited 04-11-2012 12:19 PM
Awesome, hopefully that 4k-64thrd drop issue is fixed. ![]()
04-11-2012 12:40 PM
Couldn't update with Windows tool for some reason. Got "Windows couldn't start error". Hope it's just me. Will go ahead with the traditional method of flashing instead.
04-11-2012 02:02 PM - edited 04-11-2012 02:48 PM
Same here, no go with the installer.
All good the traditional way.
04-11-2012
03:22 PM
- last edited on
04-12-2012
01:30 AM
by
Crucial_Junket
Updated firmware using windows tool without any issues. Doh, such a relieve after ***Edit to remove Crucial competitor*** updates... ![]()
Windows 7 x64
M4-256Gb
Performance seems to be the same (atto & asssd are +/- 2-5% of 0309, somewhere higher, somewhere lower).
04-11-2012 04:26 PM - edited 04-11-2012 04:28 PM
XSCounter wrote:Couldn't update with Windows tool for some reason. Got "Windows couldn't start error". Hope it's just me. Will go ahead with the traditional method of flashing instead.
DooRules wrote:Same here, no go with the installer.
All good the traditional way.
You need to place the Updater Application (.exe file) in your C:\ drive otherwise it won't work.
Crucial needs to update the tool to automatically extract the files to the system drive and not the drive the file is in!
04-11-2012 04:59 PM
SeanWebster wrote:Awesome, hopefully that 4k-64thrd drop issue is fixed.
Nope
04-11-2012 05:05 PM
rpsgc wrote:
XSCounter wrote:Couldn't update with Windows tool for some reason. Got "Windows couldn't start error". Hope it's just me. Will go ahead with the traditional method of flashing instead.
DooRules wrote:Same here, no go with the installer.
All good the traditional way.
You need to place the Updater Application (.exe file) in your C:\ drive otherwise it won't work.
Crucial needs to update the tool to automatically extract the files to the system drive and not the drive the file is in!
I ran the executable from within the zip that was on a data drive and it worked fine.
04-11-2012 05:10 PM - edited 04-11-2012 05:10 PM
GeneO wrote:
rpsgc wrote:
XSCounter wrote:Couldn't update with Windows tool for some reason. Got "Windows couldn't start error". Hope it's just me. Will go ahead with the traditional method of flashing instead.
DooRules wrote:Same here, no go with the installer.
All good the traditional way.
You need to place the Updater Application (.exe file) in your C:\ drive otherwise it won't work.
Crucial needs to update the tool to automatically extract the files to the system drive and not the drive the file is in!
I ran the executable from within the zip that was on a data drive and it worked fine.
You do know that files executed from within zip/rar archives are extracted to a temp folder in the system drive, right?