SP3 SSD, possible firmware bug, same as just fixed in another Samsung drive.

Anonymous
2014-10-20T22:49:51+00:00

I've just had to update the firmware in another device that had a Samsung 840EVO SSD because they had a serious firmware bug with it.  Out of curiosity I tested the Samsung drive in my Surface Pro 3 and it looks like it has exactly the same issue (the SP3 drive is closely related to the 840 series I believe, but an OEM version.

The test is simple, just look at the read rate across the drive.  Older data (OS, installed apps) suffered from terrible read performance after a month or so.  Newly written data is fine.

As you can see, much of the drive is down to 50MB/s now.  It should be a fairly level line right the way across at about 350+MB/s.  This test was run with AC power connected and nothing else running.

If this is the same issue as the 840EVO, the good news is it can be corrected with a firmware update and refresh of the data.  Bad news would of course be Microsoft need to look into it first, then get the Samsung engineers looking into it.

Perhaps some other people could run the test too, and post results.  Remember the drive needs to be a month or more old, so that the data can have been sitting there only being read during that time.

Further details of the bug and the fix that Samsung released can be found here:

http://www.anandtech.com/show/8617/samsung-releases-firmware-update-to-fix-the-ssd-840-evo-read-performance-bug

Surface | Surface Pro | Install and update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2015-09-30T22:01:46+00:00

Hello all

We wanted to let you know that an update to resolve this is still being worked on.  Please continue to post your experiences and technical details.

Mod Edit: Samsung SSD Optimization Utility for Surface Pro 3 now available.

Best regards

Was this answer helpful?

0 comments No comments

151 additional answers

Sort by: Most helpful
  1. Anonymous
    2014-11-18T18:53:14+00:00

    Here's my surface i7 256gb I bought in August in Vancouver Canada

    Before

    After

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-11-11T22:25:19+00:00

    SP3 128GB. Owned for almost two months.

    Thanks!  But for anyone else please note that it is just the performance graph as your system currently is that is what we need to see.

    Doing an optimize or TRIM on it's own won't help since your system does that while in use anyway, every week and for every file you delete.  Also there is no need to run DiskFresh, unless you really want to.  The performance graphs before running that already seem to be clearly showing the problem I originally posted about is present and that is what we could do with more examples of.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-11-11T04:58:34+00:00

    SP3 128GB. Owned for almost two months.

    Prior to manual TRIM

     Post manual TRIM

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-11-09T15:14:11+00:00

    Thanks for confirming that the standard "Optimize and Defragment" tool does do the trimming of unused space.  I understood that both crozone and CtitanicMVP were pointing to this tool, but just wanted some confirmation that the tool in fact trimmed all parts of the partition not currently in use (rather than trimming some set of things that Windows remembered had been deleted and were pending trimming or some other subset of all free space), and you all have certainly assured me that this is the case -- the trim done by this built-in Windows tool truly is trimming all free space.  Yes, the only point of this is to make life better for the drive for wear leveling and when it comes time to do future writes.  Reading trimmed space, as does HD Tune, is only interesting for these diagnostics.

    Was this answer helpful?

    0 comments No comments