1)Ok, so as the first topic of discussion i start with the following.
So i got me an 512GB Samsung SM951 M.2 2280 PCIe 3.0 x4 the AHCI version, and install it, and wanted to set it up as windows 10 boot drive.
I set up in bios cd rom as first boot (where the windows cd is), and the SSD as the second one.
When i reach inside the windows installer the part where one can choose the install drive, it tells me it cannot install windows on it since the pc might not be able to boot from the drive.
Thats one of the reason i uploaded the block diagram, was thinking that maybe those pci express 3.0 4x lanes that the drive is using might be used by something else, but it doesnt seem so.
I also got all the 8 Sata ports occupied, 2 with HDD, 2 with optical drives, and the rest with racks that are empty.
I need to check the manual to see if i find something that can make this work, and i will play with settings in bios, hopefully i can crack it.2)Second topic of discussions is regarding UEFI bootup.
According to User Venturi
, he has managed here to setup Uefi, with the following settings:
Links is here
in his original Post:
I figured i could do the same thing. I installed the Samsung SSD onto the m.2 slot, and the Fury X in the 5th PCI slot, got in bios, enabled UEFI, according to picture. disconnected everything except optical drive, mouse, and keyboard, and tried to boot to see if i can install windows 10 from on original disk.
I got no image on my Samsung U32E850R Monitor
, to fix it i ended up needing to reset the bios.
I had some trouble here also, at first i tried with the jumper method, the pc got itself after startup in a loop which goes through posting, and reseting, then tried to remove the battery, with the same result.
To make it work, i had to replace the Fury X with the previously owned 750ti, which was no easy feat, as i had to leave the Fury X in the case suspended, while the 750ti was plugged in the motherboard socket.
Finally it worked.
I reset the bios, and left everything on Legacy mode, and tried to install Windows 10 like that, at which point i got into the Problem described at number 1.