i am not so surprised by the shutdowns bugs...because i tested a lot at the hard-drives level few mainboards when i redistributed my hard-drives onto 3 computers ; what i saw with the sabertooth x79 with some ssds and big hard drives , is that if you use chkdsk of win 7 then reboot with win 10 that starts a new check of disc...when you reboot to 7 then a new check...; with a supermicro mainboard that has an adaptec chip connected to the ichr10 according to the mode of the ichr10 : ahci or raid or raid-adaptec : some partitions were readable or not , or drives where needing a new mbr signature . all were readables with raid modules but not ahci , hd are 4k cluster and finally the best choice is the ichr10 raid mode .
may be the samsung driver works well with win7...

Well, I thought this new driver would fix the unsafe shutdown thing, but I my system it still exists. I installed the driver version 2.1 on 1-10-2017. As you can see from the pic I have 2 new entries since then.

@denaba
I am in contact with Samsung SSD Division Europe.
I have already reported and documented this issue.
They are working on this issue.
The other major issue is the 960 devices drop out after PC Restart.
According to my tests it seems now fixed for 960 EVO updated with the new firmware .
However for 960 PRO the drop out problem does remain...

Samsung 950 PRO as system drive, Windows registers 'unexpected shutdown'. Simply unplug so this error will disappear forever...|addpics|8jw-1-9c17.png|/addpics|

@antonov_063,
I can't read your screenshot, however the "unplug" does not fix any of the problems.
I have done lot of 950 PRO "unplug" when doing tests, months after months, the 950 PRO 'unsafe shutdowns' does progress and W10 x64 'unexpected shutdown' no longer disappeared on my P8Z77 system.

@100PIER - thanks for the reply. Just keeping everyone appraised on my results.

Thanks for your efforts in notifying the folks!!

Zitat von 100PIER im Beitrag #35

---

@antonov_063,
I can't read your screenshot, however the "unplug" does not fix any of the problems.
I have done lot of 950 PRO "unplug" when doing tests, months after months, the 950 PRO 'unsafe shutdowns' does progress and W10 x64 'unexpected shutdown' no longer disappeared on my P8Z77 system.

---

Zitat von denaba im Beitrag #32

---

Well, I thought this new driver would fix the unsafe shutdown thing, but I my system it still exists. I installed the driver version 2.1 on 1-10-2017. As you can see from the pic I have 2 new entries since then.

---

@MirceaForce
To complete my post #33, 960 PRO and also 950 PRO are both concerned with the 'unsafe shutdowns' problem.
At the moment I ignore how Samsung will fix this problem which is ancient.
They are working on because Samsung NVMe driver v2.1 did not fixed the problem.

Zitat von 100PIER im Beitrag #39

---

@MirceaForce
To complete my post #33, 960 PRO and also 950 PRO are both concerned with the 'unsafe shutdowns' problem.
At the moment I ignore how Samsung will fix this problem which is ancient.
They are working on because Samsung NVMe driver v2.1 did not fixed the problem.

---

I have same issue on 960 pro. Windows events log shows "unexpected system shutdown" and started system drive check on the next boot, but ssd's SMART shows zero unexpected shutdowns increment. What to do?

@beavis,
When using Samsung v1.4 NVMe driver I had many "unexpected system shutdown" logged in Reliabilty Windows Report, and when replacing it with MS native NVMe driver the problem was less present.
At the moment I recommend to use Samsung v2.1 NVMe driver.
The SMART '0D' parameter 'unsafe shutdowns' does not seem correlate with the 'windows unexpected system shutdown'. It is strange.
May be we have to wait for a new Samsung driver to no longer observe these problems ?
For 960 PRO may be we have also to wait for a new firmware version as it was done recently for 960 EVO ?
On my side the SMART 'unsafe shutdowns' does increment for 960 PRO and 960 EVO.

uninstall samsung drivers and restart and voila the problems are gone....

Something else I just found out on driver 2.1. I was having a lot of popping in my speakers so started some troubleshooting. Long story short I got to check DPC latency and low and behold I had higher than 2000 readings. I used both DPC Latency Checker and Latency Mon. Disabled items and no change, but got to changing the drivers to the nvme and then I had way better latency readings. Used the Microsoft driver and also the 2.0 driver and now my latencies are hovering at 1000 and no pops. I installed 2.1 again and after rebooting my readings once again shot up over 2000 so 2.1 seems to be really buggy, I'd stay clear of 2.1

Update: Adding before and after pictures|addpics|efk-4-6e22.jpg,efk-5-61a0.jpg|/addpics|