GPT install "Shuts sys Down"

[revin]

Ford, you have some great tut's here!!!!
Ok for a week I've been trying to get my 3Tb on GPT

I've tried all the GPART stuff, and was able to make GPT partition but now I was able to use Rufus to make USB GPT bootable with my copy of 7x64 It all works great[ boots with UEFI USB LEXAR option] it get thru loading all into Ram BUT when it get to installing win7 just before where you will choose the drive "Starting Windows", the machine suts off, just like you hit the power switch.
FWIW, the USB is the ONLY way I can get a UEFI option.

I'm stumped??

 

[FordGT90Concept]

I never used Rufus nor trying to install Windows from a USB flash stick. All I know is that the behavior you described is consistent with a controller/drive problem. For example, if you give Windows drivers and they end up not being compatible, it will restart/go off when it attempts to boot into Windows the first time...

That said, after it shut off, have you gone into the BIOS and check if there is something to similar to "UEFI: Windows Boot Manager?" Try booting to that and see if the installation can continue.

There's also a chance that Windows is trying to install to the USB stick instead of the drives. Obviously if this is the case, things aren't going to go smoothly. Have you checked the capacity to make sure it is consistent with the drives?

 

[revin]

The install has not got far enough for it to make UEFI: Windows Boot Manager, not even far enough to open the drive selection, it only gets all the install files loaded into ram, then it will go to the next screen "Starting Windows" for a fresh install. just right after that screen "Starting Windows", is when it just shut's off.

I'm using Port 1 from the Intel native SATA 6, so it's directly tied to the norhtbridge

I can boot with just regular {MBR} selected, and it load's and install's perferct.
Rufus is an awesome installer as it takes all the cmd stuff and automaites it, by making a UEFI boot then add's the .iso
Here is the log file

Rufus version 1.3.3.250
0 devices found.
0 devices found.
Found device 'Lexar USB Flash Drive USB Device'
Using autorun.inf label for drive K: 'LEXAR'
1 device found.
Sector Size: 512 bytes
Cylinders: 487, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: GPT, NB Partitions: 1
Disk GUID: {9D587E94-EEEC-438E-92FF-FF9455297119}
Max parts: 128, Start Offset: 17408, Usable = 4009720320 bytes
Partition 1:
Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
Name: 'Microsoft Basic Data'
ID: {E52FB48E-9BF4-403C-B2AA-45C7ED656E0A}
Size: 3.7 GB (4008689152 bytes)
Start Sector: 2048, Attributes: 0x0000000000000000
Found device 'Lexar USB Flash Drive USB Device'
Using autorun.inf label for drive K: 'LEXAR'
1 device found.
Sector Size: 512 bytes
Cylinders: 487, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: GPT, NB Partitions: 1
Disk GUID: {9D587E94-EEEC-438E-92FF-FF9455297119}
Max parts: 128, Start Offset: 17408, Usable = 4009720320 bytes
Partition 1:
Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
Name: 'Microsoft Basic Data'
ID: {E52FB48E-9BF4-403C-B2AA-45C7ED656E0A}
Size: 3.7 GB (4008689152 bytes)
Start Sector: 2048, Attributes: 0x0000000000000000
Found device 'Lexar USB Flash Drive USB Device'
Using autorun.inf label for drive K: 'LEXAR'
1 device found.
Sector Size: 512 bytes
Cylinders: 487, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: GPT, NB Partitions: 1
Disk GUID: {9D587E94-EEEC-438E-92FF-FF9455297119}
Max parts: 128, Start Offset: 17408, Usable = 4009720320 bytes
Partition 1:
Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
Name: 'Microsoft Basic Data'
ID: {E52FB48E-9BF4-403C-B2AA-45C7ED656E0A}
Size: 3.7 GB (4008689152 bytes)
Start Sector: 2048, Attributes: 0x0000000000000000
Scanning ISO image...
Disc image is an ISO9660 image
ISO label: 'CD_ROM'
Size: 3105732608 bytes
Has a >4GB file: No
Uses EFI: Yes (win7_x64)
Uses Bootmgr: Yes
Uses WinPE: No
Uses isolinux: No
Using ISO: ROG-RAMPAGEx64.iso
WIM extraction method(s) supported: 7z, wimgapi.dll

Format operation started
Requesting disk access...
Caution: Opened drive \\.\PHYSICALDRIVE3 for write access
Will use 'K': as volume mountpoint
Analyzing existing boot records...
Drive has a zeroed non-bootable master boot record
Closing existing volume...
Clearing MBR/PBR/GPT structures...
Partitioning (GPT)...
Closed Windows format prompt
Formatting (FAT32)...
Using cluster size: 4096 bytes
Creating file system: Task 1/5 completed.
Creating file system: Task 2/5 completed.
Creating file system: Task 3/5 completed.
Creating file system: Task 4/5 completed.
Creating file system: Task 5/5 completed.
Format completed.
Found volume GUID \\?\Volume{c5f5e5e2-d97a-11e2-8fa6-74f06df31d92}\
Successfully remounted Volume{c5f5e5e2-d97a-11e2-8fa6-74f06df31d92}\ on K:\
Copying ISO files...
Extracting files...
Disc image is an ISO9660 image
Extracting: K:\autounattend.xml (7.6 KB)
Extracting: K:\boot\bcd (256.0 KB)
Extracting: K:\boot\boot.sdi (3.0 MB)
Extracting: K:\boot\bootfix.bin (1.0 KB)
Extracting: K:\boot\bootsect.exe (110.0 KB)
Extracting: K:\boot\en-us\bootsect.exe.mui (15.5 KB)
Extracting: K:\boot\etfsboot.com (4.0 KB)
Extracting: K:\boot\fonts\wgl4_boot.ttf (46.3 KB)
Extracting: K:\boot\memtest.efi (596.9 KB)
Extracting: K:\boot\memtest.exe (474.4 KB)
Extracting: K:\bootmgr (374.8 KB)
Extracting: K:\bootmgr.efi (653.9 KB)
Extracting: K:\efi\microsoft\boot\bcd (256.0 KB)
Extracting: K:\efi\microsoft\boot\cdboot.efi (430.5 KB)
Extracting: K:\efi\microsoft\boot\cdboot_noprompt.efi (430.5 KB)
Extracting: K:\efi\microsoft\boot\efisys.bin (1.4 MB)
Extracting: K:\efi\microsoft\boot\efisys_noprompt.bin (1.4 MB)
Extracting: K:\efi\microsoft\boot\fonts\wgl4_boot.ttf (46.3 KB)
Extracting: K:\read-me-not.txt (110 bytes)
Extracting: K:\sources\boot.wim (172.4 MB)
Extracting: K:\sources\install.wim (2.7 GB)
Extracting: K:\sources\setup.exe (260.0 KB)
Win7 EFI boot setup (this may take a while)...
Opening: K:\sources\install.wim:[1] (7-Zip)
Extracting: K:\efi\boot\bootx64.efi (From Windows\Boot\EFI\bootmgfw.efi)
7z.exe did not extract K:\efi\boot\bootmgfw.efi
Opening: K:\sources\install.wim:[1] (API)
Extracting: K:\efi\boot\bootx64.efi (From Windows\Boot\EFI\bootmgfw.efi)
Closing: K:\sources\install.wim
Finalizing, please wait...
Created: K:\autorun.inf
Created: K:\autorun.ico
Successfully remounted Volume{c5f5e5e2-d97a-11e2-8fa6-74f06df31d92}\ on K:\

Found device 'Lexar USB Flash Drive USB Device'
Using autorun.inf label for drive K: 'CD_ROM'
1 device found.
Sector Size: 512 bytes
Cylinders: 487, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: GPT, NB Partitions: 1
Disk GUID: {DFC54DB3-4FEE-42D4-A921-661380257265}
Max parts: 128, Start Offset: 17408, Usable = 4009720320 bytes
Partition 1:
Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
Name: 'Microsoft Basic Data'
ID: {6C965DAB-35F4-4382-B26B-4732CCE74249}
Size: 3.7 GB (4008689152 bytes)
Start Sector: 2048, Attributes: 0x0000000000000000
Saved 'C:\Users\Administrator\Downloads\rufus.log'

 

[FordGT90Concept]

The install has not got far enough for it to make UEFI: Windows Boot Manager, not even far enough to open the drive selection, it only gets all the install files loaded into ram, then it will go to the next screen "Starting Windows" for a fresh install. just right after that screen "Starting Windows", is when it just shut's off.

Ah, on XP install, that's exactly what would happen if I supplied the wrong F5 drivers. What basically is happening is that Windows is copying the files to a temporary location and when it tries to execute those files, they don't exist. How to fix that in your case, I'm not really sure. I guess the first thing I would do is try to avoid using a USB flash stick--it's creating an extra point of failure.

 

[revin]

I get what your saying, But it will USB install with MBR just fine.
Also I dont have to load any drivers for any of my Win 7 install's my board is all native.

The USB stick is not any differant than when you use a USB external DVD drive to setup, it's just how to get a UEFI bootable device.

Why on earth wont an internal SATA Blu-Ray burner boot UEFI ??!!!!!!!

 

[FordGT90Concept]

When dealing with GPT, it has to be EFI boot to setup, EFI resume setup after initial file copy, and EFI boot into Windows. If any of those are not EFI, it won't work. MBR is far less temperamental.


When I did it, it only worked on my external USB DVD drive. Every other path I tried failed (including the internal SATA drives). Granted, I never tried USB stick. I would try it if I had a EFI system available to me right now but, unfortunately, I don't.

Personally, I think someone, somewhere, half-assed EFI. I don't know if it is EFI devs, Microsoft, or Intel, but someone did. This USB-only stuff is nonsense.


Maybe you could list all the boot options the motherboard gives you?

 

[revin]

Thanks Ford, again your tutorial is great!!!Yes it is a temermental turd! Lol
On the DZ68, it's the option "UEFI Enable/Disable "
SATA HDD: IDE ACHI RAID
I use ACHI

So I set it to enable, and when I format the USB[GPT], either Gparted, or Rufus it then shows in "Boot Device" USB:Lexar, Toshiba xxxxxxHdd, LG xxxxBD-R/RW, :UEFI USB Lexar
[I have all other drives unhooked]
But if when formated the Hdd Raw[no os] to GPT, it DONT show UEFI, there again is the catch 22, even if I format the Hdd to GPT, it will NOT allow Windows 7 to install since it MUST install the GPT tables itself

I could understand there was some conflict IF the setup was at a point where it was rebooting, but it's not that, it's still in virtual mode using Ram to perform setup

Thing is, there is TON's of people installing Win7 in GPT

Come on Guru's, chime here and give us some help

EDIT: GT 'ole m8te you've hit on a key:
[ Note How to Install Windows 7 Using the "Unified Extensible Firmware Interface" (UEFI)

You will need to satisfy the following requirements in order to proceed:

A Windows 7 compatible system
A Windows 7 x64-bit installation media. 32-bit is not supported.
A UEFI v2.0+ compliant PC. Check your chipset manufacturer/firmware documentation.
A blank, partition-free, hard disk for installation

Just tried an MBR install[was goung to format the first Partition} by golly, on the normal Install after loading into Ram, then to go to select disc, low an behold it should have said" Initiating ROG", instead of Starting Windows"

So i'm going to wipe the disc, nd try again with Rufus................brb i hope

 

[FordGT90Concept]

My guide tells you how to pre-partition it. GPT requires three partitions on the volume. I never tried installing without pre-partitioning. Have you followed the diskpart portion of the guide?

 

[revin]

,[I had actually started my post there, but moved it to this new post to keep your post clean
Yes I did your guide when I first tried but "Error: Windows cannot install to a GPT Partition"
As in my previousUEFI Install link Windows MUST make those partitions
Your guie is how I do the clean disc, ect
Again thank you for making it.

 

[FordGT90Concept]

"Error: Windows cannot install to a GPT Partition"

The only time Windows cannot install to a GPT partition is when Windows setup is not running via EFI.

 

[revin]

Awe hell, thanks again bro!!! that was before I got that Rufus to get EFI boot !
Since all my other drive BCD's[or mostly just winload.exe error] are blown I gotta get the wife's lappy and do the back and forth thing. I'll try when I can the next day or 2 and see if I can start fresh!!

 

[revin]

Yep something not working right. Started over with clean disc
It still try's to "Start" Windows after loading into Ram, instead of "Initiating Setup", just before where you select the drive..........I'm stumpiss'd ???????????

How the hell is evr1 else getting EFI/GPT?????????????

 

[FordGT90Concept]

Did you follow my guide to the letter making sure to do everything via EFI boot?

 

[revin]

Yes. It will not get past the handoff from Ram to windows setup.
It keeps trying to "start" windows, then shut down instead of the handoff to make a drive selection. I've went thru soooo many guides and rechecked all the bootx64.efi ect files are all there where they should be but something just not "hooking" correctly.

 

[FordGT90Concept]

I'd blame either your motherboard or Rufus.

 

[revin]

I tried an old Ext. LG USB DVD 1 touch capture device, but it wont boot EFI