I'm trying to get windows onto a new PC, and I'm getting stuck at the 'select a driver to install' screen.
System specs are:
Gigabyte Aorus Gaming 7 x399 MB
Crucial CT1050MX300 1tb M.2 drive (x2)
I've updated the bios to F3g. I've tried the following set-ups:
1 x M.2 installed, sata mode AHCI
2 x M.2 installed, sata mode RAID. Raid level: volume. Each m.2 as a separate volume
2 x M.2 installed, sata mode RAID. Raid level: raid 0. Both m.2s set as a single 2tb raid drive.
Every time, windows gets to 'select a driver to install' - when sata is set to raid, if I browse to the Hw10 folder on a usb stick, it shows the 'AMD Raid bottom device', then when installed if I repeat the process, it shows the raid controller to install (all as expected on page 67 of the MB manual), but once installed its still stuck expecting drivers.
If I set AHCI, it expects drivers, but doesn't show the contents of the Hw10 folder without unchecking the 'hide' checkbox. Also, in AHCI mode, I can see the drives in diskpart from the windows installer, but in raid mode I can't.
Are there other drivers it's expecting? I tried downloading the chipset drivers from the site, but it's just an executable, so it's no use.
I'm installing windows from a USB I put the ISO on, and selecting drivers from a second USB. I copied the entire DVD that came with the MB onto the second USB, as well as new copies of the relevant drivers from the gigabyte website.
I'm trying to clean install windows 10, and I can only go from the ISO, as I don't have a windows computer to create a custom image from (my only other working machine is an old mac laptop)
I think that's all the relevant info, but I'm happy to provide more.
*edit* I don’t want to use the drives as a raid volume, I want them as separate drives. I’m only messing with raid mode because AHCI didn’t work
*edit 2* I read somewhere on the internet someone said they had a similar problem and it turned out windows didn't like their USB key - so I tried a different one, and now I get 'windows failed to start' error code 0xc000000d with the new key
*edit 3* I tried a third USB, and it's the same as the first - asking for drivers. I swapped out both the M.2 cards for an old SATA HDD from a laptop and I still get the same message, so it looks like it's nothing to do with the M.2 drives. Please, someone have a suggestion. I'm starting to lose it here...
System specs are:
Gigabyte Aorus Gaming 7 x399 MB
Crucial CT1050MX300 1tb M.2 drive (x2)
I've updated the bios to F3g. I've tried the following set-ups:
1 x M.2 installed, sata mode AHCI
2 x M.2 installed, sata mode RAID. Raid level: volume. Each m.2 as a separate volume
2 x M.2 installed, sata mode RAID. Raid level: raid 0. Both m.2s set as a single 2tb raid drive.
Every time, windows gets to 'select a driver to install' - when sata is set to raid, if I browse to the Hw10 folder on a usb stick, it shows the 'AMD Raid bottom device', then when installed if I repeat the process, it shows the raid controller to install (all as expected on page 67 of the MB manual), but once installed its still stuck expecting drivers.
If I set AHCI, it expects drivers, but doesn't show the contents of the Hw10 folder without unchecking the 'hide' checkbox. Also, in AHCI mode, I can see the drives in diskpart from the windows installer, but in raid mode I can't.
Are there other drivers it's expecting? I tried downloading the chipset drivers from the site, but it's just an executable, so it's no use.
I'm installing windows from a USB I put the ISO on, and selecting drivers from a second USB. I copied the entire DVD that came with the MB onto the second USB, as well as new copies of the relevant drivers from the gigabyte website.
I'm trying to clean install windows 10, and I can only go from the ISO, as I don't have a windows computer to create a custom image from (my only other working machine is an old mac laptop)
I think that's all the relevant info, but I'm happy to provide more.
*edit* I don’t want to use the drives as a raid volume, I want them as separate drives. I’m only messing with raid mode because AHCI didn’t work
*edit 2* I read somewhere on the internet someone said they had a similar problem and it turned out windows didn't like their USB key - so I tried a different one, and now I get 'windows failed to start' error code 0xc000000d with the new key
*edit 3* I tried a third USB, and it's the same as the first - asking for drivers. I swapped out both the M.2 cards for an old SATA HDD from a laptop and I still get the same message, so it looks like it's nothing to do with the M.2 drives. Please, someone have a suggestion. I'm starting to lose it here...
Facebook
Twitter
Instagram