[Discussion] Which are the best NVMe drivers for Intel SSDs?

@Fernando ,
Test with v6.3.0.1022 does produce also BSODS after awake up of hibernation.
Test with v7.0.0.2268 is impossible because after v7 driver is installed (without any error message) booting PC to ‘take change modifications’ is impossible… and does not work.
I have had to restore the full system, and then finally installed the Native NVMe driver.

@100PIER :
After having tested the latest Intel NVMe drivers v6.3.0.1022 and v7.0.0.2268 with my Z170 chipset system I can confirm your find:
Both drivers gave me an "IRQL NOT LESS OR EQUAL" BSOD while trying to awake from the hibernation mode.

This does confirm a severe incompatibility issue with Intel NVMe drivers and W10 v2004 on various platform architecture.

Today I have done some additional benchmark tests with my old Intel 750 NVMe SSD running Win10 x64 Build 20246.1 on my Intel Z170 chipset system.
These were the tested NVMe drivers:
1. Intel NVMe driver v5.1.0.1003 WHQL dated 08/04/2020
2. Intel RSTe NVMe driver v7.0.0.2286 WHQL dated 04/20/2020
3. Generic Win10 in-box MS NVMe driver

Here are the results I got:




@100PIER : @MDM :
The fact, that a brandnew Intel NVMe driver v7.5.0.1990 dated 12/17/2020 is now available and my old Intel Z170 system is currently running a clean installed Win10 x64 Build 21296.1000 on my old 400 GB Intel 750 SSD, gave me the opportunity to do some new performance comparisons by testing different NVMe drivers.
These were the NVMe drivers, which I tested resp. tried to test:
1. Generic Win10 in-box MS NVMe driver v10.0.21296.1000 dated 01/16/2021
2. Intel NVMe driver v5.1.0.1003 WHQL dated 08/04/2020
3. Intel NVMe driver v6.3.0.1022 WHQL dated 01/13/2020
4. Intel NVMe driver v7.0.0.2286 WHQL dated 04/20/2020
5. Intel NVMe driver v7.5.0.1948 dated 09/16/2020 (digitally signed by Intel) - this driver was not installable (neither manually nor by running the related Installer)
6. Intel NVMe driver v7.5.0.1990 dated 12/17/2020 (digitally signed by Intel) - the test failed due to a BSOD I got while rebooting after the successful installation
7. mod+signed Samsung NVMe driver v3.3.0.2003 dated 01/21/2020

Here are the results I got:
Generic MS Win10 in-box NVMe driver


Intel NVMe driver v5.1.0.1003 (left Pic) and v6.3.0.1022 (right Pic)



Intel NVMe driver v7.0.0.2286


Samsung NVMe driver v3.3.0.2003


This post has been edited by me on 01/26/2021 (after having tried to test the Intel NVMe driver v7.5.0.1948)

I tried first to install on an secondary Windows disk (where my NVMe is just a data disk), and I think to know as to why the BSOD (I would have it probably too)…

Screenshot 2021-01-25 225325.PNG.jpg

Screenshot 2021-01-25 225550.jpg

Oh and choosing any of the offered disks type change nothing. This does not work for non-Intel disks, but would it work if YOU singed it (don’t think so…)?

@MDM :

No, I have already tested the installation with a driver, which has been signed by me.
Result: I got the BSOD again, although the NVMe Controller of my Intel 750 SSD should be natively supported by the driver.

No, I have already tested the installation with a driver, which has been signed by me.
Result: I got the BSOD again, although the NVMe Controller of my Intel 750 SSD should be natively supported by the driver.

Then there is simply something quite wrong with this driver…

@Fernando ,
Currently I do use on ASUS Sabertooth X99 a Intel i750 SSD (400GB) as the W10 x64 system disk (20H2 build 19042.746) driven by v5.1.0.1003 dated on 04aug2020 (which is quite recent).
With v5.1.0.1003 I have not observed awake or bsod problems as reported for v6.xx or v7.x branch in some previous posts.

I do hesitate to try v7.5.0.1990 because I am not sure Intel did any validation on this new branch driver on a so ‘old’ device, and may be also in my case I do suspect a X99 potential incompatibility issue.

@Fernando ,
I do observe with Intel IANVME driver v5.1.0.1003 this minor problem with Optimizer function of Intel SSD tool.
Also the ANVIL score is less than you get:



@100PIER :
The Intel SSD Toolbox is outdated and not supported anymore by Intel. Its successor is the “Intel(R) Memory and Storage Tool”. You can get it >here<.
Precondition of its usage is, that an Intel SSD is connected and an Intel SATA or NVMe driver is in-use.
By the way - this tool and the included “Intel Optimizer” are working fine with my Intel 750 SSD running the Intel RSTe driver v7.0.0.2286. Look here:

Intel Memory and Storage Tool - Overview.png

Intel SSD Optimizer.png


Thanks to let me discover this new Intel MAS Tool.
I have tested it, unfortunatly I get the same ‘optimizer’ problem:


So, is it a driver problem ?
The Optimiser function under W10 does work without any problem with this i750 device.

I don’t think so.
Which Intel NVMe driver are you using? What does the tool say about the health and the Firmware of your Intel 750 SSD?

@Fernando ,
Thanks for your comments. Here are the requested informations:




Maybe it is - after all - the driver (despite my previous answer). My advice: Try the Intel RSTe v7.0.0.2286 WHQL and execute the Intel "Optimizer" again.

I got the same ‘Optimizer’ problem with v7.0.0.2286 (IARNVME) driver, and ANVIL score is less than with the more recent v5.1.0.1003 (IANVME) driver.

@Fernando ,

I do confirm after two days I have installed Intel v7.0.0.2286 IARNVME I got sometimes BSOD when booting off my Sabertooth X99 W10 64bits 20H2 build v19042.746:


For me the v7.xx branch is not compatible with my hardware.
So, i do re-install Intel v5.1.0.1003 IANVME driver which is definitively quite stable and performant for my machine even if Optimizer malfunction under Intel MAS GUI tool…

Moreover, after the BSOD IARNVME driver problem does occur the NTFS file system is corrupted.
So, it is important to restore with a proper image system disk saved previously the driver change test, or a quicker method is to rebuild the NTFS file system disk with a 3rd party Tool such as a WinPE MiniTool Partitionner boot media which does fix the problem under WinPE environment and then W10 reboot is OK.