ASRock Extreme4 x99 and m.2 first time installation and UEFI/BIOS setup Trouble

[arda21]

Just finished building with ASRock Extreme4 x99 motherboard, Just connected m.2 module to install OS first and an optical drive to boot from first, I went to Boot Options by pressing F2 on startup (startup boots up so quick usually I don't have time to read any of the other options so I just keep pressing F2) in 'BOOT' menu at UEFI (Attaching Photos)

*Please note that I actually physically connected Optical BluRay/DVD Drive on S_SATA3_1 (so I don't know why it is taking 2 First Boot Options with same names; it says S_SATA3_1 and then next one is Listed UEFI;HL-DT-ST I think that's also BluRay Drive?) and then Boot Option #3 it does show "N1-Samsung SSD.."T

Yes I was able to boot from Optical Drive with Win 7 Pro CD, So I thought it will let me choose m.2 drive to create partition and have WIN 7 installed there before I activate after first installation to upgrade to Win 10,

However as you can see in the last Photo Windows DON'T see any physical drives to install itself?

This is my very first time dealing with m.2 module ssd I read that it is better to just have module in there first to install OS and then add other SSD drives for additional drives so that's how I started since I want m.2 to have OS/Programs going forward,
Any input will be appreciated,
Thanks!

 

[arda21]

So Combination of different guides yet without fully understanding made me bypass that error;
First CRM selection mentioned on METHOD I of the link here I believe is important. http://forum.asrock.com/forum_posts.asp?TID=1236&title=how-to-install-windows-on-a-pcie-ssd

I had to find NVMe driver during the installation, but even I did all that correctly, I would end up with the above error after installation, then I started to just try randoms things I took notes as much as I could each boot and trial.

I Took a note of where my optical drive connected to, if it is on S_SATA or SATA, then I found out it was on one of the of the S_SATA, so I disabled all SATA selections (even though I had no other connections to any other drives)

Also installed new version of ASRock EXTREME4 x99 bios version to 2.30
Also instead of running UEFI from boot menu I actually tried S_SATA one
I tried different combinations Secure Boot enabled disabled, I can't remember at exactly which setting that error didn't showed up, I physically was in front of this computer for 6 hours straight yesterday.

so windows 7 finished installed it, even though each trial, I deleted all the partitions it created, it always creates all these partitions, after win 7 was able to reboot I made sure there are no usb sticks that contains any drivers or bios flashes hanging out connected, all i kept was mouse and keyboard connected when things reboot.

after i get myself at win7 i activated my key, but i didnt install anything, I just took note of huge file space already used even with anything else installed

At this stage, I just wanted to get to Win10 since I activated, however I was worried that since win10 would have to install and boot from a usb I had, I got worried that I would have to figure out a different setting at UEFI Bios thingy. long story short I just right back into it, and windows 10 installed a little more easier compared to win7 I remember it didn't recognize what was already on m.2 ssd but I just went ahead without trying to delete anything, but then my already activated win7 key didn't work at Win 10!

I called microsoft explained them that there is no way I want to get back to win 7 again and do couple of updates, they kept saying that something i did when i did a full clean install, the activation didn't register on their end, the system shows up like it is trying to install the same key to another computer! I really didn't care for any glitch as I was fuming at this stage, I paid $40 extra and upgraded to separate Key for Win 10 which activated when I was on the phone with them.

Now I still realize 46gb amount of space taken in m.2 drive, win 10 Pro should only be around 26gb Max I believe, so I am trying to figure out now if anything thru the installation process ate some of the m.2 hard drive space, I remember deleting always all the partitions I saw each trial and error, so when installation went thru I thought there wont be anything lagging behind.

I have win 10 running now, but all those sata or bios changes I made is still there, this morning I couldn't even go to UEFI bios after seeing it 55 times yesterday over 10 hour period. but I am gonna get back up in front of it, and see if I need to fix anything before starting to install my drivers of the system I just built.

Thank you for your time helping me yesterday Jimmy

 

[jimmysmitty]

Your system probably boots too fast to get into the BIOS. That SSD is pretty damn fast.

You should be fine to install drivers, the BIOS changes you made should not affect them.

Sorry you have had such trouble.

As for the size, is there a Windows.old folder in the root of your C drive? If so follow this to remove it:

http://www.howtogeek.com/223821/what-is-the-windows.old-folder-and-how-do-you-delete-it/

 

[arda21]

Hey, I figured what it is taking so much space! it was a hidden file called.. "Hiberfil.sys" on C: it is 27 gb in size???? pagefile.sys is about 10gb but thats normal for a 64gb actual ram size but hiberfil is ridiculous...

 

[arda21]

I tried turning off hibernation on power options and disabling Fast Boot but no changes yet, I thought that may get rid off that file in size.

 

[arda21]

I went ahead to reg edit and killed the hibernate that way it is gone!

 

[jimmysmitty]

I use a Command Prompt and type in powercfg -off. That kills the Hibernation and deletes the file too.

 

[arda21]

Thanks Jimmy I learnt so much from you in a short period of time! I really appreciate it mate!