As I said in our last big SSD round-up, the inconvenient truth about solid-state storage is that it still has reliability problems. Every major SSD maker seems to have been affected by one issue or another, and the SandForce BSOD bug proved particularly stubborn through most of last year. The blue screen of death has hit again, but this time, it's Crucial's m4 SSDs that are affected. The company's forums detail numerous reports a 0x00000f4 BSOD error popping up on users' systems.
Crucial has confirmed the bug, which apparently rears its head after about 5,000 hours of disk "on time." According to Crucial, rebooting will return an affected machine to normal operation, but only briefly: "the system then requires subsequent restarts after each additional hour of use." Ugh.
Although Crucial claims to have determined the cause of the problem, a firmware update to fix it isn't due until the week of January 16. The company is adamant that users aren't at the risk of data loss due to the bug, though. I'd recommend that anyone with an m4 make a backup of the drive's contents just in case.
This news is certainly disappointing, and we'll be sure to grill Crucial when we meet with them next week at the Consumer Electronics show. I can't help but find some irony in the fact that the m4, a drive we've been recommending as an alternative to folks turned off by the SandForce BSOD bug, now has one of its own.
|Steve Ballmer leaves Microsoft board, goes ballin'||14|
|Here's a 37-minute video of The Witcher 3||1|
|Tuesday Night Shortbread||22|
|Asus has a smartwatch up its sleeve, plans Sep. 3 unveilng||19|
|SanDisk's Ultra II SSD combines TLC NAND with clever caching||9|
|New Corsair contraption controls fans, temps, LEDs||12|
|Enermax's new card readers are perfect for empty external bays||30|
|A quick look at AMD's Radeon R7 SSD||64|
|Rumor: AMD to shake up FX series on Labor Day||83|