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: Most helpful
-
Anonymous
2015-10-01T17:05:11+00:00 If (as you say) it's more likely this person has 0 connectivity with SP3 SSD subsys devs/engineers, & isn't relaying a msg that's rooted in some real progress coming soon(TM), & instead is just offering platitudes, well than, that's worse, much worse. If you assume I think the poster's one of those devs/engineers, you'd be assuming incorrectly.
-
Anonymous
2015-10-01T16:44:40+00:00 C'mon now, that's all you can manage after such a huge length of time.
Surely you can be more specific about:
You are assuming the person posting this reply is somehow directly related to the team working on this.
More likely its a generic message which is in no way related to the Surface team.
-
Anonymous
2015-10-01T06:59:04+00:00 John, thank you for letting us know that a fix a still being worked on. Are there specific technical details that we could share that would help move the solution forward or is the need more to continue expressing our desire for a solution so that resources get allocated?
Ed
-
Anonymous
2015-10-01T05:39:59+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
C'mon now, that's all you can manage after such a huge length of time.
Surely you can be more specific about:
(1)
Rough time-line for delivery
(2)
What fix(es) you think you've managed to devise (go into some technical detail)
It's the least you can do given this entire farce...
Many of us remain your best advocates -despite some pointedly poor service.