darthf1

[VMM] BSOD on install

Recommended Posts

Hi all,

 

Specs:

DS3617xs with Juns loader

I3-7100

8GB DDR4

MSI B250i Gaming Pro AC

 

Im having troubles running Windows 10 on a VMM. I tried multiple versions, but they ultimately end in the same result:

  • When I boot the VM with Windows 1704 ISO (Creators update), I get instant BSOD so I can't even get to the installer
  • When I boot the VM with Windows 1607 ISO (Anniversery Update), I can get to the installer, load the Virtio HDD controller driver and the installation starts. When the VM reboots after installation I get the BSOD.
  • When I boot the VM with Windows 1507 ISO I can get through the install and boot into Windows without issues. Then I continued with installing the neccesary drivers. Then i started Windows update, and the upgrade to the latest Windows 10 has started. After the installation is finished I get a BSOD after first reboot.

 

The BSOD i'm getting is: Kmode_exception_not_handled. In the blue screen, there is nothing mentioned about a driver, so i'm not sure which driver triggers the BSOD. From the installation of the third bullet, I enabled the legacy boot menu and started Windows via Safe mode, but thats also giving me an instant BSOD. Disabling fast boot doesnt help either. I even tried all images above and incorporating the Virtio drivers in the image, but that doesnt help me either.

 

 

 

 

 

 

Edited by darthf1

Share this post


Link to post
Share on other sites

I couldn't even get it to install before it BSOD on my G4620 build.  Win 7 works

Edited by toastboy

Share this post


Link to post
Share on other sites

I'm having the same problem with Windows 10, same for server 2016.

Windows 7 seems to work.

Edited by MBchristoff

Share this post


Link to post
Share on other sites

It seems this issue is related to the CPU mode with Win2016 and Win10 on KVM. (Synology uses KVM underneath).

You can check the current CPU config when you login e.g. via SSH, then identify a (running) VM with virsh list and virsh dumpxml <ID>.

My vCPU were on "passthrough". I temporarily solved this issue by joining the VMM Pro Beta Program (under License) and then activating the CPU Compatibility Mode (VMM Pro only) for this VM - this sets the CPU Fallback to core2duo, which works fine for me (Win2016 and Win10).

 

KR,

lousek

Share this post


Link to post
Share on other sites

I have the same problem. In the log file you can see following error:

 

 

Share this post


Link to post
Share on other sites

For the time being I went back to using phpvirtualbox. I wish to use vmm though for my main NAS its nog viable if I can't use Windows 10 and Server 2016.

I'll test vmm when there is an update available on another system so at this moment I am not actively searching for a solution.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now