My long story short, I've replaced the evo ssd with another, which behaved exactly the same. At least using storahci drivers it's stable, but C7 errors keep accruing, and writes are crippled. Interestingly, it works perfectly fine on the asmedia controller, though slower, and without full support of things like virtualization.
I've finally replaced the Samsung 860 Evo with Crucial MX500 and the magic happened! No more issues of any kind on the SB950 controller using storahci drivers. I'll next update to amd drivers, just to check the difference, but it works fine as it is.
Both samsung ssds went back to amazon with a detailed 1-star review of the drives. Shame on you Samsung engineering!!
Exactly like others said. I am running Linux as well, so it took me a while to figure out it is 860 EVO (I have two, so ruled out it is not only the first faulty, I tried to find other causes, which wasted more time). Luckily I have 970 EVO in the system and that worked OK for now. Need to order more though, didn't plan it as the main storage.
This is a big waste of time. AMD / Samsung should simply mark their products as imcompatible to save everyone's time.
When I used the Microsoft AHCI driver, things seemed to work, but CRC errors were still building up in the SMART data. I'm not sure if that is an issue long term or not.
Update today March 27, 2019.
Using the Inland Professional SSD 120gb
I just ran CrystalDiskMark . Note the version top of the picture, and the size of the drive left. I have almost filled the drive. This is THE drive I mentioned before.. that was the 'pos' drive.
I use this drive as my main SSD. I am pondering on getting a Crucial mx500 250gb or maybe another Inland Pro.. the price is just to cheap. I have not followed other threads or took note if anyone was having issues with Win 10 drivers. I am using Win 7 64bit right now.
3 web pages open when I ran the test.
Notice the scores of
As far as the 9-series and below chipset versions from AMD are concerned:
- There were lots of issues and bugs due to "performance" vendor-specifc drivers that were never resolved ... there are chipset level bugs like SB950 cannot use MSI (Message Signalled Interrupts) ... and then there are driver issues like with RAID drivers, any activity to probe the status of disk can cause the system to hang or even crash
- After the latest driver (AHCI win 8 and above ... 1.3.001.0277) went missing ... AMD started recommending the "generic" Microsoft Drivers for stability (note that even though driver date might be 2006, it is an updated driver as seen from the win build version in the driver version string) ... one can still try the driver version 220.127.116.112 (for win 7 ... though win 10 can use it as well) or 18.104.22.1686 (for win 8 and above) as these are mostly well liked ... for RAID drivers there might be similar options
So, one can try different driver versions or get an add-in card with a known good chipset!
I have absolutely no problems with SB950, no instabilities, no crashes whatsoever. That is using SSD Crucial drive and 4 Seagate HHDs. The only system wide serious problems I had where when the Samsung drive was connected.
Seems like you're blaming both AMD and Windows drivers for all problems. We all know AMD and MS are not perfect, but your logic is backwards. Crucial drive works perfectly fine. Are you saying the Samsung drive is so special both AMD and Microsoft should've created special drivers for it?
You seem to have misunderstood me! I meant to say that there can be a number of reasons for the problem but one is unlikely to get a fix due to the low chance of getting vendor specific updated drivers from AMD ... why AMD and not Samsung? Because AMD abandoned their chipset driver development in my opinion ... they were overwhelmed at that time (2015) ... it was difficult to balance performance vs stability ... I did not mention the drive itself because it works for some people obviously since it is so highly rated ... it is also a question mark whether or not the issues highlighted below were ever fixed in the generic driver from Microsoft??? (links to wikipedia as original sources are mostly dead)
See also: SB950 Product Errata https://www.amd.com/system/files/TechDocs/49645.pdf
These lines are also present in the Installation Guide for the Magician software:
"Sometimes on AMD PC with AMD and ASMedia storage controllers it was found that the IOs takes a longer time to complete. In such cases if Rapid was enabled, it may get automatically disabled due to such IO errors. It may display "Rapid is in inactive state". User has to reboot the PC to enable the Rapid back.
10) If multiple iterations of Read and Write are performed, RAPID mode may become inactive due to system internal errors on some of the AMD / ASMedia Controller or Driver. "
The fix other than the obvious one of not using this particluar drive that I could come up with is to either try a number of drivers to see if one works or to get an add-in card if this drive is to be used with a chipset known to work with this drive!
I myself have a system with the SB950 southbridge ... would have liked to see this drive work as well because I was looking to get one some time ago especially after trying out an older model one from Samsung ... fortunately I installed some other brand's ssd because I had no idea back then of these issues!
I had the exact same problems, both with Windows and Linux.
After some digging, I found out that there seems to be an incompabilty between the AMD SB710/750 chipset and newer Samsung drives when using NCQ.
There are two ways to fix this:
1) Disable AHCI in the BIOS and switch to IDE
2) Disable NCQ only
Option 2 should be prefered because AHCI without NCQ is still better than pure IDE.
Disable NCQ on Windows: https://superuser.com/questions/1294158/what-may-cause-very-high-crc-errors-on-ssd-apart-from-bad-sa... (see Falcosoft's answer!)
Disable NCQ on Linux: Use grub parameter "libata.force=noncq"
After disabling NCQ, all my CRC problems vanished.
Hope this helps.