@Luke&Zya
Around the same place you turned off the ROG screen in the Bios, you may have another setting that enable or disable the modules rom posts like you are trying to see. Maybe it is not enabled. May worth a look.
The setting is called "Option ROM messages" and it must be set to "Force Bios" to be sure that they are posted.
I dont see anything that would turn on the module rom post, only post report for how long it remains on the screen, I changed it to 10 seconds but it just stays on that American Megatrends screen for 10 seconds.
Different question, do I need to use Rufus? I found a video explaining how to change to GPT using command prompt, I did it, it said successfully converted to GPT and my usb stick disappeared from my computer so I went into disk management and found it there and formatted to NTSF. Does that sound correct?
It should be correct.
Yeah sorry I didnt see your response (I was going to edit my comment lol) I just checked it using diskpart and it says that its GPT. I was just afraid that formatting might’ve reverted it back and nothing in there tells you which format it is but it looks like it’s good to go 
I’m assuming that changing the 970EVO to GPT is done during the windows 10 installation? (Or right before it installs to be exact)
Thanks
@Luke&Zya
I know it will be formated automatically in NTFS by Windows when you install it. But, if i remember right, i think it must already be in GPT.
Sorry my thought process was a little off on that one lol. So what you are saying is the SSD has to be in GPT before you start, so I would plug it into my computer and do the same process that I did with getting the usb stick to GPT. I’m assuming the SSD will show up on my computer after its installed which will allow me to change it to GPT. Basically, everything that needs to be changed in the bios doesnt need to be changed for my computer to recognize the NVMe M.2, only to make it bootable. Correct? For some reason I was thinking that it wouldn’t show up on my computer which is what had me confused as to how I was going to change it to GPT.
@Luke&Zya
Correct with one comment: As long as you have a NVMe driver compatible with your drive, it will show up in Windows. Windows 10 will probably try to install one when it will detect it.
I got the 970Evo today and followed Stickmodes instructions on the first page but I’m getting a warning. The current BIOS setting do not fully support the boot device. Do you have any idea what I did wrong?
Do you think its because I’m not using an ISO for windows 10?
@Luke&Zya
It could be… In this case, it is hard to know because i don’t know what you did exactly. Did you install Windows then try to boot from it after it is installed? Or is it the Windows on the USB that don’t want to start? If it is the second as i suspect, then it could be either that your USB is not in GPT or was not installed on the USB with Rufus in GPT only and it tried to start in Legacy mode but couldn’t because the Bios is currently in UEFI only . Or either it could be that the Bios update didn’t worked and the NVMe module is not in your Bios yet. Honestly, it is hard to say what the problem is at this point without more details or more tests to try. I suggest you first make sure your USB is set correctly then if it continue to fail, it will be time to consider that the Bios update may have failed and need to be done again.
And don’t forget to start your Windows USB by hitting F8 at boot and chosing your UEFI:USB-key-name (“UEFI:” MUST be before it) or it will try to start and install in Legacy.
Hope this will help to point you in the right direction.
Sorry I should’ve been more specific but yea I’m trying to get win10 to start installing from the USB stick. I forgot about hitting F8 and I also downloaded the win10 ISO but neither worked. When I hit F8 I get a new window before the warning. (Pic below)
When I checked using Diskpart it said my USB stick was in GPT, do I need to use Rufus first and if that doesn’t work then try to flash the bios again?
(Edit) Is your mod required to run the win10 usb stick in GPT? Or is it only for making an NVMe bootable? If its required for the win10 USB stick then I would think that it might not have flashed, especially since I cant seem to get those modules to pop up like you said they should.
@Luke&Zya
No, it is only required to boot in NVMe.
I just downloaded Rufus and it looks like its saying that the drive is in GPT. Guess I’ll try to flash the bios again. I was hoping that I was past the scary part. lol
Does it matter that the USB stick that I’m using for the bios flash is a 32gb stick?
@Luke&Zya
It’s not supposed to matter.
So I just flashed it again this time using an old 64mb stick that I’m not sure where I even got it from lol. It flashed for several minutes this time which had me worried that I f’ed up big time but it finally stopped blinking and now I am getting the ROG screen popping up twice but nothing that looks like a uefi module, then I entered and changed settings in the bios and clicked on my win10 data stick in boot override and then hit F8 and it still went to that same warning window that I got the first time.
@Luke&Zya
I am confused as to why your Windows 10 install won’t start with your USB key in UEFI. I think you should make some tests to find out where the problem comes from. You can try using Rufus in NTFS/GPT and if it fails, try FAT32/GPT. I don’t see why it would not start the install with one of those in UEFI as long as you chose UEFI:xxxxxx with F8 at startup.
Ok I’ll try that. I tried changing just the boot control to UEFI/Legacy just to see what would happen and it pops up saying missing operating system. I dont know if that mean anything, probably not. But I’ll try what you suggested
(Also I’m not getting any options to select after hitting F8)
So last night I got rufus started on that usb stick and I just tried it and now it shows up UEFI in the boot override (it may be possible that I didnt scroll down far enough to see it at the bottom but I thought I did or it was thanks to using Rufus) but now I’m getting a new message. (Pic below)
That was NTSF GTP using Rufus, later this evening I’ll try Fat32, unless you know what’s going on here? Lol
@Luke&Zya
That is weird. Seeing this, i am starting to think that your Bios flash worked but there maybe be a mismatch/mess in the internal settings that comes from the old version. That usually creates some random weird effects and this looks like it can be it. It is rather easy to correct that when it happens. Here is what you should do to get rid of that or at least be sure that it don’t comes from that:
- Redownload the v10 bios to be sure it was not corrupted during download and verify the checksum of the Bios with the hashlist to be sure your Bios is perfect.
- Reflash the latest Bios a (hopefully) last time.
- Clear CMOS and reboot. This will erase most if not all of the old settings that could be interfering.
- When it reboot, enter the Bios and load the defaults settings, save and reboot. By saving the defaults settings, you ensure something is written over any remnants that could be still there.
- After reboot, now enter the Bios again and enter your normal/usual settings, save and reboot.
After that, you can be sure there are no remnants of any old Bios version. Note that if it is your problem, it can happen with any Bios flashing on any motherboard and you would not be the first to whom it happens, the last one i saw with that bad luck can be found in the discussion in the posts #237, 238 and 239. Note that for him, the effect of the mismatch between versions were completely different. Like i said, it is usually random depending on what the mismatch affects.
I GOT IT!! Lol. I watched a 30 second YouTube video about that error I was getting (same error different issue he was having). In Stickmodes instructions (you might’ve mentioned it also, I cant remember) he says that secure boot has to be in windows uefi but I changed it to other OS, after that everything seemed to work perfectly (other than I already miss windows 7! Lol) Hopefully you didnt tell me to change it to that, my memory is horrible, I just know that the instructions on the first page says windows UEFI. Now if the option I used (OS) is not the option I’m supposed use, is there a reason or negative effect from using that?
I’m going to try and run some speed test in a few, gotta learn how to use Windows 10 first lol 