Black Screen When Doing Bootcamp Install

[xcodeSyn]

I used this websites strategy: http://blog.thedeltaflyer.com/2013/01/dual-booting-windows-8-and-mountain-lion-natively-using-efi/. This strategy worked perfectly until i pressed next on the windows drive selection screen. I select the drive and I press delete and then i press next. It takes me to the windows installation screen. After 5 seconds i get this error message:

Windows detected that the EFI system partition was formatted as NTFS. Format the EFI system partition as FAT32, and restart installation.

If you have indeed followed the guide step by step, then you should proceed as a normal installation. Why did you want to delete the primary partition which was created previously before clicking next? The whole idea of using the diskpart program to create 3 partitions is that Windows can be installed normally, that's why the author of the guide did not even bother to repeat the installation process in step 6.

I tried to install Win Server 2012 using the EFI boot approach but the computer froze after selecting the EFI boot icon, it's either incompatible with 4,1 Boot ROM or Win Server 2012. I ended up installing it using Boot Camp, so can't help you with EFI boot.

 

[xcodeSyn]

I tried to install Win Server 2012 using the EFI boot approach but the computer froze after selecting the EFI boot icon...

I can now confirm that the 5,1 Boot ROM is required for MP to perform the Win 8 EFI install. After upgrading my MP from 4,1 to 5,1, I was able to select EFI boot to get to Windows installer. After a few rounds of back and forth, I finally figured out how to install Windows 8 or Windows Server 2012 using EFI boot. Some portion of the guide mentioned earlier is unnecessary and we only need to follow the first 4 steps. First, the disk intended for Win 8 installation needs to be in Bay 1. All we need is to hit Shift+F10 when the start up screen appears, and then :
a. Type diskpart (to start disk partition program)
b. Type list disk (to confirm the disk exists for selection)
c. Type select disk 0 (to focus on the correct disk)
d. Type clean (wipe the disk clean)
e. Type convert gpt
f. Then type exit (no need to create any partitions before quitting)
g. Type wpeutil reboot (reboot)
h. Then Option-boot into "EFI Boot"

So far we only need an unallocated disk with GPT, and no partitions on the disk. Once in the EFI Boot installer, select the unallocated disk and click the next button, the installer will take care of the rest automatically by creating 4 separate partitions and start the install process. The important thing is to convert the disk to GPT and located in Drive Bay 1. If there are any partitions on the disk, make sure to delete all of them and just leave an unallocated disk being selected before clicking the next button. This approach uses the whole disk for Windows installation and I have no interest to add another OS partition, and the disk icon is named EFI Boot instead of Windows in the boot screen.

 

[pyrosurge]

I can now confirm that the 5,1 Boot ROM is required for MP to perform the Win 8 EFI install. After upgrading my MP from 4,1 to 5,1, I was able to select EFI boot to get to Windows installer. After a few rounds of back and forth, I finally figured out how to install Windows 8 or Windows Server 2012 using EFI boot. Some portion of the guide mentioned earlier is unnecessary and we only need to follow the first 4 steps. First, the disk intended for Win 8 installation needs to be in Bay 1. All we need is to hit Shift+F10 when the start up screen appears, and then :
a. Type diskpart (to start disk partition program)
b. Type list disk (to confirm the disk exists for selection)
c. Type select disk 0 (to focus on the correct disk)
d. Type clean (wipe the disk clean)
e. Type convert gpt
f. Then type exit (no need to create any partitions before quitting)
g. Type wpeutil reboot (reboot)
h. Then Option-boot into "EFI Boot"

So far we only need an unallocated disk with GPT, and no partitions on the disk. Once in the EFI Boot installer, select the unallocated disk and click the next button, the installer will take care of the rest automatically by creating 4 separate partitions and start the install process. The important thing is to convert the disk to GPT and located in Drive Bay 1. If there are any partitions on the disk, make sure to delete all of them and just leave an unallocated disk being selected before clicking the next button. This approach uses the whole disk for Windows installation and I have no interest to add another OS partition, and the disk icon is named EFI Boot instead of Windows in the boot screen.

thanks for your help. My boot rom version is: MP51.007F.B03


I'm still having issues after i complete all steps and select my drive i then press next and then 5 seconds later an error message comes up that reads:

"Windows could not prepare the computer to boot into the next phase of installation. To install windows, restart installation."

I restarted installation and then at the drive selection screen on windows install it wouldn't let me choose it so i selected drive > advanced and then i pressed delete. I then pressed next and then 5 seconds later i got another error message that reads:

"Windows detected that the EFI system partition was formatted as NTFS. Format the EFI system partition as FAT32, and restart installation."


Thanks for your help so far

 

[xcodeSyn]

I'm still having issues after i complete all steps and select my drive i then press next and then 5 seconds later an error message comes up that reads:

"Windows could not prepare the computer to boot into the next phase of installation. To install windows, restart installation."

I got the same message in one of my earlier attempts and it happened when the disk was in Bay 2 while Bay 1 was occupied by another OS X disk. So I suspect that you did not put your installation disk in Bay 1 as advised. If you did, then maybe your machine does have some unknown issues. If you didn't, then put the disk in Bay 1 and delete all partitions (not just one, and that's why you got your second error message) on that disk while in Windows Installer before clicking the next button. As said before, it's always a good idea to leave the installation disk in Bay 1 whether using Boot Camp or EFI Boot. Once installed, it can be placed anywhere else, even in an external bootable enclosure. This may not be an issue for other Macs, but seems critical to my EFI installation. To me, two critical factors include converting GPT only in Windows Installer and disk in Bay 1. YMMV.

 

[pyrosurge]

I got the same message in one of my earlier attempts and it happened when the disk was in Bay 2 while Bay 1 was occupied by another OS X disk. So I suspect that you did not put your installation disk in Bay 1 as advised. If you did, then maybe your machine does have some unknown issues. If you didn't, then put the disk in Bay 1 and delete all partitions (not just one, and that's why you got your second error message) on that disk while in Windows Installer before clicking the next button. As said before, it's always a good idea to leave the installation disk in Bay 1 whether using Boot Camp or EFI Boot. Once installed, it can be placed anywhere else, even in an external bootable enclosure. This may not be an issue for other Macs, but seems critical to my EFI installation. To me, two critical factors include converting GPT only in Windows Installer and disk in Bay 1. YMMV.

thats strange because i had my hard disk in bay 1 and i removed the rest and performed everything you told me and it still doesnt work. How very strange.

 

[xcodeSyn]

thats strange because i had my hard disk in bay 1 and i removed the rest and performed everything you told me and it still doesnt work. How very strange.

It is strange, and the only difference left unexplained seems to be the not so legit install disc. Maybe it's time to go back and try the Boot Camp approach with Win 7 instead. The Boot Camp Assistant would format the disk as FAT32, and you need to choose the format option in Windows Installer before proceeding. If both approaches fail, then I am out of ideas.

 

[xcodeSyn]

thats strange because i had my hard disk in bay 1 and i removed the rest

BTW I forgot to ask earlier, do you have any PCIe cards installed that might interfere with the installation? If yes, then maybe that's another possibility.

 

[pyrosurge]

BTW I forgot to ask earlier, do you have any PCIe cards installed that might interfere with the installation? If yes, then maybe that's another possibility.

Yes I do have PCie cards installed. I have 2 PCIe cards in a raid, i will remove them and see how everything turns out.


Thanks for your help so far in the forums!

 

[xcodeSyn]

Yes I do have PCie cards installed. I have 2 PCIe cards in a raid, i will remove them and see how everything turns out.

Somehow I got a feeling that these two PCIe cards may have been the root cause for all your trouble. Normally they are the first to go when looking for potential hardware conflicts. I only noticed that you used to have 6 disks connected in your MP, but those two Marvel raid drives were never mentioned specifically. You really don't need any OS X boot drives when doing EFI boot install. Good luck!

 

[pyrosurge]

Somehow I got a feeling that these two PCIe cards may have been the root cause for all your trouble. Normally they are the first to go when looking for potential hardware conflicts. I only noticed that you used to have 6 disks connected in your MP, but those two Marvel raid drives were never mentioned specifically. You really don't need any OS X boot drives when doing EFI boot install. Good luck!

THANKS SO MUCH!!!!

You were right the PCIe cards were causing the problem. From some research it turns out that the accelsior PCIe cards from OWC were causing the problem. When i was reading through through the comments it turns out that it only allows 1 PCIe maximum to boot windows on mac.

Thanks so much for your help. I'm also trying to find a fix because constantly taking these cards in and out is getting annoying but still, thanks for all your time and effort

 

[VamoozE]

I was getting the same on my iMac 27, turned out that the windows installer switches to another screen output bus internally... connecting an external display to the iMac proved it, since the installer was visible there.

Hi, Sorry if i sound silly, but how did u connect another external monitor to ur iMac? what adapter did you use? thunderbolt/mini display to via/dvi/hdmi?

Got the same issue, just needa know what to use for an external monitor..

Regards

----------

I know you might want to kill me but i have only windows 7 64 bit on disc (legit copy). So i have been pirating the other windows versions like windows 7 32bit and windows 8 64bit, nether the less they all gather the same result. The pirated windows comes in an ISO file and I opened it and i then burned to a dvd. Like i said before bootcamp runs smoothly and i have been following tutorials correctly. when bootcamp reboots my computer i hold down 'option' and then my drives come up and a disc called 'windows.' I select the disc and press enter and my computer tries to load the disc but comes to a black screen with a underscore _ that flashes 3 times then it disappears and the screen is still black. Thanks for your help on this forum , hopefully there is enough information there to help you figure out the problem.

Hey Man, I am experiencing the exact same issue with an iMac.. If i find a solution or a work around i will let you know.. i am still trying a few other things.. When u boot holding alt do you get a EFI boot or only Windows??

 

[xcodeSyn]

You were right the PCIe cards were causing the problem. From some research it turns out that the accelsior PCIe cards from OWC were causing the problem. When i was reading through through the comments it turns out that it only allows 1 PCIe maximum to boot windows on mac.

I am glad you finally identified the root problem. Since I doubt that Apple would care to fix the problem, you may have to contact OWC and they may have to work with Marvel to find a solution. I don't know if these cards also prevent booting from Windows, if they actually do then it is more serious than just preventing installation. How they could get away with this defect for so long is beyond my comprehension.

 

[xcodeSyn]

Hi, Sorry if i sound silly, but how did u connect another external monitor to ur iMac? what adapter did you use? thunderbolt/mini display to via/dvi/hdmi?

Got the same issue, just needa know what to use for an external monitor..

This issue is probably caused by the lack of graphic drivers for your iMac as explained here, and hopefully that solution will fix your problem. The reason to use another monitor is that the VGA driver from Windows installer works with all PC monitors, so you'll be able to see from another monitor. If your iMac has a thunderbolt jack, then it is also working as a mini Display Port for another monitor as long as it is connected as the last item if you also have other items connected thru TB.

 

[pyrosurge]

Hi, Sorry if i sound silly, but how did u connect another external monitor to ur iMac? what adapter did you use? thunderbolt/mini display to via/dvi/hdmi?

Got the same issue, just needa know what to use for an external monitor..

Regards

----------



Hey Man, I am experiencing the exact same issue with an iMac.. If i find a solution or a work around i will let you know.. i am still trying a few other things.. When u boot holding alt do you get a EFI boot or only Windows??

You would have to use thunderbolt or an thunderbolt adapter to fit the desired screen

----------

This issue is probably caused by the lack of graphic drivers for your iMac as explained here, and hopefully that solution will fix your problem. The reason to use another monitor is that the VGA driver from Windows installer works with all PC monitors, so you'll be able to see from another monitor. If your iMac has a thunderbolt jack, then it is also working as a mini Display Port for another monitor as long as it is connected as the last item if you also have other items connected thru TB.

Thanks for your help but i tried this fix a long time ago but it sadly didn't work

 

[Hoomanesl]

That means that the OS you're installing (Windows) can't find the CD ROM. This happens when installing Windows onto a MBP where the CD is external USB instead of internal. In the UFI firmware they hardcoded the CD to be the internal one, so you cannot boot off an install from an external which is extremely annoying.

You don't say much about the setup but presumably this is a Mac Pro which theoretically shouldn't have the problem, but obviously does. Try a different CD rom, one in the second slot or external (or maybe you already are trying an external CD?) to see if that helps.

Hi!
I have the same problem and I am using an external dvd driver because my internal one doesn't work! Is there any solution

 

[Chipg07]

After searching forever, I finally figured out an easy fix for this issue... Go thru the install process like normal, boot camp utility... All 3 check boxes... Create the usb, and as it's rebooting to install windows hold down the option key and boot back into osx...
Then open disk utility and partition tab for the boot camp drive and repartition it as mac extended journaled...
Then reboot again with option held down and go to the windows efi option...

This time when you get to the partition to install on, highlight the main boot camp partition that matches the size you made it, and hit delete... Then hit next... No more message about this is an mbr partition and it needs gpt
I hope this helps you... It solved my problem..