Windows Server 2016 BSOD

[AndyDK]

Just installed Windows Server 2016 in ProxMox, but sometimes my Windows Server 2016 is making BSOD, with the following fail;

Stop code: IRQL GT ZERO AT SYSTEM SERVICE

and it is stuck on 84% then i need to make a "stop" in ProxMox.

Another BSOD is

Stop code: IRQL NOT LESS OR EQUAL

also this one is stuck on 85% and i need to make a "stop" in ProxMox and start the machine again.

Sometimes when i had to reboot Windows Server 2016 it won't restart, then it get stuck on "shutting down" screen, and i need to make a "stop" in ProxMox.

I tried to re-install and update Windows Server 2016 but nothing help.

(Right now it running on 2. day without making BSOD 7-9-13)

What is cause this problem, and how to solve it?

I've got a HP Microserver G8 with 4 GB RAM. 3 of them is dedicated to Windows Server 2016.

 

[fireon]

Please post the following information:

pveversion -v
qm config <vmid>
pveperf /your/storagepath/

What Virtiodrivers do you using? Did you you that video and this Thread?

 

[AndyDK]

qm config 100

balloon: 512
bootdisk: ide0
cores:2
ide0: local-lvm:vm-100-disk-1,size=50G
ide1ata-Lager:vm-100-disk-1,cache=directsync,size=700G
ide2: local:iso/n-msws16.iso,media=cdrom
memory: 3000
name: WindowsServerStandard
net0: e1000= =76:78:73:53:00:AF,bridge=vmbr0
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=f11c51c2-b26c-4899-81b2-3c3e3e215871
sockets: 1

 

[AndyDK]

I've just installed Virtio drivers, but when i restart the server then it frozen in "restarting" and i have to stop it in ProxMox... How do i fix this problem?

 

[Oliver R]

Hi!

Why do you use IDE for your Disks and e1000 instead of VirtIO? You should change your disks from ide to scsi and your network too virtIO.

 

[AndyDK]

Hi!

Why do you use IDE for your Disks and e1000 instead of VirtIO? You should change your disks from ide to scsi and your network too virtIO.

would that help on the problem?

 

[Oliver R]

would that help on the problem?

If you use the stable virtIO drivers. First you should post your output of

pveversion -v

 

[AndyDK]

okay here is the output;

corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.2-pve1~bpo90

 

[Oliver R]

Which kernel do you use atm?

 

[AndyDK]

Which kernel do you use atm?

Kernel?

 

[AndyDK]

I just installed a new server 2016 from the video guide, but this came with this fail; CRITICAL STRUCTURE CORRUPTION

 

[Oliver R]

Kernel?

 

[HBO]

Install and boot latest 4.10 Kernel:
https://forum.proxmox.com/threads/blue-screen-with-5-1.37664/page-7#post-188422

 

[AndyDK]

Install and boot latest 4.10 Kernel:
https://forum.proxmox.com/threads/blue-screen-with-5-1.37664/page-7#post-188422

should i downgrade ProxMox ?

 

[AndyDK]

 

[fireon]

should i downgrade ProxMox ?

No only the kernel.
Have here on 2 Clusters Server 2016 running with virtio-win-0.1.141.iso without problems. Latest PVE, latest Kernel. Important is scsi on HDD and virtio on NET. And disable bad memoryshareing for the first time. Better use memory hotplug.

 

[Maxemilian Hilbrand]

I have a similar issue...
it seems like this happened during backup.

The disks are running on a CEPH cluster (not proxmox), the backup location is using a different NIC than CEPH.

After a restart, the boot disk was not found anymore. This already happened four times with the same box, and it's disappointing. I cannot figure out what the problem is. I already tried to switch virtual disk technology (sata/virtio/scsi), I moved the disks to other storages (ceph, lvm, nfs,...) without success...

I have many similar configurations, but this is the only installation with those problems.

What can I do to troubleshoot this issue?