I’ve just converted a Windows Seven physical desktop to a virtual machine using VMware converter. It’s a great piece of software because it work at file system level so it can:
0x0000007B (0xFFFFF9, 0xFFFFFFFFC0000034, 0x000000, 0x000000) Nothing's been changed in the system. The last update was my Catalyst drivers being updated but they've been working fine since. I've got Ubuntu running on the same disk (the Intel SSD) so I have access to the windows partition. Hi guys, im hoping one of you can help me, im trying to dual boot XP onto my win 7 machine and its just not working! Its getting to the 'windows is starting setup' screen on installation then blue screening with a stop 0x0000007b (0xf7802524, 0xc0000034 0x0000000 0x0000000) error, im pretty sure.
- Create a unencryped VM of a Bitlocker encrypted physical machine
- Save the image of a disk, on the disk it self.
The created image can be used in Virtualbox, but before doing so some disk drivers may need to be enabled else you’ll get a BSOD with:
It’s easier to enable the drivers from the physical system, before creating the disk image. To do so run
regedit
and set the following keys:HKLMSystemControlSet001msahciStart=0
HKLMSystemControlSet001intelideStart=0
I guess that 0 mean enabled and 3 mean disabled. I’m almost sure that
intelide
is not required if you setup the virtual disk as a SATA device. I don’t know which one of ControlSet001
or ControlSet002
so I edited both.If, as I did, you forgot to enable those drivers before creating the disk image, it’s possible to do it after. Although I’m sure it’s possible, I’ve not been able to do it from the recovery console. So I added the disk image to an other Windows Seven virtual machine, let’s say as the G: drive. Then:
- Run
regedit
- Select a root key (any of them)
- File, Load Hive, and select
G:WindowsSystem32configSYSTEM
- Give a name, let’s say DUMMY
- Edit the keys as previously explained
- Select the DUMMY key, File, Unload Hive
Advertisements
I've been dualbooting Windows 7 and Manjaro for about a year now, and I'm getting tired of rebooting every time I want to switch operating systems. I recently heard about the Virtualbox option to run an existing partition in a VM, so I decided to try that. To clarify, I have 4 partitions on the hard drive: Manjaro, a boot partition, Windows and a data partition for windows which contains the User folder, and probably needs to be available on boot.
I created a raw disk image of the whole drive, and ran it in Virtualbox. It got to the boot loader, I chose Windows, and it showed the 'Starting Windows' text for about 3 seconds. It then threw a blue screen and shut down. The error code was:
When booting normally it works fine. My theory is that it can't find or mount the data partition, and therefore crashes, but I don't know how to check if that is the case, or what to do with it if it is.
So, what is causing this error, and how can I fix it?
Sindre StephansenSindre Stephansen
2 Answers
The problem is that you only have the intel AHCI driver enable, and not the generic one.So you have to enable drivers that aren't. I don't know which ones particularly but, what I've done for myself worked pretty well except on one case:
- Go to regedit and go to HKEY_LOCAL_MACHINESystemCurrentControlSetServices
- Find the following folders: aliide, amdide, atapi, cmdide, iastor (may not exists), iastorV, intelide, LSI_SAS, msahci, pciide and viaide
- Set all their 'start' value to 0 in order to enable all theses drivers at boot
- Save your changes
- Restart into VirtualBox
If it don't work first, change your SATA controller to an IDE or SCSI one in Virtualbox, that should do it.
If you're still stuck congrats, you're stuck like me. It's an SCSI controller problem from VirtualBox, especially if your BSOD comes from CLASSPNP.sys if you boot in Safe Mode within VirtualBox.
X.LINKX.LINK1,31433 gold badges1212 silver badges2929 bronze badges
In some cases, 0x0000007b is caused by a setting which restricts the installation of devices on your computer. It may have been applied by your administrator. Microsoft describes a fix here.
The steps to address the issue are:
- Boot Hiren's BootCD in the VM
- Run Lazesoft Windows Recovery
- Select the windows drive
- Repair Tools -> Registry Editor
- Open [HKEY_LOCAL_MACHINESystemControlSet001ControlPnP]
- Set values to:
- 'DisableCDDB'=dword:0000000
- 'DontStartRawDevices'=dword:0000000
- Click the button 'Write Changes to Disk'
- Restart
26311 gold badge44 silver badges1515 bronze badges