Dual boot macOS Sierra i7 7700K, MSI SLI PLUS Z170A

The Rules said:

Profiles need to contain at least your primary system to assist others with helping you.

Click to expand...

XxCobranxX said:

For the past two days I've been trying to create a dual boot for my desktop with Windows 10 and macOS Sierra. I succesfully created a bootable USB with the installation etc on it. But now I'm stuck with the following problem. After I boot from my USB into the boot loader (clover) I select the installation disk. In a few seconds codes fly by and it stops. See the last line at the picture.

The boot arguments I used were:
-v
GraphicsEnabler=Yes
PCIRoot=1
npci=0x2000

After these failed I gave it a try with the same arguments and the -x argument. I've also tried no arguments and different combinations but no succes.

The specifications of my desktop are:

CPU: i7-7700K (I used a fakecpuid with skylake id: 0x0506E3)
MOBO: MSI SLI Plus Z170A (changed the BIOS settings, copied them from this post: https://www.tonymacx86.com/threads/...s-i7-7700k-cannot-boot-into-installer.213446/ )
GPU: Gigabyte AORUS GeForce GTX 1080 Ti 11G
SSD: Samsung 850 Evo 250 GB
HDD: Seagate Barracuda 2 TB
RAM: Corsair Vengeance LED CMU16GX4M2C3200C16

Some further information I'm using the drivers64EUFI:
- EmuVariableUefi-64
- OsxAptioFixDrv-64
- PartitionDxe-64

And the following kext files are in my other folder:
- AppleALC.kext
- FakeSMS.kext
- IntelMausiEthernet.kext
- USBInjectAll.kext

Hopefully someone can help me with my problem.

Click to expand...

• The Uploaded image shows the Clover Boot loader or the Kernel can no longer access your USB Installer Disk to get data to proceed with the booting. [See edited image]

The boot arguments I used were:
-v
GraphicsEnabler=Yes
PCIRoot=1
npci=0x2000

Click to expand...

• In this Forum only CLOVER bootloader related installation is discussed.
  • GrapghicsEnabler and PCIRoot are not used as boot flags in Clover. Clover would ignore them.
  • npci=0x2000 is specifically used for a Graphics related boot problem associated with some Motherboards. I am not sure your MoBo needs that. The current Boot error is not one that needs this flag
• For the current Boot problem try the following:
  • If you have your Windows Disk connected to the System Board, DISCONNECT it till Sierra Installation is completed fully and then reconnect Windows disk but making CLOVER containing MacOS Sierra as First boot device in the BIOS Setup.
  • In the USB installer's config plist, edit Devices>USB> [√] FixOwnership [See image of Config.plist opened and edited with Clover Configurator -V [CC-V) http://mackie100projects.altervista.org/download-mac.php?version=vibrant
    
  • If on reboot with Verbose boot, ( -v ) with dart=0 flags, the same error ( you can upload the image) is seen, then shift the USB installer to a different USB 2 port preferably in the back of the MoBo.

cmn699 said:

• The Uploaded image shows the Clover Boot loader or the Kernel can no longer access your USB Installer Disk to get data to proceed with the booting. [See edited image]

• In this Forum only CLOVER bootloader related installation is discussed.
  • GrapghicsEnabler and PCIRoot are not used as boot flags in Clover. Clover would ignore them.
  • npci=0x2000 is specifically used for a Graphics related boot problem associated with some Motherboards. I am not sure your MoBo needs that. The current Boot error is not one that needs this flag

Click to expand...

• First of all thanks for your quick reaction! And you probably noticed already I'm completely new to the hackintosh world.

• For the current Boot problem try the following:
  • If you have your Windows Disk connected to the System Board, DISCONNECT it till Sierra Installation is completed fully and then reconnect Windows disk but making CLOVER containing MacOS Sierra as First boot device in the BIOS Setup.
  • In the USB installer's config plist, edit Devices>USB> [√] FixOwnership [See image of Config.plist opened and edited with Clover Configurator -V [CC-V) http://mackie100projects.altervista.org/download-mac.php?version=vibrant
    
  • If on reboot with Verbose boot, ( -v ) with dart=0 flags, the same error ( you can upload the image) is seen, then shift the USB installer to a different USB 2 port preferably in the back of the MoBo.

Click to expand...

• I've tried the possible solutions you gave me. But none of them showed any further progress. The only thing that changed was that I've got a different error message.

XxCobranxX said:

• First of all thanks for your quick reaction! And you probably noticed already I'm completely new to the hackintosh world.

• I've tried the possible solutions you gave me. But none of them showed any further progress. The only thing that changed was that I've got a different error message.

Click to expand...

cmn699 said:

For that Kernel Panic , edit config.plist in CC-V again but then go to Rt Variables to change CsrActiveConfig from 0x03 to 0x67 and Save the edited C.plist [See uploaded Image for visual details of troubleshoot]

Click to expand...

XxCobranxX said:

After this quick fix we're back at the old error code that shows the Clover Boot loader or the Kernel can no longer access my USB Installer Disk to get data to proceed with the booting. I've got my USB plugged in a USB 2.0 port on the back of my Mobo.

Click to expand...

cmn699 said:

You may upload your CLOVER folder as Compressed file to the Forum to see if there is any clue to the problem.

Click to expand...

XxCobranxX said:

Here is a compressed file of my CLOVER folder.

Click to expand...

• BOOT section is empty : please edit Boot Args: to include[√] against -v dart=0 nv_disable=1 for now Default Boot Volume =[name of your USB installer] and Default Bootloader= [EFI ]
  
• SMBIOS is empty : I think the most commonly used and working Product name( System Definition) is iMac 14,2 .
  
• In CC-V of config.plist go to SMBIOS> and click the Magic Wand icon > iMac Image >14,2 [See uploaded composite image for visual details of all the steps]

• Regarding inserting USB installer to a different port is a trial and error until you can find one that works.

• In the CC-V >Devices> USB section, place a [√] Inject .