Windows 10 boot disc problems (Z390 Aorus Master)

[jesse.tiemissen]

Firstly, I'd like to apologise if this isn't the appropriate board for this question. Okay, here we go.

I'm having a lot of trouble booting to my Win10 installation disc. I just got all the parts in today and when I had everything put together I went to install Windows 10 but the status circle just freezes and nothing happens.

I've tried disabling CSM boot options, resetting the BIOS, but I can't figure it out. The install disk I'm using is the same one I used a month ago to install it on my older computer.

I looked around and saw a few people have had this problem (with gigabyte boards)
(See here: http://forum.gigabyte.us/thread/4341/trying-install-hanging-loading-screen) but I can't find any solutions so hopefully someone can help me.

Thanks for your time

UPDATE** 9 JAN 2019

I received the replacement motherboard today, got everything put together, and I was having the same problem. Either Newegg sent me back the same broken(?) motherboard (unlikely, it had original packaging), or the problem lies elsewhere.

I'm RMAing the CPU and RAM, even though they both tested fine when I ran MemTest86 on them a couple weeks ago.

I can't for the life of me figure out what the problem is and it's become a rather daunting problem. I have a lot of money sunk into this system and nothing I've tried so far has got it up and running.

Also, could this have anything to do with the fact that I'm trying to install Windows 10 on an NVMe drive? I found a few posts saying to disable secure boot settings, disable CSM, and a few other things, all of which I tried with no success. I doubt this is related to the drive I'm trying to install this on though because I get the same problem when I try to install it to a SATA SSD that I'm able to install win10 on and boot into with no problem on a different system.

I hope someone comes across this that can shed some light.

Thank you,

J.

UPDATE** 16 JAN 2019

Just updating the thread to close it out for anyone that comes across this in the future. The issue was related to either a faulty CPU or RAM kit. I received the replacement parts yesterday, installed them, and I booted into my Win10 USB drive without issue. From what I've gathered elsewhere; MemTest86 requires several passes to root out any problems with faulty hardware and the number of passes I ran may have been inadequate to reveal which component was faulty. I sent off both of those components before I could test each of them individually, so sadly I can't say exactly which one it was that was causing the issue.

A friend of mine told me he believed it was the RAM, but I can't accurately say for sure.

 

[lutin7812]

Hi, I had a similar issue trying installing Win 10 on same components (1tb nvme card). It took nearly 15 minutes just to get to the installation language selection.
I was booting from a usb key on my usb 3.0 port.
When I plugged on a legacy usb 2.0 it works smoothly. Reason is that usb 3.0 is not handle by the win 10 installation dvd. As long as you havn't install the correct mobo driver those usb 3.0 won't work properly.
Furthermore, it's a good idea when installing Windows to just have only on drive connected, this avoid conflict if upgrading from older windows already installed.
Hope this can help someone.

 

[manhunt234]

I had exactly the same issue with my new build. Tried using Rufus to create a bootable Windows 10 image (MBR and GPT). Also tried using the official Microsoft Media Creation tool to make a bootable USB (USB 2.0 and 3.0). In addition, tried creating a bootable DVD using the media creation tool. I even tried creating a bootable Ubuntu USB disk - same issue.

The Windows / motherboard status circle would just freeze and my CPU fan (Noctua NH-D15) would start spinning quite fast. The Num lock and Caps lock LEDs on the keyboard would not work either and the entire PC would lock up.

I tried running the PC with only one RAM stick inserted into one slot in the motherboard at a time. I ran memtest86 for 6 hours (4 iterations), no errors could be identified in the RAM.

Was going to RMA the CPU / RAM / Motherboard, but tried updating the BIOS (should have tried that in the first place!) to the latest version and that fixed the issue! I updated it from version F8 to version F9.

Here is my setup:

Gigabyte Z390 Aorus Pro (rev. 1.0)
i7 9700K (stock)
Corsair Vengeance LPX 32GB (3200Mhz)
Corsair RM750x (750W)
EVGA RTX 2070 8GB Black Edition

I hope this might help someone.

 

[wolfecho]

I had the same issue with ym aorus master, intel 9900k and corsair vengence ram. My chassis doesnt have space for a dvd drive and i hardly use dvds anymore, so teied installing from a flashdrive using the media creation tool......

I battled for 2 hours and read posts like these online, nothing helped, until i got one crazy idea...

I have 2 drives, a samsung 500g nve and a western digital 4tb sata. Im trying to install win 10 on the nve, since bootdisk and loadtike speeds of a nve for gaming is great. I get to the usb boot menu, select the 500g nve and create a partition and run the install but every time it seems that files do not work on the nve since after the install the pc reboots and goes direcrly to the usb drive to install again... i did check boot manager and tested every drive. The os was not installing and logically there should be nothing blocking it.

After trying over and over confident that the new gear i got tedaybid not faulty, i decice that instead of starting the installation with my win 10 product key ill say instead i dont have a key - ibwas then presented with a menu to select my version of win 10.

I have a pro key, so naturally i select pro and this time while creating the partition i noted that instead of just a system drive being created as an extra, there were 2 other system drives created during the install process... this time it worked, i pulled out the usb after the install and it booted into win 10 from my nve.

So the problem is the poopy design of the media creation tool. I was installing the latest version at the time btw 1903. Hopefully this helps anyone else who has the same issue

 

[BOB_013]

I had this exact issue and I can confirm that updating the BIOS fixed it straight away.