cancel
Showing results for 
Search instead for 
Did you mean: 

Intel 750 400GB PCI-E w/3.1 NVMe Driver Issue

bdcintel
New Contributor

I have the Intel 750 400GB PCI-E NVMe drive in a Asus z170 board running Windows 10. In the past, I've upgraded from the 1.8 to the 3.0 NVMe driver (and all previous driver versions) without issue for the past 2 years.

Starting with the 3.1 driver, I have been having issues updating. If I install the driver from Device Manager, the system reboots and Windows will fail to load. Windows attempts a repair but fails. The only option is to reinstall the OS.

If I attempt to do a clean install and "load driver" and select the 3.1 driver, the OS will not install, I just receive a generic error that it cannot proceed when loading that driver. I have to use the 3.0 driver.

The 750 400GB PCI-E drives are listed as compatible with the 3.1 driver, what is going on?

18 REPLIES 18

idata
Esteemed Contributor III

Hello BDCIntel,

Thanks for letting us know about this situation, we would like to investigate on this as we have not received reports of the driver failure.We will be testing one of our drives as well, in the meantime, could you please provide the following:-Firmware version on the SSD?-Computer's specs (https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows- Please use this utility) and attach the file here.We'll be waiting for your response while we work on this as well.Regards,Nestor C

bdcintel
New Contributor

Thank you for taking time to look at this issue.

Drive Firmware: 8EV101H0

I have also attached my system support tool export.

idata
Esteemed Contributor III

Hi BDCIntel,

Thanks for providing this information, we will continue with our research on this situation and we will keep you posted with any updates.Regards,Nestor C

Hello,

I have the same problem with two x99 systems and a Dell Optiplex-3010. The SSD also has the latest firmware. The system runs with drivers up to v1.8. After installing the drivers v3.0 or later, the system will only start in recovery mode. This problem also occurs with firmware 8EV101F0.