none
Hyper-V crashes when using the Samsung NMVe driver with the 960 Pro SSD

    Question


  • This weekend I've got my brand new Samsung 960 Pro.I've installed the Samsung NVMe Driver Version 2.1

    When creating a new virtual machine, the computer crashes with a BSOD; 

    Stop code: DRIVER IRQL NOT LESS OR EQUAL

    What failed: secnvme.sys



    Creating a virtual machine on my old SATA drive works like a charm. I use Windows 10 Pro, with the Jan 2017 updates. I've been using the new drive for two day's now, and it only seems to happen with Hyper-V. If coping other big files, the system stays stable. 


    • Edited by Dennis9347 Monday, January 30, 2017 6:38 AM
    • Moved by BrianEhMVP Monday, January 30, 2017 4:55 PM
    Monday, January 30, 2017 6:35 AM

All replies

  • Hi Dennis9347,

    I have seen similar issues caused by antivirus applications. If there is on your device, uninstall it temporarily.

    >>I've installed the Samsung NVMe Driver Version 2.1

    The issue seems to be related to the driver, I suppose you may consult Samsung technical support for better help:

    http://www.samsung.com/sg/info/contactus/

    Best Regards,

    Leo


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, January 30, 2017 8:15 AM
  • That's the support link is for refrigerators :) :( I've already contacted support via an other page.

    I use the Microsoft Windows Defender AV, disabled it, no difference. So I don't think it has anything to so with AV. 

    If there is an update, i'll post it in here...


    • Edited by Dennis9347 Tuesday, January 31, 2017 7:05 AM
    Monday, January 30, 2017 10:08 AM
  • Hi, 

    It seems that this can be the issue related to this driver. Revert from Samsung NVME driver to Standard NVME driver. 

    We can also update the firmware to check this issue: 

    http://www.samsung.com/semiconductor/minisite/ssd/download/tools.html

    Please Note: Since the websites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information. 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, February 1, 2017 3:42 PM
    Moderator
  • When not using the Samsung NVME driver, the SSD performs horrible. So that's not an option. I already have the lastest firmware. 

    This is really a serious issue, 100% replicatible, I've contacted Samsung, I'v told them what happend, gave them my sysinfo, dump file, screenshots from the crash, the error message, this is what I got back: 'they don't give feedback to end users...'  That's a shame Samsung!


    • Edited by Dennis9347 Wednesday, February 8, 2017 9:09 AM
    Saturday, February 4, 2017 6:43 PM
  • Hi, 

    Would you mind to share the dump files here for our research? 

    Please upload the file onto OneDrive and post the shared link here. 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, February 6, 2017 5:37 AM
    Moderator

  • Hi,

    I have exactly the same problem, i.e. Samsung NVMe drivers installed, 960 Pro, and systematic BSOD when creating a new virtual machine in Hyper-V. Works fine when uninstalling the Samsung driver.

    I have a memory dump, but I don't feel like publishing a public link to it. Is there a way to send it to you privately ?

    Tuesday, February 7, 2017 10:25 AM
  • Hi, 

    You can send your dump file to tnmff@microsoft.com


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, February 8, 2017 5:47 AM
    Moderator
  • Thank's for your reply, at least one of the involved companies take thier interest. I've been nagging Samsung support for an update for a week now, but I don't get an update. 

    I've send you my system information and the dump file.

    I also analyzed the dump file and;

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 000000000000001b, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff80f295d907a, address which referenced memory


    • Edited by Dennis9347 Wednesday, February 8, 2017 12:05 PM
    Wednesday, February 8, 2017 7:35 AM
  • Hi,

    It's directly related to secnvme driver (Samsung NVMe) which call memory in mistake. We have to wait for Samsung's update. Thanks for your understanding.  

    TRAP_FRAME:  ffffb180ad1c9030 -- (.trap 0xffffb180ad1c9030)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000003 rbx=0000000000000000 rcx=000000000000005a
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80f295d907a rsp=ffffb180ad1c91c0 rbp=0000000000000001
     r8=ffffdd80202c1470  r9=ffffdd80202c1618 r10=0000000000000001
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    secnvme+0x1907a:
    fffff80f`295d907a 488b4818        mov     rcx,qword ptr [rax+18h] ds:00000000`0000001b=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8023e556829 to fffff8023e54b6f0
    
    STACK_TEXT:  
    ffffb180`ad1c8ee8 fffff802`3e556829 : 00000000`0000000a 00000000`0000001b 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffb180`ad1c8ef0 fffff802`3e554e07 : 00000000`00000000 fffff802`3e55022c 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    ffffb180`ad1c9030 fffff80f`295d907a : 00000000`00000000 00000000`00000000 00000000`00000028 00000000`00000001 : nt!KiPageFault+0x247
    ffffb180`ad1c91c0 00000000`00000000 : 00000000`00000000 00000000`00000028 00000000`00000001 ffffdd80`1a84c420 : secnvme+0x1907a


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Friday, February 10, 2017 9:37 AM
    Moderator
  • I have the exact same issue. Running the Samsung v2.1 drivers for my Samsung SSD 960 PRO 1TB og it gives me BSOD everytime I create a VHD, both in HyperV and in DIsk Management, no change at all, same error and BSOD and nothing is created on the location I pick.

    I'm listening to this thread now too....hope for an update soon. Should be "easy" to find, as it happens 100% of the time.

    Monday, February 13, 2017 7:54 PM
  • Same here.

    Samsung 960 Pro 512GB on a Alienware 15 R3.

    Repeatable test with a BSOD every time.

    Tuesday, February 14, 2017 5:32 PM
  • Hi,

    It's directly related to secnvme driver (Samsung NVMe) which call memory in mistake. We cannot do anything on Client side in this case. We have to wait for Samsung's update. Thanks for your understanding.  

    TRAP_FRAME:  ffffb180ad1c9030 -- (.trap 0xffffb180ad1c9030)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000003 rbx=0000000000000000 rcx=000000000000005a
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80f295d907a rsp=ffffb180ad1c91c0 rbp=0000000000000001
     r8=ffffdd80202c1470  r9=ffffdd80202c1618 r10=0000000000000001
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    secnvme+0x1907a:
    fffff80f`295d907a 488b4818        mov     rcx,qword ptr [rax+18h] ds:00000000`0000001b=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8023e556829 to fffff8023e54b6f0
    
    STACK_TEXT:  
    ffffb180`ad1c8ee8 fffff802`3e556829 : 00000000`0000000a 00000000`0000001b 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffb180`ad1c8ef0 fffff802`3e554e07 : 00000000`00000000 fffff802`3e55022c 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    ffffb180`ad1c9030 fffff80f`295d907a : 00000000`00000000 00000000`00000000 00000000`00000028 00000000`00000001 : nt!KiPageFault+0x247
    ffffb180`ad1c91c0 00000000`00000000 : 00000000`00000000 00000000`00000028 00000000`00000001 ffffdd80`1a84c420 : secnvme+0x1907a


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thanks for your update Kate Li
    Wednesday, February 15, 2017 6:26 AM
  • I asked Samsung again for an update; nothing, 0.0, ZIP, zero very disappointed by this. 
    Wednesday, February 15, 2017 6:32 AM
  • This is the answer I got from them, which is just ridiculous:

    Dear Customer,

     
    We did come across this issue before and upon investigation from our engineers it was determined that the issue is a resulted from Hyper-V not accepting our driver. As an alternative, our engineers looked into VMware and saw that he driver works fine there and advised that this could be a workaround.

    Wednesday, February 15, 2017 9:41 AM
  • Don't drivers have to be certified by Microsoft, especially when they affect storage ?

    Wednesday, February 15, 2017 11:20 AM
  • Kate Li, I'm not saying the problem is hyper-v, but the case it not resolved, this is what I got from Samsung:

    We have found that 960 is working fine with other virtual machine software, such as VMware and Virtualbox after NVMe driver 2.1 installation.

    It seems Hyper-V has an issue and you’d better contact to MS to resolve the issue.

    ------------------------------------------------------------------------------------->8

    My answer to Samsung;

    The conclusion of Microsoft, which I share BTW, is that the driver of Samsung is illegally addressing some memory, that also appears from analyzing the memory dump. 
    The argument that other hyper visors run is a very shallow remark and one that proves Samsung support didn't investigate at all.
    Come on, do your work, that's all I ask. All you're doing now is finding reasons to avoid doing your work. Be a responsible man/woman and pick this up seriously, pretend to be a good support department. And if you don't know how to do your job, I'll help you with that (shameful but necessary);
    -install a windows 10 pro on a intel platform computer
    -install the Samsung 2.1 nvme driver
    -install the hyper-v role
    -create a hyper-v machine,And you will also see a BSOD, a memory dump is created
    -Now analyze that memory dump, and find out that the secnvme.sys is causing the crash. That's the one you, Samsung created. 
    -than you go to the software developer and start harassing them till they pick it up
    Delivering support on these technical issue's IS YOUR WORK, please pick it up seriously




    • Edited by Dennis9347 Monday, February 20, 2017 8:15 AM
    Friday, February 17, 2017 8:58 AM
  • Looks like we cannot expect anything from Samsung. What's the point in developing high-end hardware if they are unable to develop software properly... I'd rather have a working driver than a fancy (and almost useless) Magician application.

    Tuesday, February 21, 2017 4:36 PM
  • Same thing just happened to me. I decided to create a profile here just to add me to the list of watchers.

    Just installed Windows 10 fresh on my new Samsung 960 PRO drive.

    After installing Docker and restarting to enable hyper-v I had this same nasty surprise.

    Friday, February 24, 2017 12:57 AM
  • Hi!

    Same problem here.  Have version 2.1 of driver (secnvme.sys) and 960 PRO.

    Happens with both Docker (Windows Containers = Hyper-V) and "pure" Hyper-V".

    And it happens even if my VHD files are hosted on another drive.

    And it happens every time I start something, except for the "nanoserver" Docker container.

    I suppose it is because that container image is so small...? 

    Friday, February 24, 2017 10:04 AM
  • Interesting. I got Docker started by going to the Hyper-V manager, going into settings and selecting another drive for both Virtual Hard Disks and Virtual Machines.

    Pulling alpine linux successfully and running sh.


    Friday, February 24, 2017 8:06 PM
  • One week later, I've contacted several media to shine some light on this issue. No answer from Samsung, I'm gonna write another email. 

    Please everyone who have the same, reply here, the more people complaining...


    www.gourami.eu www.smspassword.com


    • Edited by Dennis9347 Sunday, February 26, 2017 10:02 AM
    Sunday, February 26, 2017 10:01 AM
  • Same Problem here on my new shiny i7 with 960 Pro 1TB.

    Just installed Hyper-v and created a VM:  a nice blue screen appeard.

    a least the "Magician" Benchmark doesn't look bad with Microsoft NVMe driver.

    But i totally agree, Samsungs work is very dissapoiting, especialy when you keep the price of the 960 pro in Mind.

    regards

    Stefan

    Monday, February 27, 2017 6:27 PM
  • Same Problem here 960Pro 2 TB.
    Tuesday, February 28, 2017 1:46 PM
  • Thanks everyone for reporting this, and please, if you also have problems creating a hyper-v machine on a samsung 960 pro post a reply here, thanks.

    www.gourami.eu www.smspassword.com

    Tuesday, February 28, 2017 4:12 PM
  • I also contacted Samsung Support and this was the answer I got:

    thank you for contacting our support!

    We are aware of the issue. Headquarters is trying to reproduce it and see if a fix/workaround is possible.

    Cheers!

    Erwin

    Thursday, March 2, 2017 2:22 PM
  • Add me to the unhappy list. Just put a new 2TB 960 Pro in my new laptop. I enabled Hyper-V, imported some VMs, and bam! BSOD. I was getting some errors on shutdown prior to that which are now gone once I uninstalled the Samsung driver. The error on shutdown/restart was "The instruction at <hex location> referenced memory at <other hex loacation>. The memory could not be written."

    I did e-mail them and hopefully the more people that contact them, the sooner we get a fix. At least it works with the native driver in Windows 10, but it's very disappointing since you're using a "crippled" drive without Samsung's driver.


    Allan Hirt Windows Cluster MVP Twitter: @SQLHA Blog: http://www.sqlha.com/blog

    Friday, March 3, 2017 11:21 AM
  • This is the answer I got back from Samsung:

    Dear Customer,

     

    Upon our engineers look into the matter they determined this issue to be with the Hyper V program and advised the aforementioned solutions. We apologize for the inconvenience in which this has caused but aside from this I’m afraid that there are no other recommendations on the matter.


    Allan Hirt Windows Cluster MVP Twitter: @SQLHA Blog: http://www.sqlha.com/blog

    Friday, March 3, 2017 6:36 PM
  • Well, if Samsung keeps on blaming Hyper-V for the problem, Microsoft should better start taking things seriously, as currently Samsung is pushing their customers to 3rd party solutions, like VMWare...

    Monday, March 6, 2017 9:14 AM
  • Could you ask for more details?, It's nice that the blame Santa, but can they provide with some foundation why?

    www.gourami.eu www.smspassword.com

    Tuesday, March 7, 2017 1:57 PM
  • Same Problem 960Pro 512Gb
    Thursday, March 9, 2017 3:14 AM
  • I am have the same issue with 512Gb 960 PRO. I had to switch to VMWare.
    Thursday, March 9, 2017 2:42 PM
  • Update on Samsung forum:

    In Samsung's initial findings, they believe the crash is being caused by a bug in how Hyper-V was accessing the driver, causing secnvme.sys to crash.

    Samsung did not find this issue when using VMWare and Virtual Box, which is why they recommened using those programs.

     

    Samsung is currently verifying and working on the issue with Microsoft. I am going to create a sticky and will update with any future updates.

    https://us.community.samsung.com/t5/Memory-Storage/Crash-BSOD-in-NVMe-driver-on-Windows-10-Pro-when-creating-a-new/m-p/76070#M243

    Friday, March 10, 2017 8:50 AM
  • Thanks P_thierry for the update! Happy that ather 1.5 months finaly something happend.

    www.gourami.eu www.smspassword.com

    Saturday, March 11, 2017 9:17 AM
  • Same problem here, 960 PRO 1TB.
    Monday, March 13, 2017 11:43 AM
  • Same problem. 960 Pro 512 GB. Nasty BSOD surprise.

    Since this is on a brand new development machine this is a serious issue. I need Hyper-V for running emulators (among which are Android VM's) to run apps under development. Using other virtualization products as Samsung suggests is not an option.

    • Edited by Marcel_v_D Friday, March 24, 2017 10:43 PM
    Friday, March 24, 2017 10:30 PM
  • On 13-3-2017 samsung updated their FAQ page; 

    http://www.samsung.com/semiconductor/minisite/ssd/support/faqs-02.html

    Stating; 

    The blue screen error (message : What failed: secnvme.sys) may appear after enabling Hyper-V in Windows 10 with Samsung NVMe Driver and 960PRO.layer close

    Samsung is verifying the cause of this issue and the solution is estimated to be available before the end of March, 2017.

    It's almost the end of March, I must say, I'm very exited :)



    www.gourami.eu www.smspassword.com

    Tuesday, March 28, 2017 8:53 AM
  • Samsung 960PRO - 512GB

    Same Problem !!

    SAMSUNG - Take this is SERIOUS - Either show Microsoft WHY Hyper-V is the root cause or FIX YOUR DRIVER !!

    Quote: "It's almost the end of March, I must say, I'm very exited :)" - ACK! - Me too ....

    Tuesday, March 28, 2017 11:44 AM
  • They have 3 days... I doubt they will have a solution any time soon.

    I had to pull my new 960 from my system because of this

    Tuesday, March 28, 2017 3:39 PM
  • Just installed Windows 10 Pro (15063.0) on Samsung 960 PRO 512 GB and the NVMe driver v2.1 from Samsung and the problem is still there. I wonder if Samsung will provide any fix by the end of March or not. For now the new drive is unusable for me, I'm moving back to my Samsung 850 Pro 256 GB...
    Tuesday, March 28, 2017 6:20 PM
  • Update on Samsung forum:

    In Samsung's initial findings, they believe the crash is being caused by a bug in how Hyper-V was accessing the driver, causing secnvme.sys to crash.

    Samsung did not find this issue when using VMWare and Virtual Box, which is why they recommened using those programs.

     

    Samsung is currently verifying and working on the issue with Microsoft. I am going to create a sticky and will update with any future updates.

    https://us.community.samsung.com/t5/Memory-Storage/Crash-BSOD-in-NVMe-driver-on-Windows-10-Pro-when-creating-a-new/m-p/76070#M243

    Considering Hyper-V is a type 1 hypervisor and VMware Workstation is a type 2 hypervisor, Samsung shouldn't and wouldn't see the same behavior.

    Hyper-V runs under the primary OS, moving it into a VM (the primary partition) where VMware Workstation runs on top of the OS as an application.  

    A lot of drivers can work poorly in this scenario, since they are unlikely tested running with Hyper-V and don't understand that extra layer of software between the hardware and the OS.

    Its disappointing that a company as large as Samsung doesn't understand hypervisor differences. 

    Tuesday, March 28, 2017 11:39 PM
  • Omg, they changed it to; 

    The blue screen error (message : What failed: secnvme.sys) may appear after enabling Hyper-V in Windows 10 with Samsung NVMe Driver and 960PRO.layer close

    Samsung is preparing the solution and it is estimated to be available in April, 2017.


    www.gourami.eu www.smspassword.com

    Friday, March 31, 2017 12:14 PM
  • Could be related to the Creators Update coming out from MS.
    Friday, March 31, 2017 10:45 PM
  • Looks it's not a problem merely related to Hyper-V.

    I have the same reproducible BSOD with "DRIVER IRQL NOT LESS OR EQUAL" message during Windows 7 backup in Windows 10 OS. It's OK with MS driver.

    Saturday, April 1, 2017 7:05 AM
  • Thanks for your message,  this does shine a hole new light on the matter...

    I assume you backup to your Samsung 960 PRO, I cannot test it because I have my Samsung 960 pro as my system disk. 


    www.gourami.eu www.smspassword.com

    Sunday, April 2, 2017 8:17 AM
  • For Windows 7 backup, I did the internal copy. - Backedup to another partition in the same drive before moving it to NAS.
    Monday, April 3, 2017 2:15 PM
  • Samsung has released version 2.2 of the NVMe driver, which is supposed to address the issue.

    I didn't have a chance to test it yet.

    Thursday, April 6, 2017 1:39 PM
  • I've just installed the new driver and it seems it is fixed :-)
    Thursday, April 6, 2017 5:25 PM
  • "We apologize for your inconvenience

    Please try again within 24 hours

    There is a daily limit on the number of this software. 
    Unfortunately, the download limit for the day has been reached, please try again within 24 hours. 
    We apologize for any inconvenience this might have caused you. Thank you."

    Come on, Samsung. Download limit on your drivers?!

    Thursday, April 6, 2017 8:31 PM
  • Peter, I saw the same error yesterday, but finally I downloaded the driver from here:

    https://www.touslesdrivers.com/index.php?v_page=23&v_code=52983

    The driver can be downloaded from here (it works already)

    http://www.samsung.com/semiconductor/minisite/ssd/download/tools.html in DRIVER section.

    Friday, April 7, 2017 4:46 AM
  • The 2.2 driver is just released. I got a heads up from the Windows PM I know who I alerted to this issue (and is why this got fixed). Big thanks to the Windows dev team here. :) I couldn't say anything before but now that it's out, I'm glad SAmsung fixed it.

    I've got 3 VMs running at the moment, no BSOD yet. Will update if things change.


    Allan Hirt Windows Cluster MVP Twitter: @SQLHA Blog: http://www.sqlha.com/blog

    Monday, April 10, 2017 11:27 PM
  • Two days ago, I've updated my system with the 2.2 driver. Hyper-V now works!< but I do need to do some benchmarking to see if the performance is still good...!

    www.gourami.eu www.smspassword.com

    Tuesday, April 11, 2017 6:44 AM