BSOD "stop error message 0x0000007B" in Boot Camp based existing VM

Discussion in 'Installation and Configuration of Parallels Desktop' started by omprakash, Jan 30, 2012.

  1. omprakash

    omprakash Bit poster

    Messages:
    5
    Getting BSOD "stop error message 0x0000007B" while trying to start already existing Boot Camp based Windows 7 Virtual Machine .

    Windows 7 is working perfectly on Boot Camp Partition.

    any suggestions??
     
  2. YanaYana

    YanaYana

    Messages:
    1,666
  3. Germerican

    Germerican Bit poster

    Messages:
    2
    I'm having the same issue when trying to create a Windows 7 VM from my already existing Boot Camp partition with Parallels 7 Build 7.0.15054 (Revision 722853).

    My MacBook Pro stats are as follows:

    [​IMG]

    I recently replaced my OEM HDD with a 128GB M4 Crucial SSD and have about 75GB of space left.

    Windows 7 under Boot Camp works just fine without any problems, whatsoever. When I try to create a VM from Boot Camp, however, I constantly get the following Startup Repair screen when Parallels tries to automatically upgrade the "My Boot Camp" VM.

    [​IMG]

    After some time attempting to repair who knows what, Startup Repair fails with the following message:

    [​IMG]

    When I choose to upgrade the VM manually, which Parallels does not recommend, I get the following BSOD with error message *** STOP: 0x0000007B (0x8078BB58, 0xc0000034, 0x00000000, 0x00000000)

    [​IMG]

    I have spent the last two days researching a solution and all I can find are reports of the same issue dating back to 2009 and Parallels 5. Apparently, whatever the issue is, it hasn't been resolved in almost three years.

    I've read through many KB articles, none of which where able to resolve my issue, including the one YanaYana mentioned.

    I'm a little upset that I spent full retail price on Parallels 6 and then an upgrade price on Parallels 7, only to not be able to run Windows 7 as a VM through Parallels.

    Any help/lead/idea regarding this long-lasting problem would be greatly appreciated.

    Andy
     
  4. Germerican

    Germerican Bit poster

    Messages:
    2
    Just wanted to give a quick update to my previous post.

    After searching for two days, without finding an answer, I decided to start playing with some settings.

    I switched the hard drive setting in the VM configuration from SATA 0:1 to IDE 0:1 and that did the trick. VM installed without a hitch.

    Just FYI.

    Andy
     
  5. YanaYana

    YanaYana

    Messages:
    1,666

Share This Page