When moving to the whole OS to P2V or a new model Corrective action when 0x0000007 B error does not start

For the image as it is the operating OS installed and running
Moving by P2V from physical disk to hyper-v or vmware image acquisition and image restoration.
Or you want to start replacing only the hard disk and SSD to the new model
Troubleshooting when the OS does not start due to a bull screen 0x0000007B error when starting the OS

Start rescue with Windows Installer DVD, WinPE etc CD-ROM or DVD-R etc.
For Windows installer, issue shift + F10 command prompt.

Start Registry Editor regedit.exe.

The disk's drive letter will be waiting for you to move like D: \ or X: \
Look for the file D: \ Windows \ system32 \ config \ SYSTEM.
Specify the D: \ Windows \ system32 \ config \ SYSTEM file in the menu: File -> Load Five.
Name can be anything Good 'a' etc. OK
"A" or other subordinate
Open HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Service
If "CurrentControlSet" does not exist, if "ControlSet001" is not found, check the subordinate to "ControlSet002".

Valid if the value of START is 0. Invalid if 3.

○ For AHCI
amdxata 0
atapi 0
msahci 0
intelide 3
pciide 3

iastor 0
iastora 3
iastordatamgrsvc ※ It did not exist
iastorf 0
iastorv 3

storflt 0
storsvc 3
storvsc 3
vhdmp 3

○ intel Onboard RAID
atapi 3
iastor 0
iastordatamgrsvc 2
iastorv 0
intelide 3
msahci start 3
pciide start 3

After changing, the registry editor's hive is written and the OS starts up.