Crucial to Fix M4 BSOD Issue in Two Weeks
by Kristian Vättö on January 6, 2012 1:41 PM ESTHere we go again. Pretty much every SATA 6Gb/s SSD offering has experienced some issues and it appears the Crucial M4 is no exception. There have been threads about non-stop blue screens of death (BSOD) floating around in Crucial's forums for a month or so. Yesterday, Crucial announced that they are on schedule to provide a firmware update for their M4 SSD series. The update is supposed to fix a firmware bug that is causing the BSODs after about 5000 hours of active use. The BSODs are not random and occur roughly every hour, which definitely affects productivity. Luckily, the data on the SSD remains unaffected. If Crucial is able to meet their schedule, the update will be available the week of January 16th.
Source: Crucial
40 Comments
View All Comments
Kristian Vättö - Saturday, January 7, 2012 - link
I agree. While I think I have never read a whole DT article, I don't think they deserve the visibility they get. I guess it was different when DT launched but nowadays, they are totally different. We have no impact on what they post and vice versa. If they post crap, it's linked to our site automatically, even if we strongly disagree with the article.We have some plans on improving pipeline visibility which may (and hopefully will) reduce or even remove the visibility of DT on AT. I'll be sure to bring this up in our next chat.
ddarko - Saturday, January 7, 2012 - link
Oh thank god.Mr Perfect - Monday, January 9, 2012 - link
DT does have interesting things once in a while, but the users are so caustic I just stopped reading it. The article just kind of provides the topic for the ensuing flame war.sprockkets - Sunday, January 8, 2012 - link
They seem to run on the same damn server. Jason Mick pretty much has to add "EDITORIAL" to every article it seems.It is fun to watch the fanbois eliminate/troll each other though.
damianrobertjones - Saturday, January 7, 2012 - link
There were a WHOLE load of posts on the Crucial forum tall those months ago and although I tried to inform people it obviously got ignored.Shame really as the proof was there for all to see.
Now we have a second bug
MrSpadge - Saturday, January 7, 2012 - link
It's Crucial, not Corsair.Namey - Friday, January 6, 2012 - link
I can feeeeel your anger. It gives you focus, makes you STRONGER.Araemo - Friday, January 6, 2012 - link
They have when it has come up.. But as a website that relies primarily on actual hands-on testing.. even running one of these drives 24/7 would take 200 days to bring this issue up.. so they probably have no first hand evidence to report on.Kristian Vättö - Friday, January 6, 2012 - link
The problem is that there are no studies on this. Google "[enter the SSD here] issue" and you will find something, regardless of the SSD. It's always hard to come up with an objective article without any concrete figures. How can we prove that one SSD is more reliable than the other without having any backup?Anand tried to prove and find the SandForce bug for months. This Crucial issue is even harder because it requires 208 days of 24/7 running. Besides, how do we know that never SSDs, e.g. Samsung 830 and OCZ Octane, don't suffer from a similar issue? Only time will tell, I guess.
If you want my opinion on what SSD to get, it's Samsung 830. From what I have seen around the forums, it has no widespread issues. Then again, I thought the same about Crucial M4 a few days ago, and Intel 320 before the 8MB bug.
piroroadkill - Sunday, January 8, 2012 - link
http://www.xtremesystems.org/forums/showthread.php...Sacrificing SSDs for science!