Cant's install windows 10 from USB on Gigabyte z170x-Gaming 7 motherboard

Toggle sidebar Toggle sidebar
G

Grimfyre

Distinguished
Feb 21, 2014
92
0
18,630
I recentlybought a new motherboard... the z170x-Gaming 7 from gigabyte...

However both SSD and HDD have had windows 10 attempted to install on and a "corrupted" version of windows.

So i put windows 10 on a usb drive and am attempting to install from usb in order to format the drives... however the pc gets stuck on the Gigabyte logo screen if I try to boot from the UEFI partition 1 of the usb.... and if i load from the boot device that just says USB (no uefi) it will get to the windows logo and then freeze. No loading loop or anything.

Any advice?
 
Sort by date Sort by votes
G

Grimfyre

Distinguished
Feb 21, 2014
92
0
18,630
So i found out a couple of issues.... My RAM were not in the correct dual channel slots (that fixed why my bios only read one ram stick)

Also the bios did not originally detect my hard drives...i plugged their sata cables into other slots and now it detects them...

However I am having thesame issue where the installation from the usb just gets stuck on windows logo with no indication of loading or anything..
 
Upvote 0 Downvote
G

Grimfyre

Distinguished
Feb 21, 2014
92
0
18,630



So right now on the bios tab of the bios it says ...

Windows 8/10 features : Windows 8/10
CSM Support : Enabled
LAN PXE Boot Option ROM : Disabled
Storage Boot Option Control : Legacy
Other PCI devices : UEFI
 
Upvote 0 Downvote
G

Grimfyre

Distinguished
Feb 21, 2014
92
0
18,630


It works on my laptop with the same usb drive...so i'm not sure that would help.

I am however reinstalling the windows file onto this usb to see if that does anything.

 
Upvote 0 Downvote
captaincharisma

captaincharisma

Glorious
Oct 13, 2004
10,963
76
45,290


just because it work on one computer doesn't mean it will work on another

 
Upvote 0 Downvote
G

Grimfyre

Distinguished
Feb 21, 2014
92
0
18,630



hmm not sure how it could work in other pcs but not one.... how would changing the usb do anything different?

I am trying to reinstall on the current usb...if that doesn't work then I will go out and buy another usb to try that method i guess.
 
Upvote 0 Downvote
G

Grimfyre

Distinguished
Feb 21, 2014
92
0
18,630
So far nothing has worked. i got advised by one guy to remove one of the hard drives and just keep the SSD and still it freezes on the windows logo... does anyone know what could be wrong??
 
Upvote 0 Downvote
L

LinuxDevice

Distinguished
May 20, 2017
756
109
19,540


Can you attach the SSD (or whichever your primary install is to) to another PC and format it (any option to make bootable would be useful)? Then see if you can install on the other machine. The goal is to remove old partitions and start clean. Hopefully the other computer will also be UEFI and not legacy.
 
Upvote 0 Downvote
G

Grimfyre

Distinguished
Feb 21, 2014
92
0
18,630



So I actually just did that, however after a format (full not quick) There is still a "Windows Boot Manager" boot option from the hard drive which makes no sense to me.

I also just put in a physical disk drive and put in a copy of windows 10...it is acting exactly the same.

If i choose the 0P: ATAPI iHAS124 B it just freezes on windows logo
If i choose the UEFI: ATAPI iHAS124 B it freezes on the gigabyte logo
 
Upvote 0 Downvote
M

mtoddvan

Prominent
Jul 22, 2017
36
0
560
Here is what I would do.
1. change the bios from legacy to UEFI
2. CSM enabled
3. Windows 8/10 Features enabled it is defaulted to Other OS (why I do not know.
4. Try & install windows 10 64
5. If you still can not install mirrior files from usb to Hdd can use a pre os program.
https://www.partitionwizard.com/?pw
Is what I use.
6.Enter Bios set Hdd to boot first
7. Then try to install from hdd to SSD.
8. If that does not work hit me back.
 
Upvote 0 Downvote
G

Grimfyre

Distinguished
Feb 21, 2014
92
0
18,630


You lost me after #4...

I do not have a spare HardDrive to do this from... All my hard drives or SSD have the "windows boot manager" thing on them from when i was originally trying to reinstall windows on my old motherboard...

Formatting the drive doesn't seem to get rid of it all of a sudden so idk what's going on.

 
Upvote 0 Downvote
M

mtoddvan

Prominent
Jul 22, 2017
36
0
560


Got you, yeah had to go back & reread your original post I missed the part about having boot on your drives already.
Try the other steps 1-4 & see if you can get it to install.

 
Upvote 0 Downvote
G

Grimfyre

Distinguished
Feb 21, 2014
92
0
18,630


Yeah I tride that and get the same thing... if I try using UEFI it just freezes on the gigabyte logo and doesn't even make it past the AD code.
 
Upvote 0 Downvote
M

mtoddvan

Prominent
Jul 22, 2017
36
0
560


Hmm I use the exact same board.. let me think I'll get back to you in few. Do you have access to burn to cd?
 
Upvote 0 Downvote
G

Grimfyre

Distinguished
Feb 21, 2014
92
0
18,630


Yeah i've burned windows 10.

So here is what i've done since the last time I replied on here...

I removed my laptop hard drive and tried it on the pc....didn't work at all.

I put my SSD into the laptop to attempt and format/reinstall windows...

The laptop reinstalled windows so it wasn't the SSD.

I've got just the motherboard, cpu, psu, 1 stick of ram and 1 hard drive hooked up and it still just keeps freezing...

I hate to think this motherboard was DOA but i'm starting to think it is...

I cant think of any other bios settings that I would need to set.
 
Upvote 0 Downvote
L

LinuxDevice

Distinguished
May 20, 2017
756
109
19,540
I see this:
Storage Boot Option Control : Legacy

Just as a test, put boot option to anything bug legacy...then see if the drive is detected. Then try putting other UEFI modes in legacy as a test. I don't expect the system to necessarily boot, it's just a test to see if those changes allow detection when previously there was none.
 
Upvote 0 Downvote
G

Grimfyre

Distinguished
Feb 21, 2014
92
0
18,630


What do you mean "when previously there was none"? My pc detects the drives perfectly fine...

So here are a few updates.... I ordered new RAM (since my ram Serial Numbers were not on the compatibility list) That did not change anything except give me cooler looking RAM.

I just tore the entire system apart and rebuilt it. That did not change anything.

At this point I can only think that one of the following is faulty...

Power Supply
Motherboard
CPU

I checkd the CPU when i tore the system down to make sure no Thermal paste got onto the board or god forbid under the CPU... Didn't see anything like that... All i saw was the thermal paste on the cpu... although there was a wierd looking black rubberish looking strip around the cpu on the Green portion of the cpu... I tried wiping it away thinking it was thermal paste but it wont come off so idk what it is... I'd hate to think something is actually wrong with the CPU.

At this point I only see 2 options... Bring the PC to a tech and pay around $90 for them to try and figure out whats wrong and either fix it or tell me what i need to do.... Or return this new motherboard for a replacement to see if it was a DoA motherboard.

I am going crazy having to use a laptop right now -_-

Just to remind anyone reading this....

This is the issue...

When booting windows 10 from either a USB or Disk, It freezes on the windows logo and doesn't go any further (no loading circle or anything)

If i remove the disk or usb at the start of the logo appearing then i will get the error message saying it was interupted... But if i leave it for 5+ minutes it will lock up and freeze.

I have stripped the entire system down to 1 stick of ram, the SSD, motherboard, cpu, and power supply and nothing has worked yet to fix the issue. It is a BRAND NEW motherboard and Brand New Ram, but everything else was from a previous build and is 6 Months old.

Thanks for all of your time and help on this matter.
 
Upvote 0 Downvote
L

LinuxDevice

Distinguished
May 20, 2017
756
109
19,540
Elaborate more on the windows 10 install disk...what was the source when you put it on the USB drive? A DVD to a USB DVD reader? And what was the signs and symptoms of leading up to being "corrupted"?

FYI, when in legacy BIOS mode the motherboard provides more driver services for basic devices, e.g., a USB keyboard or mouse would not work without a driver in the motherboard itself. BIOS legacy ties old partition styles and size limits to whether or not the motherboard BIOS supports those styles/limits. Understanding those partitions is part of the BIOS and is essentially a disk controller driver and file system driver.

There was a goal in migrating to UEFI that the operating system be able to more flexibly handle things which had previously been tied to the BIOS (such as large disks), including many basic drivers used at boot time prior to reaching the operating system. This information had to be stored somewhere though, and goes to a UEFI partition on the hard drive. So how far the system gets before it fails may be an indicator of the stage in boot which was reached at the time it locks...more specifically, BIOS will only lock once it is waiting for a bootable drive to load and execute fails. UEFI may fail slightly earlier when it is reading that UEFI partition...or it may appear to lock at the point when it begins loading the operating system's image (the actual install partition)...in which case it probably succeeded in reading the UEFI partition and is now waiting for an executable boot partition.

It is my feeling that motherboards capable of both BIOS legacy mode and UEFI cannot handle both at the same time. It really isn't possible to correctly partition a single disk with both BIOS and UEFI partitions. I also believe the motherboard and/or operating system will become "confused" if one disk is GPT (which is UEFI partition scheme) and another disk uses older BIOS style partitioning.

So I happen to wonder about the install medium itself. If the operating system is not UEFI then it won't understand a UEFI partition and will fail once it hands off to the operating system...but windows 10 should understand UEFI (and not understand legacy BIOS). It just seems like having a setting for part of the system being BIOS and part being UEFI might be a bug waiting for a place to happen. I can't find it now, but I am thinking somewhere in all of this thread there was mention of BIOS having a separate UEFI/BIOS legacy mode for USB or other subsets of things which can choose UEFI or BIOS. This could have an effect on a USB install medium...imagine legacy USB working to start the install DVD over USB, and once execution takes over by the install disk (it is a mini-operating system), if some other UEFI/legacy mode is required it might fail because of USB issues when there is no UEFI support...the operating system has its own requirements once past finding and starting the DVD (or USB external drive).
 
Upvote 0 Downvote
G

Grimfyre

Distinguished
Feb 21, 2014
92
0
18,630
Thanks everyone for trying to help. It appears that my cpu was at fault. Not sure what happened but had a tech test the cpu and all 4 cores failed the test, so i RMA'd the cpu and the new cpu works just fine.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom