The news of Samsung's SSD 840 EVO read performance degradation started circulating around the Internet about a month ago. Shortly after this, Samsung announced that they have found the fix and a firmware update is expected to be released on October 15th. Samsung kept its promise and delivered the update yesterday through its website (download here). 

The fix is actually a bit more than just a firmware update. Because the bug specifically affects the read speed of old data, simply flashing the firmware isn't enough. The data in the drive has to be rewritten for the changes in the new firmware to take place. Thus the fix comes in the form of a separate tool, which Samsung calls Performance Restoration Software. 

For now the tool is limited to the 840 EVO (both 2.5" and mSATA) and will only work under Windows. An OS-independent tool will be available later this month for Mac and Linux users, but currently there is no word on whether the 'vanilla' 840 and the OEM versions will get the update. Samsung told me that they've only seen the issue in the 840 EVO, although user reports suggested that the 'vanilla' 840 is affected as well. I'll provide an update as soon as I hear more from Samsung.

The performance restoration process itself is simple and doesn't require any input from the user once started. Basically, the tool will first update the firmware and ask for a shut down after the update has been completed. Upon the next startup the tool will run the actual three-step restoration process, although unfortunately I don't have any further information about what these steps actually do. What I do know is that all data in the drive will be rewritten and thus the process can take a while depending on how much data you have stored in your drive. Note that the process isn't destructive if completed successfully, but since there is always a risk of data loss when updating the firmware, I strongly recommend that you make sure that you have an up-to-date backup of your data before starting the process.

The restoration tool has a few limitations, though. First, it will require at least 10% of free space or the tool won't run at all, and there is no way around the 10% limitation other than deleting or moving files to another drive before running the tool. Secondly, only NTFS file system is supported at this stage, so Mac and Linux users will have to wait for the DOS version of the tool that is scheduled to be available by the end of this month. Thirdly, the tool doesn't support RAID arrays, meaning that if you are running two or more 840 EVOs in a RAID array, you'll need to delete the array and switch back to AHCI mode before the tool can be run. Any hardware encryption (TCG Opal 2.0 & eDrive) must be disabled too.

In regards to driver and platform support, the tool supports both Intel and AMD chipsets and storage drivers as well as the native Microsoft AHCI drivers. The only limitation is with AMD storage drivers where the driver must be the latest version, or alternatively you can temporarily switch to the Microsoft driver by uninstalling the AMD driver. Samsung has a detailed installation guide that goes through the driver switch process along with the rest of the performance restoration process. 

Explaining the Bug

Given the wide spread of the issue, there has been quite a bit of speculation about what is causing the read performance to degrade over time. I didn't officially post my theory here, although I did Tweet about it and also mentioned it in the comments of the original news post. It turns out that my theory ended up being pretty much spot on as Samsung finally disclosed some details of the source of the bug.

As most of you likely know already, the way NAND works is by storing a charge in the floating gate. The amount of charge determines the voltage state of the cell, which in turn translates to the bit output. Reading a cell basically works by sensing the cell voltage, which works by increasing the threshold voltage until the cell responds.


However, the cell charge is subject to multiple variables over time. Electron leakage through the tunnel oxide reduces the cell charge over time and may result in a change in the voltage state. The neighboring cells also have an impact through cell-to-cell interference in the form of floating gate coupling, which is at its strongest when programming a neighbor (or just a nearby) cell. That will affect the charge in the cell and the effect becomes stronger over time if the cell isn't erased and reprogrammed for a long time (i.e. more neighbor cell programs = more interference = bigger shift in cell charge). 

Because cell voltage change is a characteristic of NAND, all SSDs and other NAND-based devices utilize NAND management algorithm that takes the changes into account. The algorithm is designed to adjust the voltage states based on the variables (in reality there are far more than the two I mentioned above) so that the cell can be read and programmed efficiently.

In case of the 840 EVO, there was an error in the algorithm that resulted in an aggressive read-retry process when reading old data. With TLC NAND more sophisticated NAND management is needed due to the closer distribution of the voltage states. At the same time the wear-leveling algorithms need to be as efficient as possible (i.e. write as little as possible to save P/E cycles), so that's why the bug only exists on the 840 and 840 EVO. I suspect that the algorithm didn't take the change in cell voltage properly into account, which translated into corrupted read points and thus the read process had to be repeated multiple times before the cell would return the correct value. Obviously it takes more time if the read process has to be performed multiple times, so the user performance suffered as a result.

Unfortunately I don't have an 840 EVO that fits the criterion of the bug (i.e. a drive with several months old data), so I couldn't test more than the restoration process itself (which was smooth, by the way). However, PC Perspective's and The Tech Report's tests confirm that the tool restores the performance back to the original speeds. It's too early to say whether the update fixes long-term performance, but Samsung assured that the update does actually fix the NAND management algorithm and should thus be a permanent fix. 

The EVO has been the most popular retail SSD so far, so it's great to see Samsung providing a fix in such a short time. None of the big SSD manufacturers have been able to avoid widespread bugs (remember the 8MB bug in the Intel SSD 320 and the 5,000-hour bug in the Crucial m4?) and I have to give Samsung credit for handling this well. In the end, this bug never resulted in data loss, so it was more of an annoyance than a real threat.



View All Comments

  • damianrobertjones - Saturday, October 18, 2014 - link

    Opens Samsung Magician....

    Nope no update for me :(

    (I'm in the U.K.)
  • Coup27 - Saturday, October 18, 2014 - link

    For some reason Samsung are not offering this update via Magician, you have to download it separately from this page:
  • lord_anselhelm - Saturday, October 18, 2014 - link

    Had to uninstall my AMD SATA AHCI driver (amd_sata) twice, as the first time it redownloaded itself again from Windows Update, but thereafter it was smooth sailing via the Microsoft AHCI driver (msahci). On that note, AMD doesn't seem to want to let you uninstall it easily, as there's no option in the AMD Catalyst Install Manager to remove it. In the end I had to remove it by uninstalling the device directly in Device Manager!

    Did a quick test before and after with AS SSD Benchmark and looks as though it picked up a bit, though not too much as my drive hasn't seen too much in the way of multiple extra writes or whatnot.

    P.S. I finally bit the bullet in signing up for a new account name here as my old account name seems officially unretrievable (since I no longer have access to the email address with which it was registered).
  • Coup27 - Saturday, October 18, 2014 - link

    Testing with AS SSD will not tell you anything. AS SSD and similar benchmark programs create a new test file when they perform a test. This issue affected the read speeds of old files, files which had not been modified for months. Reply
  • lord_anselhelm - Monday, October 20, 2014 - link

    I had not thought of that :) Much obliged for the reply there :)

    It did help me to show the massive differences between amd_sata and msahci. Each has vastly different weaknesses and strengths, oddly enough.
  • LeadStarDude - Saturday, October 18, 2014 - link

    Is it safe to run the repair tool if the EVO drive being repaired is the OS drive? Sorry if this is a noob question, but better safe than sorry... Reply
  • Coup27 - Sunday, October 19, 2014 - link

    Yes. This is how a lot of people will be doing it. I did it the other day on my OS drive. Worked fine. Reply
  • lord_anselhelm - Monday, October 20, 2014 - link

    I can confirm that I carried this out on my boot drive (GPT and EFI) with no issues at all. Reply
  • bbdd - Wednesday, October 22, 2014 - link

    I guess I drew the short straw. I started running restoration software several hours ago on a 1TB 840 EVO running Win 7. The firmware update and steps 1 and 2 completed successfully, but once I hit step 3 the problems started.

    At about 80% complete, I started getting BSODs. Each time, I restart and the Samsung software seems to try to pick up where it left off. But it's slow-going, as the machine it trying to reboot at the same time. Then, it will run for some time more and BSOD again. The error mentions something about nvlddmkm.sys. From Googling, I think I have some video driver incompatibility (these are probably older drivers), but I don't understand how this software would affect the video system anyway. The hard drive light is constantly lit, so I take step 3 to be the reading-and-writing phase of the process.

    After 3 or 4 BSODs, I booted into Safe Mode to see if I could figure out how to stop the Samsung software from running on restart. Using SysInternals AutoRuns, I didn't see where it loading from. For curiosity, I started the restoration software while still in Safe Mode, it picked up where it left off, and seems to be running. Fingers crossed.
  • bbdd - Wednesday, October 22, 2014 - link

    The restoration program completed under Safe Mode. I rebooted Windows normally, everything seems to be working. Maybe it would be safer to wait for the DOS version of the program, even if you are running Windows, just to avoid any driver incompatibilities? Reply

Log in

Don't have an account? Sign up now