Crucial M4 firmware update (000F)

[Burner27]

I'm booting into the updater but it does not recognize my drive once there.

See my post if it helps.....

 

[Burner27]

FW - 0309

FW - 000F

 

[icanhascpu2]

This forum needs a 'delete post' function.

 

[icanhascpu2]

Its nice to see crucial being diligent with updates for their product. I can't wait for their next iteration of drives.

Can you believe some people are making this out to be a bad thing?

son of a b...I just shipped 20 computers with this drive....at least they had 0009

0309 has been out for ages and was the more important one....

 

[Coup27]

SSD firmware updates are clearly here to stay for the time being. That should be taken into account when fitting them into machines you are not actually responsible for maintaining.

Also as above, you should really have flashed them to 0309 first. If the machines you shipped are on 24/7, expect them to go boom in 6 months time.

 

[Reikon]

Someone on the Crucial forums got a huge loss of performance after the update. Not sure if it's a common occurrence.

http://forum.crucial.com/t5/Solid-S...rmware-000f-is-now-available/m-p/93740#M27970

 

[Burner27]

My sequential and 512k reads went down, but I wouldn't call it a HUGE drop in performance. All my other numbers went up actually.


FW 000F AS-SSD Benchmark:

 

[jhansman]

Interesting that about every third person in that Crucial forum post claims success and improvement, while the rest piss and moan. Methinks is perhaps a chipset issue? I'm holding off until either Crucial posts a revision or I can see that owners of my chipset combo (890FX/SB850) are enjoying improvement. Otherwise, no point in breaking in what's already fixed.

 

[imaheadcase]

Updated worked fine for me, performance seems about the same to me on M4 256gig

 

[Chiropteran]

update game some sort of error message, but it seemed to install anyway.

 

[jhansman]

As yet, I haven't read a single reason to do this update. But then, I'm five iterations back from my mobo's bios, too.

 

[masteryoda34]

Worked fine here. x58 motherboard.

 

[sequoia464]

I got a slight decrease in reads - slight increase in writes ... pretty much a wash.

 

[OlafSicky]

Works here just fine some change in R/W but nothing to worry about.

 

[icanhascpu2]

As yet, I haven't read a single reason to do this update. But then, I'm five iterations back from my mobo's bios, too.

I'd say a rule of thumb is dont fix what aint broke (or isnt going to break).

 

[Uncle Bob]

Q: Has anyone installed this firmware and subsequently installed or re-installed windows?

I ask because I'm working on a new rig for someone which has had Windows 7 installed and running for a week. During this time I've updated the firmware and the motherboard bios.

System Spec:
Core i7-2700K
Gigabyte GA-78X-UD3P-B3 Motherboard (original bios F4 - currently on F8)
16GB (4 x 4GB) Crucial Ballistix DDR3-1600
Crucial M4 120GB SSD (on the intel sata-3 6gb/s port 0) (original firmware 0309 - currently on 000F)
2 x 1TB Seagate Barracuda (both on the Marvel ports)
LG BH10LS38 Internal Blu-Ray SATA Drive (on the intel sata-2 3gb/s port 2)

Now, I'm having major issues re-installing windows. First I had the 'Windows cannot install to this disk' which required manually deleting and creating a partition on the drive. Now I'm getting a 'file corrupt or missing (error: 0x80070570)' during the install !

 

[Uncle Bob]

Turns out - nothing to do with firmware updates....

Removed two sticks of ram and disconnected mechanical drives. Sailed through install without any problems at all

Go figure....

 

[jhansman]

Turns out - nothing to do with firmware updates....

Removed two sticks of ram and disconnected mechanical drives. Sailed through install without any problems at all

Go figure....

Well, that's interesting. I'm not sure I would have thought to try those particular troubleshooting steps, but they just got added to my list. :thumbsup:

 

[Uncle Bob]

Well, that's interesting. I'm not sure I would have thought to try those particular troubleshooting steps, but they just got added to my list. :thumbsup:

Reduce and simplify ;-)

Looking like I've got a bad stick of RAM.. getting install failures on some apps now but only when using one pair and not the other. Frustratingly they're passing Memtest86+

 

[jwilliams4200]

Well, that's interesting. I'm not sure I would have thought to try those particular troubleshooting steps, but they just got added to my list. :thumbsup:

The part about disconnecting drives is S.O.P. for troubleshooting Windows installs. That is the first thing I tell people who are having problems -- disconnect all drives except the one you are installing to. It solves a lot of problems people have.

 

[survey_sez]

fwiw - i had a terrible time getting the updater to recognize the m4 with either the windows or the boot flash utility on my p8z68-v pro gen3 rig. crucial clearly needs to do some more work on the updater. i eventually used another one of my rigs that did recognize it and flashed from there. wound up getting an error indication after it flashed as another member mentioned, although it did indicate 000f afterwards. big mistake - read on.

the m4 basically bricked after updating firmware from 0001 to 000f. rma'd it back to corsair and received a refurb'd one about a week later that is at 0309. that might indicate even crucial is reluctant to use 000f.

 

[bryanW1995]

Turns out - nothing to do with firmware updates....

Removed two sticks of ram and disconnected mechanical drives. Sailed through install without any problems at all

Go figure....

Well, that's interesting. I'm not sure I would have thought to try those particular troubleshooting steps, but they just got added to my list. :thumbsup:

You always want to disconnect all other drives when installing the OS.

fwiw - i had a terrible time getting the updater to recognize the m4 with either the windows or the boot flash utility on my p8z68-v pro gen3 rig. crucial clearly needs to do some more work on the updater. i eventually used another one of my rigs that did recognize it and flashed from there. wound up getting an error indication after it flashed as another member mentioned, although it did indicate 000f afterwards. big mistake - read on.

the m4 basically bricked after updating firmware from 0001 to 000f. rma'd it back to corsair and received a refurb'd one about a week later that is at 0309. that might indicate even crucial is reluctant to use 000f.

I had no problems at all on my ga-z68ma-d2h, and I updated the firmware on both of my m4's.

 

[Endymion FRS]

You always want to disconnect all other drives when installing the OS.

Woah is this bad? I installed Windows 7 on my m4 with a Caviar Black connected too. It seemed like it went fine. Or did I unknowingly screw something up?

 

[mrpiggy]

the m4 basically bricked after updating firmware from 0001 to 000f. rma'd it back to corsair and received a refurb'd one about a week later that is at 0309. that might indicate even crucial is reluctant to use 000f.

Corsair for RMA of a Crucial Drive? Typo?

FYI, if there's a brand new firmware, the chances of you getting the new firmware on a replacement drive is small. No company is going to go through all their existing shelf stock and update firmware right away as long as their are no showstoppers with the current firmware. Eventually you would get the newer firmware, but not until the shelves have been replenished with newer manufactured stock.

 

[thelastjuju]

What is the point of all this?

Is there something wrong with the firmware included with the M4 I bought about a month ago?? Everything seems to be working perfectly, is there something I will run into in the future if I don't upgrade the firmware?

Usually I avoid firmware upgrades unless totally necessary. Hell, I'm even avoiding video card drivers unless they are totally necessary, at least with AMD's drivers.