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
SP3 SSD, possible firmware bug, same as just fixed in another Samsung drive.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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:
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.
Answer accepted by question author
Anonymous
151 additional answers
Sort by: Newest
-
Anonymous
2015-12-08T22:22:56+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.
Best regards
Almost another month has gone by; can we get some more information on a potential fix please?
-
Anonymous
2015-11-19T07:01:43+00:00 Just as a followup to my post above. I have run the diskfresh tool mentioned earlier in this thread and while I understand that it's not a "final" solution it was pretty painless. It took about an hour or so, but you could continue to use the Surface as normal while it did it's thing. Windows 10 (with update) SP3 i7 - 256GB about half full.
While there's not a massive improvement in the average speed, it made a pretty dramatic improvement to the consistency of the HD Tune graph.
-
Anonymous
2015-11-17T05:53:48+00:00 Surface Pro 3 i7 - 256GB about 1 year old and just over half full :-(
I look forward to seeing a fix for this... like others I've been hesitant to try out the previously linked driver given it was pulled so quickly and is no longer available.
While we're waiting for a proper fix, is there any advice or direction you could give us on whether we should (or shouldn't) apply the previously available firmware? Its still available on several mirrors.
Cheers,
Dave
-
Anonymous
2015-11-16T12:16:56+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.
Best regards
Again, not to trying to pester here, but it has been almost another month and I've not heard any word on whether this issue is being addressed anymore or not. Can we get an update with some tangible details, please?
You don't have to feel like you're "pestering", this has gone WAY beyond the point of any SP3 owner having to feel guilty of doing that, this is bordering on sheer negligence/incompetence.
Get your proverbial together MS, pronto, this combined w/the HEAVILY doco'd & serious Wifi/Power issues some folks are having (happy to say I'm not one of them), & I smell a class action in the air.