0x0000007b Blue Screen of Death on boot

T

timeshifter

Bit poster
Using the latest versions of Transporter and Parallels Workstation I'm having some trouble. I've installed Transporter and it seems to work fine. I've tried it two ways. One by running it on the machine I want to migrate and writing to a second hard drive, then copying the resulting files to the new host machine. I've also tried it by running the software on the new host PC and having it pull the files off the "old" PC across the network.

During boot I get a Blue Screen of Death (BSOD) with the error 0x0000007b. I think this may be because my "old" PC is a Dell Dimension 8400 with SATA drivers and the VM uses standard IDE drivers. Boot.ini does get processed and I get as far as the Windows logo for just a moment.

I tried booting the Windows install CD to do a repair installation. It recognizes the C: partition but not it's format (I think it says "unknown format"). Also, when I boot my BartPE disk and try to look at the C drive it doesn't recognize the format either.

I've had a different level of progress using Acronis True Image. It won't boot at all as a Windows PC but I can boot with BartPE and it reads the C drive just fine. I'll post a separate thread about that in the appropriate section.

Is there something I'm doing wrong? Any suggestions.
 
Hello. Please try to repair your Windows installation:
1. Insert your XP installation disk, set booting from CD
2. Run VM, wait for copying necessary files
3. In next screen press Enter, and then F8 to accept EULA
4. Choose "Repair"

I hope it will help
 
Thanks Archy, but I already tried that. When it gets to the point where it'd normally offer the option for repair it doesn't recognize the disk format of C: - it says something like "unknown format". Don't remember the exact message right now.
 
Archy said:
http://support.microsoft.com/kb/324103/en-us
Click to expand...
This article covers all kinds of things, none of which apply. I had seen both of these before I posted.
Archy said:
http://support.microsoft.com/kb/314082/en-us
Click to expand...
To resolve this error, use the same hardware for the backup computer:
• Replace the problem hardware components in the backup computer with components of the same manufacturer, make, and model as the motherboard in the computer that you are backing up.
• If the system disk is a SCSI disk, use the same make and model of SCSI controller in the new computer.
• If the system disk is an IDE disk, use the same kind of motherboard in the new computer, a motherboard that has the same kind of IDE chip set and the same PnP-ID as the motherboard in the computer that you are backing up.
Click to expand...
Th second article says to use the same hardware. Well, that kind of defeats the whole purpose doesn't it. It may have something to do with the fact that my old machine (that I'm migrating from has SATA drives while the Parallels VM emulates IDE.

Here's where it gets more interesting. IT ALL WORKS ON MY MAC RUNNING THE LATEST PARALLELS!

There are no STOP errors or other showstoppers. I moved over the EXACT SAME VM that Transporter created to the Mac and it booted it the first time.

To be more thorough I installed Parallels Workstation on a Windows XP Media Center 2005 machine. Got the same 0x0000007b error on that as I did on my Vista machine. So the score is:

Mac with Parallels - Works
Vista with Parallels - not work
XP with Parallels - not work
 
Hello Timeshifter,

Thanks for your detail investigation.

The design of this Transporter version (is a built-in feature in Parallels Desktop for Mac) concentrates on the possibility to allow the migration of remote Windows PC over network to Parallels VM on your Mac.

The some problems may occur with the old version of Parallels Workstation. Now we are working at this point, and it will be taken into account in the next version of Parallels Workstation.

Best Regards,
Helen.
 
You must log in or register to reply here.
Back
Top