[SOLVED] Samsung SSD 860 EVO very slow Read speed

Apr 1, 2020
2
0
10
Hi,

I have two 860 Evos in my system the OS one is fine but I have just ran a benchmark in Samsung magician on my second B drive which is used as a Games Library and the Sequential Read/Write is way of 9/490 MB/s. I have also noticed alot of texture popping in games on this drive and have now put this issue to be the cause of that.

I have reached out to Samsung and awaiting a reply from them but was wondering if anyone has had this issue before?

I can try to provide more information if required.
 
Solution
Did Samsung get back to you with a solution? I'm having similar issues with my 860 EVO. In my case it's not 100% persistent, I can get some hours where it performs normally at roughly 500 read and write, then it just tanks. Samsung Magician's benchmark shows history, and the numbers for the previous tests I did are:

Sequential Read (MB/s)Sequential Write (MB/s)Random Read (IOPS)Random Write (IOPS)
5615308422878613
15298471674707
152924476171

I find this completely baffling. I only just installed Magician and I don't remember from my previous...
Did Samsung get back to you with a solution? I'm having similar issues with my 860 EVO. In my case it's not 100% persistent, I can get some hours where it performs normally at roughly 500 read and write, then it just tanks. Samsung Magician's benchmark shows history, and the numbers for the previous tests I did are:

Sequential Read (MB/s)Sequential Write (MB/s)Random Read (IOPS)Random Write (IOPS)
5615308422878613
15298471674707
152924476171

I find this completely baffling. I only just installed Magician and I don't remember from my previous CrystalMark tests if only reads were affected.

I don't really think is specifically an EVO issue, because the reason I have the EVO in my system is that I changed out a Crucial drive that I'm pretty sure was having similar issues (although I did not troubleshoot that in the same way so I cannot be certain). If that was the same, not actually a failing drive, then it points to OS or motherboard/UEFI to me.

I updated the firmware for the EVO and it behaved fine for an entire evening, unfortunately the issue returned the next morning, dashing my hope that the solution had been found.

I should point out that I have another SSD and two M.2 drives in the system that all perform flawlessly. I'm considering hardware troubleshooting like swapping out the SATA cable at this point.
 
Solution
Did Samsung get back to you with a solution? I'm having similar issues with my 860 EVO. In my case it's not 100% persistent, I can get some hours where it performs normally at roughly 500 read and write, then it just tanks. Samsung Magician's benchmark shows history, and the numbers for the previous tests I did are:

Sequential Read (MB/s)Sequential Write (MB/s)Random Read (IOPS)Random Write (IOPS)
5615308422878613
15298471674707
152924476171

I find this completely baffling. I only just installed Magician and I don't remember from my previous CrystalMark tests if only reads were affected.

I don't really think is specifically an EVO issue, because the reason I have the EVO in my system is that I changed out a Crucial drive that I'm pretty sure was having similar issues (although I did not troubleshoot that in the same way so I cannot be certain). If that was the same, not actually a failing drive, then it points to OS or motherboard/UEFI to me.

I updated the firmware for the EVO and it behaved fine for an entire evening, unfortunately the issue returned the next morning, dashing my hope that the solution had been found.

I should point out that I have another SSD and two M.2 drives in the system that all perform flawlessly. I'm considering hardware troubleshooting like swapping out the SATA cable at this point.
Hi, yes Samsung got back to me and noted my CRC number was very high and advised to change the SATA cable. I done this and the drive now works 100%. I would say try changing out the SATA cable for a new one.
 
Thanks for getting back to me. Coincidentally, I was digging through my box of spare cables looking for one as the notification for this ticked in. I've swapped it out now, so fingers crossed this does the trick. Since it was intermittent for me I can't really know for a few days, but first benchmark ran OK at least.

Update: It's been a few days now with no issues. At this point I feel fairly confident in saying that this did indeed turn out to be a faulty SATA cable for me as well.
 
Last edited:
Hi, yes Samsung got back to me and noted my CRC number was very high and advised to change the SATA cable. I done this and the drive now works 100%. I would say try changing out the SATA cable for a new one.
Chiming in to say thanks as well. I had the same problem. Two 860 EVO's, my 250GB OS reached over 560mb/s read speed, the second 500GB storage one 34mb/s. For me the solution wasn't in changing the cable but to simply use another SATA port on my motherboard, so I guess the issue is in the port.
 
Last edited: