Using 1809 with the standard built-in NVMe driver works perfectly with my 970 EVO 500 GB and 250GB drives running in the system. Using 1809 with the Samsung ver. 3 NVMe driver works perfectly with my system with either the 970 EVO 500 GB or the 250GB drive. However using 1809 with the Samsung ver. 3 NVMe driver makes my system BSOD after returning from sleep with my 970 EVO 500 GB and 250GB drives running in my system. All logic points to a Samsung driver issue, when the Windows 10 built-in driver works, but the Samsung ver. 3 does not.
... View more
I have found that the NVME ver. 3 driver is the culprit. I have recently bought two 970 EVO drives; first a 250 GB version, but after running with it for a while I found 500 GB at a nice price. Running either the 250 or 500 GB version *alone* with the NVME ver. 3 driver works just fine. My motherboard, the ASUS X99 SABERTOOTH, only comes with one M.2 connector, so I purchased two different NVME to PCIe adapter to attach the second 970 EVO (the one without Windows 10). This made my system crash after resuming from sleep with the BSOD INTERNAL_POWER_ERROR message (I have to wait a couple of minutes to invoke the error, because if I resume the computer to quickly it will work just fine). Same error with the two different NVME to PCIe adapters. I then found this thread and this one: https://www.tenforums.com/bsod-crashes-debugging/119040-bluescreen-after-1809-october-update.html My next step was to remove the Samsung NVME ver. 3 driver and that fixed my BSOD issues completely! I am currently running with the built-in driver from Microsoft. So Samsung please get cracking at fixing the driver so that your customers experiencing the bug can install the driver (again) - thanks :-)
... View more