[SOLVED] Windows 10 21H1 turns itself off

[ayozeve]

I am experiencing an error with the latest version of Windows 10 21H1 (downloaded on Thursday). I have installed the machine with Virtio drivers (scsi, network, controller ...) And everything works fine, however after a while an error occurs in windows and the machine restarts alone and stays frozen.

I have to say that I have been using proxmox for years and that something similar had never happened to me.
When it happens to me it shows those messages just before (sorry that the system is in Spanish)




and:




On this machine it has the non-subscription version and pve-manager 7.0.13 but I have tested it on a machine with 6.4.4 and subscription and absolutely the same. Different types of disk drivers (virtio-block), different versions of windows (home and pro), with BIOS and UEFI ... Even with previous versions of the virtio drivers (the used at the beginning were 208-1 ... ) and remains the same. I am attaching screenshots of the Windows error to see if it could have happened to someone and they have solved it.

pveversion -v

proxmox-ve: 7.0-2 (running kernel: 5.11.22-5-pve)
pve-manager: 7.0-13 (running version: 7.0-13/7aa7e488)
pve-kernel-helper: 7.1-2
pve-kernel-5.11: 7.0-8
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.5-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve1
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-10
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-12
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.11-1
proxmox-backup-file-restore: 2.0.11-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.1-1
pve-docs: 7.0-5
pve-edk2-firmware: 3.20210831-1
pve-firewall: 4.2-4
pve-firmware: 3.3-2
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-16
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1

agent: 1
balloon: 0
bios: ovmf
boot: order=scsi0;ide2;net0
cores: 8
cpu: host
efidisk0: local-zfs:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide2: none,media=cdrom
machine: pc-q35-6.0
memory: 8192
name: Servidor
net0: virtio=62:2B:77:74:1F:FE,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win10
scsi0: local-zfs:vm-100-disk-1,size=420G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=2de576d0-c6e4-4a29-9a2e-2ce34587bc63
sockets: 1
vga: virtio
vmgenid: 8deacb36-f6d9-482b-a902-95ed540114da

 

[oguz]

hi,

On this machine it has the non-subscription version and pve-manager 7.0.13 but I have tested it on a machine with 6.4.4 and subscription and absolutely the same. Different types of disk drivers (virtio-block), different versions of windows (home and pro), with BIOS and UEFI ... Even with previous versions of the virtio drivers (the used at the beginning were 208-1 ... ) and remains the same. I am attaching screenshots of the Windows error to see if it could have happened to someone and they have solved it.

that's really weird if it doesn't work with neither version...

however after a while an error occurs in windows and the machine restarts alone and stays frozen.

how long does it usually take before the freeze happens?

what is configured on this VM? (which services running, how much workload on average, etc.)

do you see any other warnings or errors in the event log leading to the freeze?

 

[ayozeve]

hi,

that's really weird if it doesn't work with neither version...


how long does it usually take before the freeze happens?

what is configured on this VM? (which services running, how much workload on average, etc.)

do you see any other warnings or errors in the event log leading to the freeze?

Hello, a very silly bug, I needed to rest: D. I have installed many machines (always server versions) and in this case when installing a machine with windows 10 it was something as simple as not deactivating the system's hibernate option ... I was tired of trying and did not see what was in front of me.

However, it is not enough to leave it in case someone is like me to be clueless and that happens to him. Thank you very much and sorry for the inconvenience.

Regards

 

[oguz]

Hello, a very silly bug, I needed to rest: D. I have installed many machines (always server versions) and in this case when installing a machine with windows 10 it was something as simple as not deactivating the system's hibernate option ... I was tired of trying and did not see what was in front of me.

ah, that explains it

However, it is not enough to leave it in case someone is like me to be clueless and that happens to him. Thank you very much and sorry for the inconvenience.

thanks for posting the solution