I already tried to set it to cputype=host, it didn't work, also bluescreen. @Lonnie: Please report back if updating virtio drivers changed something for you, didn't help me either...
great that it works for you. It seems that there are more or less two problems. Old drivers and some CPUs which won't work with 10/2016. I'll wait if wolfgang finds anything...
I did a full cleanup on the virtio drivers (uninstalled and removed old versions) and my servers ran for hours but then bluescreen again
It's really strange that this bug appears sometimes very fast after booting and sometimes hours later (without a visible cause).
@talos: is your system still...
@talos: that's interesting. I'm using 0.1.141 since I opened this thread and still experience bluescreens. Can you post the output of "pnputil -e" within your VM?
Just to be sure: One user claimed that it only happens with VM on a SSD drive. I've different servers with different CPUs running 5.1 and Server 2016 without issues. My problem "server" has a SSD drive. I've no clue how this can be connected but maybe other users have the same setup?
I didn't try to install it directly. You are right, my system is old but other users have the same issue with newer hardware so I think the problem is more or less important to solve.
Hi wolfgang,
First of all thank you that you look into it.
Windows version: Server 2016 core and standard GUI edition: 10.0.14393
Both have the same problem, the GUI version more often than the core version. There is no specific action to reproduce this but it happens within one hour after...
@fabian: Since I have the same problem (but coming from 5.0), is there a possibility to default boot the older kernel? Currently I've to intercept booting -> advanced -> boot old kernel. My changes to Grub didn't work (see post #7 above).
Is this a Proxmox or a kernel issue?