Can't get Samsung 960 EVO 500GB to work

admiral.weppas

Prominent
Oct 21, 2017
11
0
510
Core i5-8600K, AsRock Z370 Extreme 4

I just can't get it to work. It shows up in Bios. When i disable CSM it won't show up as a bootable drive anymore.
Both with CSM enabled and disabled, during Windows Setup it doesn't show up as a drive.
Tried to clone my existing windows on it. It's listed under device manager, but disk management doesn't show it.
 
Solution
I do hope you get some substantive assistance from ASRock. Based on our experience it's something of a crapshoot. Sometimes you're lucky enough to reach a competent technician who provides a sensible solution to the problem. Other times...

As for Samsung, you definitely should contact that source. Hopefully they'll be responsive.

admiral.weppas

Prominent
Oct 21, 2017
11
0
510

upgraded the motherboard 2 weeks ago. and did a fresh install on my ssd. got the m.2 yesterday
 
Cloning your existing windows may be a problem as the NVMe drive uses its firmware during a UEFI install to operate properly. That's something your current installation lacks.

NVMe SSDs do not appear within the BIOS until Windows creates the system partition with the EFI Boot Sector. Your M.2 SSD contains UEFI driver information within the firmware. By disabling the CSM module Windows will read and utilize the M.2-specific UEFI driver.

Guide for installation:

1- The M.2 drive has to be the only drive installed.

2 - Go into the bios, under the boot tab there is an option for CSM, make sure it is disabled.

3 - Click on secure boot option below and make sure it is set to other OS, not windows UEFI.

4 - Click on key management and clear secure boot keys.

5 - Insert a USB memory stick with a bootable UEFI USB drive with Windows 10 Setup on it, USB3 is quicker but USB2 works also. A Windows DVD won’t work unless you’ve created your own UEFI Bootable DVD.

6 - Press F10 to save, exit and reboot.

7 - Windows 10 will now start installing to your NVMe drive as it has its own NVMe driver built in.

8 - When the PC reboots hit F2 to go back into the BIOS, you will see under boot priority that windows boot manager now lists your NVME drive.

9 - Click on secure boot again but now set it to WIndows UEFI mode. (see #3 above)

10 - Click on key management and install default secure boot keys

11 - Press F10 to save and exit and windows will finish the install. Once you have Windows up and running, shutdown the PC and reconnect your other SATA drives.

I would also recommend installing the Samsung NVMe driver at this point to replace the Windows one. (optional)

** How to create a bootable UEFI USB drive with Windows 10 Setup
https://winaero.com/blog/how-to-create-a-bootable-uefi-usb-drive-with-windows-10-setup/
 

admiral.weppas

Prominent
Oct 21, 2017
11
0
510


My problem with this guide is, that i cant recreate point 3. I don't have the option to set it to other OS.
https://imgur.com/IlNNbY1
https://imgur.com/iYoKPB1
 
1. You indicate that you have "tried to clone my existing windows on it", the "it" obviously referring to the Samsung M.2 SSD. So that indicates you're working with a bootable drive that you presumably tried to clone its contents to the Samsung SSD. Is that right?

2. So what's the present bootable drive? A HDD or another SSD? And that drive contains a viable OS (which is?) that boots without incident and functions problem-free in your present system? Or is there a problem with the present boot drive's performance in your current system? Provide the total data contents on that drive, OK?

3. Presumably you've properly installed/connected the Samsung M.2 SSD in your system, right? So what PRECISELY happens during your disk-cloning operation? What precisely is the problem here? You get some message from the d-c program of a problem? Or the d-c operation seems to proceed normally but you still cannot boot to the cloned Samsung SSD? What has happened? And what d-c program are you using? The Samsung Data Migration program?

4. Can we assume that all things being equal your preference is to clone the contents of the existing boot drive to the Samsung SSD?

Please understand you must clearly & precisely detail the problem you're experiencing and provide specific information re the system components you're working with.
 

admiral.weppas

Prominent
Oct 21, 2017
11
0
510


I have an Samsung 850 SSD with Windows 10 installed on it. I have a new M.2 SSD and want Windows on it. Doesnt matter if I clone my existing one or if i do a fresh install on my M.2. Just want it to work.
Can't clone because Windows Disk Management doesn't recognise the M.2
 

admiral.weppas

Prominent
Oct 21, 2017
11
0
510


Yes and yes.
The m.2 Drive doesn't show up in samsung magician. nor does it in disk management. shows up under drives in device manager tho.

 
It's truly a puzzle. The only recourse I can envision at this point is to contact Samsung tech support and determine whether RMA proceedings are in order or whether they can shed some light on this problem.

(I'm reasonably certain at one point during this issue arising you've uninstalled the M.2 SSD from its ASRock's motherboard's PCIe connector and then reinstalled it, yes? If you haven't done so, give it a try.
What we would also do in situations like this is install the SSD in another motherboard that had the capability of accommodating this M.2 SSD as another troubleshooting step. We have onsite a number ASRock motherboards (Z170 & X370) that we would use for that purpose but obviously I assume that kind of troubleshooting step isn't available to you.)

In any event please keep us informed how & when this issue has been resolved.
 

admiral.weppas

Prominent
Oct 21, 2017
11
0
510

Switched M.2 slots. didn't help. ordered a PCI adapter for M.2s just to see if it'll make any difference

 
It occurs to me that your ASRock Z370 Extreme4 is a new MB with the latest BIOS being v1.10 (non-Beta) dtd. 10/16/17. See https://www.asrock.com/MB/Intel/Z370%20Extreme4/index.asp#BIOS

You've installed that BIOS?

Also, this might be a MB issue as well. Probably would be desirable to contact ASRock's tech support and see what they have to say about this issue. We've generally found their tech support reasonably responsive. See https://event.asrock.com/tsd.asp for the support request form.

This might come down to a RMA issue re the motherboard.

 

admiral.weppas

Prominent
Oct 21, 2017
11
0
510

Yes, have the newest Bios. Wrote them already. Hope they'll be able to help
I also found out on the QVL for storage that the motherboard supports the 250gb version of the m.2. The 500gb ist not listed. Maybe that might be the problem.

 
That shouldn't be the problem; if it is that's a miserable way to market this type of MB. We generally find these QVLs are woefully out-of-date and all too frequently provide misinformation of one kind or another. And this applies to virtually every motherboard manufacturer we've dealt with, not just ASRock.
 

admiral.weppas

Prominent
Oct 21, 2017
11
0
510

I've watched/read a lot of guides on how to install a M.2
They all have one thing in common; "set secure boot option to 'other OS'"
I don't have that option. maybe that might the problem?

Here are my secure boot options:
https://imgur.com/IlNNbY1
https://imgur.com/iYoKPB1
 
Frankly we've never set that BIOS setting to Enable and always leave that setting to its default "Disabled" when the motherboard's BIOS contains that setting. I can't ever recall running into any problem involving the Secure Boot setting when installing a M.2 SSD (or any other type drive) with any OS. On the other hand I can't recall coming across that "Custom" setting. Is there no explanation in ASRock's User Guide?

Also I can't recall ever coming across that "Factory Key Provision" setting. (Remember I haven't as yet worked with the Z370 motherboards, so I'm not familiar with any special BIOS settings for that type of MB.) Again, any detailed explanation in the User Guide? (I'm aware ASRock's User Guides are generally pitiful in providing detailed understandable commentary on their motherboard's BIOS/UEFI settings).
 

admiral.weppas

Prominent
Oct 21, 2017
11
0
510

No. Manuel is useless ragarding that.
 
I suppose you could just change the default settings to determine if it will help. If it doesn't (which I suspect), it should be simple enough to access the BIOS again and change them back to the default settings.

Have you communicated yet with Samsung re this issue?
 

admiral.weppas

Prominent
Oct 21, 2017
11
0
510

Tried every setting. Disabled and enabled.
Haven't reached out to Samsung yet. I contacted AsRock tho, as I'm sure they'll be more of a help.
Won't hurt to contact Samsung tho.

 
I do hope you get some substantive assistance from ASRock. Based on our experience it's something of a crapshoot. Sometimes you're lucky enough to reach a competent technician who provides a sensible solution to the problem. Other times...

As for Samsung, you definitely should contact that source. Hopefully they'll be responsive.
 
Solution