StarWind Software

Hello, we have moved a physical machine with the converter.
Unfortunately we cannot start the machine. We always get a blue screen. The blue screen is gone so quickly that we cannot see what the problem is.
In the converter there was no possibility to select the "repair mode". A repair with a Windows CD is not possible.
We think the problem is that the new hardware is not recognized.

Is there a solution to the problem?

Kind regards
Björn Harrenberger

Hello,

More details thrown into this thread will be highly appreciated.
1. You did P2V conversion if I am not mistaken. Where have you moved it? Is it cloud or some physical server?
2. Is the VM running? If so, send us the dump files, please. Transfer dumps via some service like Google Disk or Dropbox.
3. Windows repair mode option works only for vmdk (with OS inside) <->vhdx conversion (both directions).

Hello Yaroslav,

here are my answers to your questions:
1. yes I did a P2V conversion. the now virtual machine is to run on a physical computer Win10 1903 in Hyper-V. For your information: it is a programming environment that cannot be reinstalled.
2. no the machine makes a blue screen immediately after starting (see photo). so I can't get a dump file. However, I exported the event viewer. At first glance, there is no problem for me here.
3. Ok I understood that. I suspect that I have the problem that the new hardware is not recognized.

Please give me a path where I should save the file

Best Regards

Could you enable hardware compatibility mode for that VM?

https://docs.microsoft.com/en-us/previo ... v%3Dws.11)
Yes, it might be a hardware-related issue. Could you provide me with the screenshot of VM settings?

1. What is the guest OS for that virtual machine? I am sorry to inform that you are not alone to face that issue (i.e., that's a known issue for Windows 10 1903).
2. Let me know if any of these fixes works:
https://answers.microsoft.com/en-us/win ... 0f0f5698af
https://www.reddit.com/r/HyperV/comment ... perv_host/

Hello Yaroslav,

maybe I should also mention that on the physical Win10 machine under the Hyper-V 2 more VMs run without problems. It runs a VM with Windows7 64bit and a Windows10 64bit.
All have the same settings. therefore it cannot be due to compatibility.

Now to your questions:
1. The VM has a Win7 64bit
2. None of these solutions help me

I am glad that I do not have this problem alone. There are a few pictures in the appendix.

Best Regards

2 more VMs run without problems.

Were they also converted with StarWind V2V Converter?
Could you do a P2V conversion again to see if the issue persists? It might be quite a long process, so leave the conversion overnight. It might be related to the hardware.
Please, share here anything you may find weird in StarWind V2V Converter outputs.

This might be off-topic, but I want to point that out. Your VM has 2 processors while your physical Intel I7 has 4 cores. Is there any way to try starting that VM on some other computer?

The information you share is very good and interesting, thanks to that, I know more useful things. Keep posting interesting things and I will keep an eye on your posts.

I did a P2V conversion and it worked again. Thank you very much.

You are always welcome.