10 Replies Latest reply: Oct 12, 2013 10:02 AM by Scotch_Brawth
Scotch_Brawth Level 3 Level 3

Hi,

 

I had a working Windows 7 x64 Pro Boot Camp setup until recently.  Now, when I attempt to boot from the Statup Manager, I can select the Windows partition but it simply sits at a black screen indefinitely.  I attempted to set the Windows partition as the Startup Disk from the System Preferences, but it doesn't appear.  I've attempted to boot from the Windows 7 Installation DVD in order to perform a Windows Startup Repair, but that black screens in the same manner as the Windows partition.

 

Here's the result of sudo gpt -r -vv show disk3 on the relevant disk:

 

gpt show: disk3: mediasize=500107862016; sectorsize=512; blocks=976773168

gpt show: disk3: Suspicious MBR at sector 0

gpt show: disk3: Pri GPT at sector 1

gpt show: disk3: Sec GPT at sector 976773167

      start       size  index  contents

          0          1         MBR

          1          1         Pri GPT header

          2         32         Pri GPT table

         34          6        

         40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

     409640  156303528      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

  156713168    1269536        

  157982704  659841040      3  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

  817823744     262144        

  818085888  158687232      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  976773120         15        

  976773135         32         Sec GPT table

  976773167          1         Sec GPT header

 

Here's the result of sudo fdisk /dev/disk3 on the relevant disk:

 

Disk: /dev/disk3geometry: 60801/255/63 [976773168 sectors]

Signature: 0xAA55

         Starting       Ending

#: id  cyl  hd sec -  cyl  hd sec [     start -       size]

------------------------------------------------------------------------

1: EE    0   0   2 - 1023 254  63 [         1 -  818085887] <Unknown ID>

*2: 07 1023 254  63 - 1023 254  63 [ 818085888 -  158687232] HPFS/QNX/AUX

3: 00    0   0   0 -    0   0   0 [         0 -          0] unused     

4: 00    0   0   0 -    0   0   0 [         0 -          0] unused     

 

So far as I can tell, this means my hybrid MBR setup is intact, but I could be wrong.  I should point out that this drive doesn't actually contain a bootable OS X partition, which exists on a completely separate drive and boots just fine.

 

Anyone able to assist?


Mac mini (Mid 2011), OS X Mountain Lion (10.8.2), 256GB SSD, 500GB HDD, 8GB RAM
Solved by Scotch_Brawth on Oct 12, 2013 10:02 AM Solved

Turns out the culprit is my Plextor PX-120U USB BDROM drive.  I unplugged it and Windows now boots fine.

 

Just in case anyone else encounters the same problem…

Reply by Scotch_Brawth on Sep 16, 2013 4:47 PM Helpful

Following advice from a thread on MacRumors, I unplugged everything except the keyboard, mouse and monitor and Windows booted fine.  So, it must be a hardware incompatibility issue.  I'll figure out exactly which device is responsible tomorrow.

 

Thanks for the additional replies.  For anyone who's interested, I'll post the device responsible once I've figured it out.

All replies

  • RB DEAL Level 1 Level 1

    I was getting the same and my problem was Intel HD 4000 drivers.  Had to update the EFI to 2.6, upgrade to Lion, and reinstall the drivers.  Works fine now.  I was on a macbook air.

  • Scotch_Brawth Level 3 Level 3

    I don't run an Intel HD 4000, but I think I did do an Thunderbolt update recently.  I don't think would have affected the Boot Camp install.

     

    OOC, how did you "reinstall the drivers" if you couldn't boot into Windows?

  • RB DEAL Level 1 Level 1

    Safe mode would boot fine.  Windows was running, just the display was not coming on.  Safemode disabled the third party drivers and the dislpy would fire right up.

  • Scotch_Brawth Level 3 Level 3

    Safe Mode doesn't work either.  Besides, I don't see how this could be a driver issue.  The install worked fine when I last used it.  It's something that's happened when I wasn't in Windows that's caused a breakage.

  • Scotch_Brawth Level 3 Level 3

    Help?

  • GregoryBL Level 1 Level 1

    Looks like you lost your mac recovery partition between the second and third GPT parts.

     

    Not sure why this would mess up your Windows partition - the only difference seems to be that it has a different number.

     

    Maybe someone who knows more than I do about this will know how that could mess it up and how to fix it.

  • Christopher Murphy Level 3 Level 3

    It might be worth seeing if rEFInd can help find the various parts of the Windows bootloader to get this to work. Otherwise it's exploratory sugergy to find out what's going on. The Apple CSM-BIOS isn't configurable, so it might be blindly loading the first available Windows bootloader it comes across instead of the one for the drive that contains the bootable Windows installation - i.e. if the external ever had a Windows install attempt onto it, it'll have a bootloader, even if the install never worked or you reformat it. Two Windows bootloaders will cause such problems. If there's no possibilty of two drives containing two bootloaders then it's some other confusion or corruption either at the bootloader level or maybe even NVRAM.

  • kbajpai Level 1 Level 1

    I have actually made it possible to use gdisk & rEFit to triple boot the system with Mac, Windows8 & Windows7. Right now I don't have time, but tomorrow for sure I will post the reply.

  • Scotch_Brawth Level 3 Level 3

    Following advice from a thread on MacRumors, I unplugged everything except the keyboard, mouse and monitor and Windows booted fine.  So, it must be a hardware incompatibility issue.  I'll figure out exactly which device is responsible tomorrow.

     

    Thanks for the additional replies.  For anyone who's interested, I'll post the device responsible once I've figured it out.

  • Scotch_Brawth Level 3 Level 3

    Turns out the culprit is my Plextor PX-120U USB BDROM drive.  I unplugged it and Windows now boots fine.

     

    Just in case anyone else encounters the same problem…