System Thread Exception Not Handled w/host cpu type selected (TR 2990WX)


New Member
May 24, 2019

I'm getting a BSOD immediately on install of Win10 if I use host for cpu type. I'm running pve 5.4-6 and a Win10 iso I pull/created from MS' tool w/in the last month.

My vm config is thus:
bios: ovmf
bootdisk: virtio0
cores: 4
cpu: host
efidisk0: local-lvm:vm-106-disk-1,size=4M
ide2: local:iso/Windows_10_32bit_and_64bit.iso,media=cdrom
machine: q35
memory: 8192
name: win10-pve05
net0: virtio=CE:C0:17:00:38:33,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=be4054ac-3a82-4400-9721-d24941aa788b
sockets: 1
vga: vmware
virtio0: local-lvm:vm-106-disk-0,size=150G
vmgenid: 38b34db8-2d6d-4b2b-8141-429a490a5e82

Again this BSOD (STOP) occurs right after the install attempts to load (right after pressing '...any key to boot off of CD or DVD' and then selecting Windows 10 Setup (64-bit). I've even tried safe mode, same issue.

If I change the cpu type to kvm64 I do not get this issue. I've searched around and haven't found this particular case before. I have seen a few threads where this BSOD occurs on existing/migrated VMs but safe mode works. Nothing for an at-install on a ThreadRipper.




The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!