Samsung Nvme Driver 3.3

0 views

Skip to first unread message

Lane Frisch

unread,

Aug 3, 2024, 11:52:48 AM8/3/24

to reiclearveskey

I have a Dell Inspiron 7373 13" laptop which is fitted with a 256GB SATA M.2 SSD. The Dell spec for the laptop states that it can use either SATA M.2 SSDs or NVMe M.2 SSDs. So I ordered a Samsung 970 Evo Plus NVMe M.2 500GB SSD.

Finally I shut down the laptop, removed the rescue USB and restarted the laptop but it would not boot into Windows. I tried a boot repair using Macrium and it reported that all was good but the laptop will still not boot from the new drive. I also tried a Windows boot repair but this also failed to solve the problem.

I have checked Samsung's website and they have an exe file download for installing the NVMe drivers. So I put back my old SATA SSD into my laptop and booted into windows. I checked the device manager for installed drivers and sure enough there was no NVMe driver installed under disk controllers, only SATA driver. So I tried to install the Samsung NVMe driver before taking another image but it will not install the drivers unless a Samsung NVMe SSD is present.

I am now struck, I cannot install the NVMe driver unless the drive is installed but if I install the drive it will not let me boot into windows to install the driver! One thought was to purchase a NVMe external enclosure so I can connect the NVMe SSD via the USB3.1 port, this may then enable me to install the NVMe drivers before I cone the SATA SSD.

I was upgrading my laptop from an M.2 sata to a larger M.2 nvme drive. I used an external M.2 USB enclosure and Acronis to make a clone of the original drive. I installed the clone into the laptop but it wouldn't boot (inaccessible boot device). What worked for me was simply booting into safe mode once. Apparently this enabled the NVME driver to run at boot time from then on.To do this - When the boot fails and goes to the recover screen select:Troubleshoot->AdvancedOptions->AdvancedStartupOptions->StartupSettings, then select Restart. When the computer restarts enter the number (4) for EnableSafeMode. Let safe mode come up, login and restart the computer.

I was advised by Macrium to try booting into Windows in safe mode. They thought that loading Windows in safe mode with a minimum drivers, etc may enable Windows to boot far enough to find the new drive and load the NVMe drivers. I tried this and it worked! Once I was in Windows in safe mode I went to Device Manager and sure enough the Windows NVMe driver had been loaded and the drive was present.

I then logged out, shut down and restarted the laptop in standard mode and everything loaded as it should. I have now updated to the Samsung NVMe SSD driver and run some diagnostics and benchmarks. All is running as it should and much faster!

I had the same problem installing Samsung Evo plus and wanted to share what i did in detail from the helpful advice above. There where steps missing that i had to research before I was successful. This might be an easy list to follow for folks who dont know how to access command prompt.

The generic Microsoft NVMe driver seems to be called stornvme. (For comparison, the generic SATA AHCI driver is storahci, though Intel RST has a different name.) You can change its configuration using sc from an administrator Command Prompt:

I did the same but from a 256 GB nvme SSD to a 1TB one.I used the 'create system recovery option' in Windows 7 backup (available in Windows 10/11), wrote it to an internally attached HDD.Replaced the SSD, booted from a recovery USB stick and restored the system image.The system gave a 'Unaccessible boot device' after initial boot, and system repair could not fix it, neither the manual bcd options through a dosprompt (windows 11 does not have the boot folder on the system disk, but on a separated hidden partition)I then booted in safe mode, did a CHKDSK /F and rebooted. It all worked, only the partitions where as small as on the original ssd. Used a 3rd party partition tool to move and enlarge the partitions.All works great now.

I tried several of the suggestions on this forum as my device would show in windows and bios but would not boot. The issue was my boot was set to legacy for storage and pci devices so changed to UEFI then had to convert the drive to GPT and finally booted my Evo 970, would have long given up without this thread ! Thanks everyone ?

Update:
Meanwhile I was able to find out the reason for my reported issue and to solve it.
Reason (very mysterious): The NVMe Controller of my other NVMe SSD (a 1TB Samsung 990 Pro) used the generic Phison NVMe driver v1.5.0.0 WHQL.
Solution: After having replaced the generic Phison NVMe driver by the generic MS Win11 in-box NVMe driver stornvme.sys everything was fine.
Here is the screenshot of the Dashboard after having solved the problem:
WD Dashboard works now1362782 124 KB

Have my first issue with my very first build after using computers and remembering the days before the interweb. I intended to be ambitious and to maybe over build with some headroom for future upgrades. Whatever I own I do try to ensure I get the best out of it and to that end I am bumping against installing Win10 after Raid 0 the two drives within the Bios. I have gone through the videos of trying to load bottom drivers then raid config but i still get get the windows setup to see them as raided drives. I need a detailed idiots guide rather than a detailed expert guide if that makes sense. Any help with videos or pdf's......at 43 I am feel it might be like teaching someone to use a spoon. Will continue my own searching and googling as there must be something I am missing.

3.Enter the Raidxpert2 menu in BIOS, you need to initialise (writes some data to the drives to prepare them for Raid) all hard drives that will be used for Raid. This option will be in the Raidxpert2 menu, so check all options.

I try raid 0. In bios I'm creating raid, and at first glance everything is fine (I can add screenshots from the BIOS). Then I made a bootable USB flash drive and added drivers there. During installation, I add 3 drivers sequentially from the DD folder, they are installed, but still two nvme disks are displayed.

Strange thing. tried again from the beginning. In the BIOS, I left SATA in AHCI mode (before that stood in raid), and nvme as raid. I got to the driver installation and this time I could not install anything from the nvme_did folder, the list was empty, like "incompatible with my equipment". But from the nvme_cc folder (for a different processor) - success, and one disk appeared! While everything seems to be established and working, I observe.

I used the NVMe_DID drivers, browsing to and then installing rcBootom, RCRaid, and RCfg in that order. It made no difference - after installing all three drivers and doing a refresh, the Windows installer still sees two separate NVM drives and can't install.

However, from reading AMD NVMe/SATA RAID Quick Start Guide for Windows Operating Systems I've seen that this can happen when the system has multiple controllers, so no problem - I choose the first one.

Yes, drivers will be provided and added to that page when they become available. For now you can use the previous drivers for Windows 11. I am using them on my Windows 11 installation with 2 drives in Raid 1 configuration.