POST A COMMENT

15 Comments

Back to Article

  • Azsen - Saturday, January 14, 2012 - link

    Well I spent about half an hour hunting around for simple instructions to copy the firmware ISO file to a bootable USB drive instead of CD (I don't have any spare CD-Rs around).

    Simplest guide was here:
    http://www.storagereview.com/how_upgrade_crucial_s...
    Reply
  • DanNeely - Saturday, January 14, 2012 - link

    Did they explain why its 5184? That doesn't look like anything special in either minutes, seconds, or days. Reply
  • Meaker10 - Saturday, January 14, 2012 - link

    It's to do with a SMART counter apparently. Reply
  • Lord 666 - Monday, January 16, 2012 - link

    In the past couple days, my 256gb with 009 on it started acting very similar to this bug. Checked the hours and I'm in the low 2100s. Going to try this update in a few. Reply
  • Azsen - Saturday, January 14, 2012 - link

    Have just upgraded my 128GB M4 successfully. I remember in the previous guide (to update the firmware to v0009) it was saying you needed to put the SATA mode as IDE in the BIOS or it wouldn't work. However this instruction is left out of the latest guide. I wasn't sure if that was intentional or a mistake so I tried putting the drive it in IDE mode anyway but the updater program crashed when detecting the drive, so best to leave it in AHCI mode as that worked fine in the end.

    Apparently in the guide it says it won't work if you're using SATA 6GB ports so I had to go into the case and put the cable onto the number 0-3 SATA 3G ports which was a pain.

    Anyway all done now. Hopefully in 7 months time I won't be having blue screens. :) Would be interested to hear if it does actually fix the issue from users who are currently having the problem.
    Reply
  • Soulkeeper - Saturday, January 14, 2012 - link

    Burnt the .iso, had the thing booted, and flashed in under 5min.
    I love crucial and plextor's easy iso update method, great for non-windows users or people with multiple systems.
    Reply
  • damianrobertjones - Monday, January 16, 2012 - link

    ... but they shouldn't have to do this at all.... In all my life I've NEVER had to update a hard drive until the SSD march Reply
  • UltraTech79 - Friday, April 06, 2012 - link

    Never having to do it in the past somehow means never needing to to you? Many older hard drives have failed in the past due to software issues that could not be updated.

    Somehow in your mind you've corrupted this feature into a bad thing. A decade about these drives you have failed with this bug, and wholly new revisions of this drive would have been replaced with with all the same info otherwise. Today we can fix this problem without buying a new drive.

    This is 1000x better than it was before, please contact reality for more details.
    Reply
  • GTVic - Monday, January 16, 2012 - link

    The newest Intel SSD tools allow you to update virtually all Intel SSDs while running Windows. Burning an ISO is an inconvenience and a waste of a disc in comparison. Reply
  • DanNeely - Monday, January 16, 2012 - link

    Patching firmware while a system is live requires a significantly greater degree of either validation; or the writing the entire system in a functional programming language. While Ericson created its own language (Erlang) to allow patching its telecom systems that way; skills in functional programming are very rare outside of academia. Reply
  • UltraTech79 - Friday, April 06, 2012 - link

    You realize crucial also has a utility that lets you do that right? Get better information before looking like an idiot fanboy. Also, anyone that knows the risk of firmware updating knows to not do it that way anyway. Reply
  • Dug - Monday, January 16, 2012 - link

    I was very careful to download the 128GB version of 309, but everytime I try it, it states successful but lists 009. Reply
  • Coup27 - Tuesday, January 17, 2012 - link

    "Burning an ISO is an inconvenience and a waste of a disc in comparison."

    I completely disagree. Firstly you can use YUMI or similar Linux tool and make a bootable ISO on a USB stick. Second updating in a DOS/Linux environment is far less likely to go wrong than updating via Windows. Samsung have just released a new firmware for their 830 series with Windows flashing possible through their Magician software or you can burn/mount an ISO. I chose the latter and used a CD-RW and it worked without issue. There are many reports of people who chose the WIndows method being greeted with BSOD's and having to reflash using the ISO.

    Granted if Windows flashing is offered, it should work. But I think all experienced users would take DOS/Linux flashing over Windows flashing anyday.
    Reply
  • UltraTech79 - Friday, April 06, 2012 - link

    I'm glad their are people that actually know what the hell they are talking about posting here along with the morons with half-wit information and input. Thanks. USB booting is great, and no wasting an optical disk on 2MB of data never to be used again. (unless you have a RW, but the USB stick is still going to be faster and easier) Reply
  • maltschul - Sunday, January 22, 2012 - link

    I had this exact problem last week with my BSODs on my 256gb Micron C400. It was a strange problem to troubleshoot because at first iaStor.sys (running under System) would max out the CPU, freeze the computer, and then after a few minutes the OS would finally bluescreen.

    Thought I was gonna have to replace the drive. But after Micron's firmware 0309 update, all good!! Yes I know they're the same, relabeled drive but figured I'd through it out there.
    Reply

Log in

Don't have an account? Sign up now