Intel was rumored to be working on a SandForce based drive for several months now, but even the rumors couldn't encapsulate just how long Intel and SF has worked on this drive. According to Intel, the relationship began 1.5 years ago. Still lacking a 6Gbps controller of their own and wanting to remain competitive with the rest of the market, Intel approached SandForce about building a drive based on the (at the time) unreleased SF-2281 controller. Roughly six months later, initial testing and validation began on the drive. That's right, around the time that OCZ was previewing the first Vertex 3 Pro, Intel was just beginning its extensive validation process.

Codenamed Cherryville, Intel's SSD 520 would go through a full year of validation before Intel would sign off on the drive for release. In fact, it was some unresolved issues that cropped up during Intel's validation that pushed Cherryville back from the late 2011 release to today.

Intel's strenuous validation will eventually make SandForce's drives better for everyone, but for now the Cherryville firmware remains exclusive. Intel wouldn't go on record with details of its arrangement with SandForce, but from what I've managed to piece together the Intel Cherryville firmware is exclusive for a limited period of time. That exclusivity agreement likely expires sometime after the SF-2281 is replaced by a 3rd generation controller. There are some loopholes that allow SandForce to port bug fixes to general partner firmware but the specific terms aren't public information. The important takeaway is anything fixed in Intel's firmware isn't necessarily going to be fixed in other SF-2281 based drives in the near term. This is an important distinction because although Cherryville performs very similarly to other SF-2281 drives, it should be more reliable.

As Intel has been working on this firmware for quite a while, it's likely that the 520 uses an older branch of the SF-2281 firmware that has been updated over the past twelve months.

The BSOD is Back, but Not on Intel

Back in October SandForce announced that it had discovered a firmware issue that resulted in unexpected BSODs on SF-2281 drives on certain platforms. Why it took SandForce several months to discover the bug that its customers had been reporting for a while is a separate issue entirely. SandForce quickly pushed out the firmware to OCZ and other partners. Our own internal testing revealed that the updated firmware seemed to have cured the infamous BSOD.

Just as background, our SSD testing is rarely over once the review goes live. Any drive we recommend gets tossed into a primary use machine somewhere within the company. We keep track of drive behavior, including any bugs or performance issues over time. This long term testing process takes place over months. The results of these long term tests are folded into future reviews and recommendations.

The BSOD is caused by a bug in SandForce's power state logic that ultimately results in the drive disconnecting from the system while it's running. It turns out that Windows isn't a fan of you hot un-plugging the drive it's running on, which results in the BSOD. We had two systems that exhibited the BSOD, both of which were fixed by the update last October.

As luck would have it, our own Brian Klug happened to come across an unexpected crash with his 240GB non-Intel SF-2281 based SSD two weeks ago when he migrated it to another machine. The crash was an F4 BSOD, similar in nature to the infamous BSOD issue from last year. While two of the systems we reproduced the BSOD bug on were cured by last year's firmware update, Brian's system (an X58/Core i7 build) was BSODing regularly playing Battlefield 3. Games end up being a great way to trigger the SF-2281 BSOD issue as they frequently switch between periods of idle and load, which does a good job of stressing the power state logic in SandForce's firmware. I immediately sent Brian an Intel SSD 520 to see if the BSOD remained on Intel's drive. Switching to Cherryville caused Brian's BSODs to go away. Indeed most end user reports of SF-2281 BSODs went away with the fixed firmware, but we've still heard of isolated issues that remain unresolved. Whatever Intel has done with the 520's firmware seems to have fixed problems that still remain in the general SF-2281 firmware.

This is actually a dangerous precedent as it means one of two things. The first possibility is that SandForce has been made aware of flaws in its current firmware and chooses against (or is legally prevented from) disclosing it to its partners. The second possibility, and arguably even worse for SandForce, is that Intel was able to identify and fix a bug in the SF-2281 firmware without SandForce knowing it existed or was addressed. I suspect it's the former but as no one is willing to go on the record about the Intel/SandForce agreement I can't be certain.

Intel did go on record saying that the 520 is expected to have far fewer F4/F7 BSODs than any other SF-2281 drive. I asked Intel if I should read into the phrase "far fewer", but the answer was no - the 520 is expected to have similar reliability to the Intel SSD 510 and 320.

At the end of the day that's what Intel really brings to the table with the 520. As you'll soon see, performance isn't very different compared to other SF-2281 based drives. Intel's biggest advantage comes from the unique firmware that ships with the drive. Intel is also quick to point out that while other SF-2281 manufacturers can purchase the same Intel 25nm MLC NAND used on the 520, only Intel's drives get the absolute highest quality bins and only Intel knows how best to manage/interact with the NAND on a firmware level. While it's nearly impossible to prove most of this, the fact that we're still able to reproduce a BSOD on the latest publicly available SF-2281 firmware but not on the SF-2281 based Intel SSD 520 does say a lot about what you're paying for with this drive.

And you are paying a premium for the 520 compared to other SF-2281 based SSDs on the market today:

Intel SSD 520 Price Comparison
  60GB 120GB 180GB 240GB 480GB
Intel SSD 520 (SF-2281) $149 $229 $369 $509 $999
Kingston HyperX (SF-2281) N/A $205 N/A $420 N/A
OCZ Vertex 3 (SF-2281) $95 $190 $240 $375 $850
Samsung SSD 830 $110 $220 N/A $360 $800

Last year Intel hinted at a move from the consumer market to enterprise server and client markets. The 520's higher price likely won't matter there, but for consumers the higher price is noticeable - particularly with good options from companies like Samsung now available on the market.

The Intel SSD 520
POST A COMMENT

138 Comments

View All Comments

  • eman17j - Wednesday, February 08, 2012 - link

    Are you trying to say that Amd's cpus are unreliable? I have one and I have no problems at all with it. I dont have crashes or freezes. Reply
  • bji - Wednesday, February 08, 2012 - link

    He's a beginner. He doesn't know what he's talking about. Reply
  • eman17j - Wednesday, February 08, 2012 - link

    Wrong because the business buys the drive at an higher price then raises the price on their product or service and passes the cost of the drive to the consumer so the consumer ends up paying for the price premium anyways Reply
  • gamoniac - Monday, February 06, 2012 - link

    Is playing game part of Brian's job description? Reply
  • Brian Klug - Monday, February 06, 2012 - link

    Heheh, I guess you could say that for once, yes, playing BF3 was part of the job! :)

    -Brian
    Reply
  • Oberst - Monday, February 06, 2012 - link

    Seems like there is the first customer with the bsod bug in the intel forum. It seems like the reliability is no better than at all the other SF drives and it's just a matter of (bad) luck.
    http://communities.intel.com/message/149389#149389
    Reply
  • Makaveli - Monday, February 06, 2012 - link

    That tool installed his brand new Intel 520 drive in IDE mode? Reply
  • NitroWare - Wednesday, February 08, 2012 - link

    You would be surprised how many laptop owners (and even desktop owners) are unaware that they should use AHCI mode. I can guarantee that there are millions of boards out there with modern HDD or SSD in non optimal mode.

    Another large tech site interviewed several mobo vendors about Z68 and most sad it was supposed to ship with RAID mode as default due to the SRT feature., the reality is much different.

    2010 1st gen core i5 thinkpad has problems with third party SSDs which some users claim IDE mode is the only way they get their 'cheap' SSD working

    There is a mentality that if a user knows how to physically install a drive then they do not need to do anything else. Then there is the old drivers issues, yeah whatever the motherboard came with at best.

    That is something the chipset vendors need to work on. Some motherboards put up a warning if you try to turn AHCI off with an auto counter to re-enable it.

    It is definitely possible that a BIOS can detect a SSD and at least put up a text message saying what the recommend setting is. It is hard to ignore such messages.
    Reply
  • mustardman29 - Monday, February 06, 2012 - link

    I was trying to tell the OCZ support guys ever since their latest firmware that the BSOD is still there. It happens a lot less but it's still there.

    They were trying to tell me it was something wrong with my system and that I should re-install windows. That the kind of thing I would expect to hear from a 1-800 number that goes to someone in India reading a script. Not from a drive manufacturer.

    I'll never buy another OCZ drive. Not because of the problem but because of the way they are dealing with it. Pretending it's does not exist and telling people to re-install windows.

    And yes, Sandforce deserves part of the blame for pretending there was no problem for a long time despite many people saying otherwise.

    However, I would not hesitate to buy this intel drive. They obviously found the problem and fixed it with their own firmware. Something the controller manufacturer seems incapable of doing.
    Reply
  • ckryan - Monday, February 06, 2012 - link

    You're not crazy. SF2281s still have stability issues, and the TRIM related BSODs are still happening too. Most people won't ever have problems with a 2281, but many did and still live with the occasional problem. The last round of FW did indeed fix many problems (it solved mine), but others still suffer. I stopped using the drives just because I have quite a few I play with, but you can still get a 2281 to flop on TRIM every once in a while.

    I'm sure Intel really put the screws to Cherryville's FW, but I think some of the issues with 2281 and their ilk are still mysteries to the SF partners, and possibly even LSI/SF and Intel (the expect fewer problems?).

    Here's hoping the next gen of the SF is bulletproof.
    Reply

Log in

Don't have an account? Sign up now