BSOD when loading virtualbox on Oracle VirtualBOX. Where to dig?

Question

virtual box

There is a task to remove a copy from a running machine and run it in a virtual machine. After cleaning from garbage, the system occupies 135 gigabytes. The working disk is assembled on a zero raid. OS W7x64. What was done.
1. I took a disk2VHD image in VHD format. Removed only the C: drive. But generally in system 2 logical disks.
2. I created a new x64 machine in VirtualBOX, picked up my image.
3. Recreated the boot partition using the W7 installation disk.
4. When creating the image, the information about the logical D: was written anyway. Removed. That is, now the image contains information only in the form of a 100 MB boot partition and the C: drive itself.
5. I start the machine: it loads, it comes to the running line, then bsod and reboot.
Virtualka settings twisted in different ways. It's still bsod. :(

Answer 1

Transferring installed Windows from hardware to a virtual machine is like transferring a hard drive with Windows from one machine to another: it often loads without problems (machine of the same generation + some luck), but sometimes it crashes into a BSOD. The reason is that the set of drivers and their settings are tailored for specific hardware, and without the necessary drivers, the system cannot boot. In the general case, Windows assumes booting only on the hardware on which it was installed.
Typical solutions (in descending order of probability):
Much less likely, but worth a try:

1. System-> Chipset:change.
   
2. Storage-> Attributes-> Type:change.
   

Answer 2

There is an idea to recapture the system image to a virtual disk of the .vmdk format, that is, first create such a disk, then onto it using a utility, for example: www.macrium.com/reflectfree.aspx (in my opinion it is very convenient because it drags the boot sector ), then on the hypervisor you give out the same capacities as in physics and should essentially take off.

Answer 3

Look at the BSOD error code, maybe something will clear up. On a real computer, first of all, you need to look at IDE-AHCI in BIOS, on a virtual machine, you can also switch them somewhere. Nothing can be said without the error code.

Answer 4

I caught bsod:
do I understand correctly that this is precisely the incompatibility of disk firewood?