BSOD Win10 install

ogghi

Well-Known Member
Jan 27, 2017
33
2
48
36
Hey Guys,

I'm trying to install a Win10 pro (both from ISO and automatic deployment) and it fails at this:

Screenshot_2017-01-30_09-58-27.png

Any hints?
Sounds like memory or HDD, but even trying with a lot of different settings does not change.

Just before the BSOD I see this:

Screenshot_2017-01-30_10-23-06.png

Any ideas are very welcome!
 
also post your:

> pveversion -v

and your VM config:

> qm config VMID

and check your windows ISO, re-upload the ISO.
 
Hi tom, thanks for the answer.

Code:
pveversion -v
proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve)
pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e)
pve-kernel-4.4.35-1-pve: 4.4.35-76
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-101
pve-firmware: 1.1-10
libpve-common-perl: 4.0-83
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-70
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-9
pve-container: 1.0-88
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.6-2
lxcfs: 2.0.5-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80

Code:
qm config 102
boot: nc
bootdisk: sata0
cores: 8
cpu: host
memory: 16384
name: test-pxe
net0: e1000=F6:44:25:58:53:37,bridge=vmbr1
numa: 1
ostype: win10
sata0: pve1-ssd:102/vm-102-disk-1.qcow2,size=250G
scsihw: virtio-scsi-pci
smbios1: uuid=a7f29959-1f2c-4915-a88c-10f2e14fb542
sockets: 1
 
No ideas here on how to solve this?
Any input is highly appreciated :)
 
did you checked your windows ISO, re-upload the ISO?

upgrade to latest version, see:
https://pve.proxmox.com/wiki/Downlo...Proxmox_Virtual_Environment_4.x_to_latest_4.4

as windows is known to work, maybe a hardware issue on your side?

Best practice for windows, see my VM config:

Code:
root@pve-2-51:~# qm config 135

agent: 1
bootdisk: scsi0
cores: 6
ide0: iso-templates:iso/virtio-win-0.1.130.iso,media=cdrom,size=163080K
ide2: iso-templates:iso/SW_DVD5_WIN_ENT_10_1607_64BIT_English_MLF_X21-07102.ISO,media=cdrom
memory: 4096
name: win10
net0: virtio=CA:EC:4C:C5:26:E6,bridge=vmbr0
numa: 0
ostype: win10
scsi0: local-lvm:vm-135-disk-1,discard=on,size=32G
scsihw: virtio-scsi-pci
smbios1: uuid=c711b067-e5e1-4d61-90e9-dec7af65d80c
sockets: 1
 
Hi, thanks for the reply.
Just tried, it does not happen when booting from an ISO. It only happens when booting over PXE a custom win10 image.
So the issue might not be in Proxmox, or better, not only. This image boots and installs fine on a physical machine.
When I have a solution I'll let you guys know.
 
Follow up here:
It was caused by the AsIO.sys driver included in our custom image.
After removing that file from the image it worked just fine!
 

About

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!