Problem Installing SSD PCIE Samsung960

jeroen, usually Secure Boot is disabled by default, but this may be an error from it.  Please go into your BIOS and Disable Secure Boot.  Please post your system specifications in your signature as I have.  Thanks and enjoy, John.

EDIT:  I suspect it has nothing to do with your 960 SSD.  Many users use this SSD, including me (boot device).  I suspect your install USB.  I would suggest you use MS Media Creation Tool to create a USB.  However, if you are running now and can see your SSD in W10, then use Samsung Magician to check and update (if needed) your 960 firmware.  All mine have firmware 2B7QCXE7.


Edited by MisterJ - 27 Oct 2017 at 5:04am

Yes that was the error I received. Today I tested the Samsung SSD 960 in my other system which also uses an NVME SSD. So I went on and installed Windows on the Samsung SSD 960. The same error occured. So I identified the error as being a corrupt SSD.

I can try to update the firmware of the disk.


Edited by jeroen - 27 Oct 2017 at 8:27pm

Hello John,

Edited by jeroen - 28 Oct 2017 at 6:48am

MisterJ, just a thought about the Windows instillation error you have (had?) there. Not sure if you are still trying to deal with it.

IIRC, you incorporate drivers into your Windows 10 installation, the AMD NVMe RAID drivers, is that correct?

Again IIRC, another ASRock X399 user trying to use the AMD NVMe RAID, whom installed the AMD NVMe RAID drivers manually in a Custom install, said while installing the RAID drivers, he received the digital signature error too. He was able to select "install anyway", as we can when we install software without the digital signature in Windows. Obviously we are not given that option with incorporated drivers, correct?

Just a thought to get past this if it remains a problem for you.

Also, I would respectfully suggest installing Windows with the NVMe RAID drivers on a SATA SSD temporarily, that would then allow you to experiment with creating an NVMe RAID array. I did that with Intel's NVMe RAID to get a feel for how it works and IMO it really helps instead of doing it the first time and attempting to install Windows. I found some subtle issues involving the UEFI, the fixes were actually incorporated into the UEFI by ASRock. They may have learned that on their own, but I verified "in the wild" that it needed to be done.

The point is, who knows what you might find. Much less frustrating to find this on a test array.

MisterJ wrote: Thanks, parsec.  I injected the RAID drivers into all three images (2 boot and install).  I removed the one from the install image and it works on VM.  I get no errors on injection and am not using the /ForceUnsigned option.  I tested the RAID driver files with SignTool and all was OK.  I would like to read the the post of the user with the signature error.  Can you provide a link?  Injecting has always work for me on W7 and W10, just have not used a RAID in a while.  Thanks for the suggestion, though.  Thanks and enjoy, John.

So you no longer have that problem? I'm confused from your post, sorry.

I haven't looked yet, but it was one of the very few threads about AMD NVMe RAID. I'm sure you posted in that thread too.