Author: Gambit
Subject: SM951 as OS boot device information
Posted: 09 Feb 2017 at 6:42am
Hi Parsec,
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Edited by Gambit - 1 hour 4 minutes ago at 6:42am
Subject: SM951 as OS boot device information
Posted: 09 Feb 2017 at 6:42am
Hi Parsec,
thanks again for your patience.
NOTE: Sorry about some of the screenshots these were taken on my Cintiq Monitor, which connects to my graphics card (and the first port is the only one that will fit this) with a DVI-I connection (which is hardwired into the LCD Tablet) and for some reason displays red. Not sure if this is a connection or BIOS thing as I am pretty sure when I originally setup my PC it was black. This does not affect the monitor when windows is running.
Ok, So after several attempts to install Windows on my SSD again last night and reading your post several times I seem to be further back that I previously was, as now I cannot get Windows to create a Boot Manager record in the BIOS. It just keeps booting back into the USB and attempt to start the install process all over again.
First I will address some of the things I tried including a tip in your post I thought may work, but alas it did not. :( I will then add below some screeenshots of my bios and the install process so that it can more easily illustrate the settings I have and you may see something I have overlooked.
I noticed in your post that you mention the USB should be in the IO panel, I was not doing this I had it plugged into the front on my PC. So I plugged it into one of the USB 2.0 ports in the back, unfortunately this did not change anything.
The other thing I tried was manually clicking on the NEW button when setting up the SSD to install windows. I normally just clicked NEXT on the Unallocated Drive and let windows take care of this. Either way windows seems to create the exact same number of Partitions as shown below.

Figure 1. Whether I manually click NEW to setup partitions or just Click NEXT windows creates the same partition setup.
I created a NEW Rufus UEFI Boot USB (The NTFS format was a default Rufus changed when I added the ISO, I fixed this and there was no change), once after manually formatting the usb as FAT32 and a second time via Rusfus again ensuring the format is FAT32 with GPT UEFI setup as per screenshot.

Figure 2. Rufus UEFI Boot USB setup.
NOTE: I do leave the USB drive in the entire time, but as I said it seems to just keep loading the start of the Windows Install again not actually the continuation of the Windows installation process.
To eliminate anything I can think of I removed my graphics card, so the only Inputs to the PC were my second monitor running via DVI-D into the motherboard, Ethernet cable, Keyboard and Mouse connected in the top two USB connections and the USB Boot drive in one of my Grey USB 2.0 ports and of course the PCIE Adaptor and Samsung 960 EVO M.2 SSD.
Once again this did not seem to change a thing. I am starting to wish for the days when I could get the winload.efi screen and create a Windows Bott Manager in the BIOS, I am at a lost to what may be preventing this from creating a bootable Windows Installation...
I did noticed something interesting, but it might be nothing... when in the BIOS the first boot drive is UEFI: USB X, however if I press F11 for boot options when booting UEFI: USB X is the second option and USB: USB X is the first. Is there a way to tell when you have booted into the windows installer maybe via command prompt where it has successfully booted in UEFI Mode? I am wondering if it is doing this correctly, even though the windows installer seems to create the correct partitions for install.

Figure 3. When F11 Boot Options selected it shows USB selection first even though BIOS has UEFI. Not sure if is an issue.
I will attach a copy of my BIOS screens for you to confirm my settings. These are the same settings I have had the entire time, with the exception of trying it with CMS disabled which would not boot at all as my graphics card is not a GOP card.

Figure 4. System Browser shows my adaptor and Samsung 960 EVO M.2 SSD registered as Mass Storage Controller.

Figure 5. Shows the Storage Configuration settings. I have no other drives connected.

Figure 6. Shows the CSM settings which are enabled and the Launch Storage OpROM policy is set to UEFI

Figure 7. Shows my first Boot Option is set to UEFI.

Figure 8. Shows that the Installation seems to have gone OK. However on reboot it boots straight back into the Installation process to start again...
I wish there was something obvious I was missing, my components are perfectly fine and would like to push any MB/CPU upgrade off until next year when the next generation of boards and CPUs come out it I can. So any further insight is much appreciated.
G.
Edited by Gambit - 1 hour 4 minutes ago at 6:42am