Installer reboots around the 50% progress bar (i5 3rd gen, nvidia 970)

System: i5 third gen, gigabyte series 7 board, 16gb ram. I have configured the bios as recommended.
I do have a nvidia 970 gtx, tried nv_disable=1 and get the prohibited sign, tried configuring in bios to initialize the igfx card first and booting from the integrated intel card, tried safe mode.

Unibeast was configured in UEFI desktop mode. Didn't choose inject nvidia. Booting from F12 and choosing UEFI usb.

Do i have another option before i have to remove the nvidia card?

EDIT: on safe mode i get the OsxAptioDrvFix and relocation block error, but i am using the latest unibeast so this shouldn't be an issue? From the "big list" thread i don't understand where it says "If OsxAptioDrvFix doesn't work, try OsxAptioDrv2Fix (but not both at once)." Do i have to put something on the boot flags?

Disable igfx in BIOS, add nv_disable=1 to Clover options.

fjleon1980 said:

System: i5 third gen, gigabyte series 7 board, 16gb ram.

Click to expand...

I think you'll have more luck if you list the specific motherboard model in the system config area to the left and/or your signature.

fjleon1980 said:

I do have a nvidia 970 gtx, tried nv_disable=1 and get the prohibited sign

Click to expand...

I would start from here. Set the BIOS to boot from the 970 with nv_disable=1. If you get the prohibited sign, boot verbose and see if it's the AptioFix problem. (You can try with integrated graphics both enabled and disabled and see if there's any difference.)

fjleon1980 said:

EDIT: on safe mode i get the OsxAptioDrvFix and relocation block error, but i am using the latest unibeast so this shouldn't be an issue? From the "big list" thread i don't understand where it says "If OsxAptioDrvFix doesn't work, try OsxAptioDrv2Fix (but not both at once)." Do i have to put something on the boot flags?

Click to expand...

Try to download and run Clover and install to a scratch USB if you have one. Choose to "Customize" the install and make sure to select drivers64UEFI/OsxAptioFix2Drv-64 and after it installs, copy EFI/CLOVER/drivers64UEFI/OsxAptioFix2Drv-64.efi to your regular USB install drive's EFI partition and move away the OsxAptioFixDrv-64.efi that's currently there.

(If you're in Legacy mode, the files would be on the drive itself instead of the EFI partition.)

This is a bit of a long shot; most people don't get the relocation block problem using Clover v3270 or higher (included in UniBeast 6). But it may be an issue specific to your motherboard.

i always have it disabled, since i would get a reboot i tried moving my dvi monitor cable to the igfx port and enabling it in bios. In both cases i tried nv_disable=1

I think you'll have more luck if you list the specific motherboard model in the system config area to the left and/or your signature.

Click to expand...

You are right, just added it. Gigabyte z77-d3h, intel i5 3570k and asus strix 970

I would start from here. Set the BIOS to boot from the 970 with nv_disable=1. If you get the prohibited sign, boot verbose and see if it's the AptioFix problem. (You can try with integrated graphics both enabled and disabled and see if there's any difference.)

Try to download and run Clover and install to a scratch USB if you have one. Choose to "Customize" the install and make sure to select drivers64UEFI/OsxAptioFix2Drv-64 and after it installs, copy EFI/CLOVER/drivers64UEFI/OsxAptioFix2Drv-64.efi to your regular USB install drive's EFI partition and move away the OsxAptioFixDrv-64.efi that's currently there.

Click to expand...

So the idea is to install a newer clover to another usb and grab the files to update the unibeast usb? I don't know if i prefer doing that or removing the card (i have another usb but it's a little chore to backup its data and formatting hfs, it may be less trouble to remove the card)

Anyway thanks both of you i will try something tomorrow

Make sure your not injecting. And boot with with -v nv_disable=1

i fixed this by removing the nvidia card and then running the installer. I panicked because when i added the card back i would get 1 long beep and then 2 short beeps from the motherboard. Had to short out the CMOS jumper 2 times! Pretty scary, thought i fried the card.