Where (at which disk) did the Setup create the necessary partitions?
The "Compatibility Support Module" (CSM) should be enabled unless your system is able to boot in "clean" UEFI mode (usually there are some required EFI modules missing on systems with an older Intel chipset system or with a discrete graphics card).
According to Samsung’s "White paper" for their 950 Pro SSDs (look >here< ) there is an Option ROM module within the SSD, which may allow booting off the Samsung 950 Pro SSD in LEGACY mode for some systems, but I doubt, that this will work with all systems. The much better and safer option is to boot the SSD in UEFI mode using the GUIMode Partition Table (GPT), but this requires the presence of an appropriate NVMe EFI module within the in-use mainboard BIOS.
They were all there on the 512GB Samsung Pro.
You can check it by inserting the related USB Flash Drive into any Windows system and running the Disk Management.
You can "repair" the boot sector by booting off the media containing the original OS image and choosing "Repair" instead of "Install".
Checking in disk managment it’s just a single 8GB FAT32 partition. Properties on the drive say GUID Partition Table (GPT), basic type.
The Win10 Setup always creates a separate small sized and usually hidden partition containing the boot sector. The only question is, where (on which disk) it is situated.
zazzn
July 18, 2016, 9:56pm
766
Actually it’s a p3500 which is the same as the 750NVME drive just re-bran with a different enterprise firmware.
No, I don’t know such hack.
I would try different bios versions until you find the one that might by chance work for you. Your going to have to roll up your sleeves if your going to get this working. I would leave the Sata efi driver in your rom and remove something else like a FireWire module or network boot module you’d probably never use. Check out the Ozmosis tutorials on how they make room in their roms for a whole lot more than one file. Also do your testing with a minimal barebones configuration pulling out sound cards and whatever else might be eating lanes and listen to Fernando about using the igpu if possible. Then work up from there.
Hi, I bought recently a Sm951 nvme for my G751jy but it is not recognised by the bios. What should I do to make it work?
@Linux86 :
What makes you so sure, that it is not recognized? The SSD will not be listed within the "Advanced" section of the BIOS, but may be bootable nevertheless.
If the SSD is not bootable, you should insert the required NVMe EFI module into the BIOS of the mainboard according to the start post of this thread and install the OS in UEFI mode.
winyl:
I just found out it is not nesseary to modify G751JY bios to let the bios see Samsung NVME 950PRO. I modified the bios succcessfuly, added the NvmeExpressDxE to bios, had to delete Mtftp6D module to do so. Bios flashed with afuwinx64 and worked.
I have read that winyl had a lot of problems with bios modding and I don’t know if it’s possible to modify g751jy bios without breaking anything.
It may be a good idea to send him a PM.
I did it, thanks for the advice
I followed the procedures described in the first post and in the winyl’s post (I deleted Mtftpd6d, added NvmeExpressDxE and flashed with afuwinx64) and it worked!
@Linux86 :
four partitions that the Win10 installer made, not 3 like on the 512:
zazzn
July 23, 2016, 1:59pm
777
Hi Fernado,
EDIT by Fernando: To save space, I have inserted the MMTool details into a "spoiler" and removed unneeded parts of the fully quoted text and blank lines.
@daynomate :
Not really.
The shown partitions of Disk 1 (your 512 GB Samsung NVMe SSD) look fine and don’t indicate any reason why you were not able to reboot after the first part of the OS installation.
This partition is not essential. The Disk Management of my Win10 system doesn’t show this partition either.@zazzn :
zazzn:
I want to give this a shot anyways, it seems there is one user that had a P8p67 on the forums that was able to get it to work with the Samsung drive and a PCI-E adapter. I don’t see why my p3500 can’t be detected.
Good luck!
zazzn
July 23, 2016, 3:43pm
779
@Fernando Looks like it still doesn’t detect. The very strange thing is if I force to UEFI, the machine will hang at the splash screen, until I clear the CMOS. then it will work and be forced to legacy.
What do you mean? The BIOS and Windows obviously both have detected the NVMe SSD.
What do you mean with "force to UEFI"? You should not try to disable the CSM completely, because your mainboard BIOS doesn’t contain working EFI modules for all important devices (Intel Graphics, LAN etc.).
The CPU Microcode has nothing to do with your boot problem.
You can replace the recetly inserted NVMe module by another one taken from a newer ASUS mainboard and look, what happens, but I am rather unsure, whether this procedure will solve your current problem.
