migrating win7 physical comp to vb gives bsod

[missjuly]

hello,
my current project is to upgrade my computer to win10 from win7. I'd like to create a virtual machine out of my physical comp just in case I needed to look up some settings.

so I created a .vhd file using disk2vhd and added as a drive to vbox. this didn't work out because the file it created didn't have a boot sector and diskpart refused to recognize a partition to set active.
then I created a backup of my current system using acronis true image. I also created a acronis bootable cd. I was able to boot from it, find a backup and restore to my .vhd or .vdi images.
The guest starts but then gives a bsod like this:

v bsod.jpg (84.5 KiB) Viewed 1193 times

I thought windows would fix this so I first tried using the cd and attempt repairs. it failed like this:

v repair fail.JPG (55.88 KiB) Viewed 1193 times

I tried hitting F8 at boot up to go into safe mode but it gets stuck at this, then bsod:

v safe mode.jpg (114.89 KiB) Viewed 1193 times

I thought it was disk related so I also set it to treat the drive as ide and not sata, eventually I made an exact drive copy and used .vmdk to mount it in vbox. Same.
It seems to be getting stuck at boot up. I'm guessing it's driver related?
could anyone point me in the right direction here?

thank you!

[mpack]

Stop 0x7B has been discussed many times in the past. I suggest a Google search.

[missjuly]

Of course. That's what I started with. After 2 days of reading and attempts I finally gave in. So here I am.

[mpack]

In the top hit I already say everything that is known about the error, so I don't see what additional help you expect.

[missjuly]

Thank you for your reply.

I have been trying to test and apply any fixes that this forum or google gave me. I still have to find one that works for me. So far nothing worked.

[missjuly]

got it to work but what a trip....
so for those out there that need to migrate their windows 7 physical machines to a virtual world, here is how I did it.

thanks to mpack I ran across these two posts:
viewtopic.php?f=2&t=49954 - (look at 14. Jun 2012, 16:09)
https://communities.vmware.com/message/2030146 - (look at May 7, 2012 6:49 AM)

this was not a complete one step solution because every hardware is different. In my case I had to adjust entries as follows:
Aliide = 3
Amdide = 3
Atapi = 0
Cmdide = 3
iaStorV = 3
intelide = 0
msahci = 0
pciide = 3
viaide = 3
lsi_sas = 0
lsi_scsi = 0

to make things easier, have a clean w7 install vbox ready to compare those registry entries with a .vhd copy of the system that's giving you problems.
thanks again.