Blue screen with 5.1

cybermcm

Active Member
Aug 20, 2017
95
10
28
@wolfgang: thanks for the fast reply. So it seems that this is not the cause... well thanks again for your efforts looking into it...
 

talos

Active Member
Aug 9, 2015
63
8
28
@talos
please use the virtio 0.1.141 (current stable)
The 0.1.126 is know to be buggy with Win2016 and Win 10

I updated virtio drivers on two Windows 10 VMs and had no crashes so far. If this is really the solution i wonder what changed in qemu. I used 0.1.126 for a long time with Windows 2016 and Windows 10 without any issues.

So far it looks good.
 

cybermcm

Active Member
Aug 20, 2017
95
10
28
@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?
 

wolfgang

Proxmox Retired Staff
Retired Staff
Oct 1, 2014
6,496
498
103
@cybermcm
It is Host HW related. The Xeon-D as 'talos' use is not affected.
Thank to cpierr03 I can reproduce it on a E5 Hashwel CPU.
I'm have start bisecting the kernel, but i think it will take time because Windows need time to stuck.
And so it is hard to tell if the kernel work or not.
 

wolfgang

Proxmox Retired Staff
Retired Staff
Oct 1, 2014
6,496
498
103
I found a possible bug.

Pleas try to update the microcode of your Intel CPU.
A reboot is necessary.
The procedure would work as followed.

Code:
wget http://ftp.de.debian.org/debian/pool/non-free/i/intel-microcode/intel-microcode_3.20170707.1~deb9u1_amd64.deb
apt install iucode-tool
dpkg -i intel-microcode_3.20170707.1~deb9u1_amd64.deb
reboot

Please report back.
 
Last edited:

cybermcm

Active Member
Aug 20, 2017
95
10
28
Just updated the microcode, testing now -> keep my fingers crossed ;-) I'll report back
 

talos

Active Member
Aug 9, 2015
63
8
28
@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?

Here is the output of pnputil.

Code:
Microsoft PnP Utility

Published name :            oem3.inf
Driver package provider :   Red Hat, Inc.
Class :                     System devices
Driver date and version :   02/12/2017 100.74.104.13200
Signer name :               Red Hat, Inc.

Published name :            oem2.inf
Driver package provider :   Red Hat, Inc.
Class :                     System devices
Driver date and version :   07/19/2017 100.74.104.14100
Signer name :               Red Hat, Inc.

Published name :            oem5.inf
Driver package provider :   Red Hat, Inc.
Class :                     System devices
Driver date and version :   02/12/2017 100.74.104.13200
Signer name :               Red Hat, Inc.

Published name :            oem10.inf
Driver package provider :   Red Hat, Inc.
Class :                     Storage controllers
Driver date and version :   02/12/2017 100.74.104.13200
Signer name :               Red Hat, Inc.

Published name :            oem11.inf
Driver package provider :   Red Hat, Inc.
Class :                     System devices
Driver date and version :   02/12/2017 100.74.104.13200
Signer name :               Red Hat, Inc.

Published name :            oem15.inf
Driver package provider :   Red Hat, Inc.
Class :                     System devices
Driver date and version :   07/19/2017 100.74.104.14100
Signer name :               Red Hat, Inc.

Published name :            oem16.inf
Driver package provider :   Red Hat, Inc.
Class :                     Storage controllers
Driver date and version :   07/19/2017 100.74.104.14100
Signer name :               Red Hat, Inc.

Published name :            oem9.inf
Driver package provider :   Red Hat, Inc.
Class :                     Storage controllers
Driver date and version :   02/12/2017 100.74.104.13200
Signer name :               Red Hat, Inc.

Published name :            oem8.inf
Driver package provider :   Red Hat, Inc.
Class :                     Network adapters
Driver date and version :   02/12/2017 100.74.104.13200
Signer name :               Red Hat, Inc.

Published name :            oem0.inf
Driver package provider :   Red Hat, Inc.
Class :                     Network adapters
Driver date and version :   07/19/2017 100.74.104.14100
Signer name :               Red Hat, Inc.

Published name :            oem14.inf
Driver package provider :   Microsoft
Class :                     Printers
Driver date and version :   06/21/2006 10.0.16299.15
Signer name :               Microsoft Windows

Published name :            oem13.inf
Driver package provider :   Microsoft
Class :                     Printers
Driver date and version :   06/21/2006 10.0.16299.15
Signer name :               Microsoft Windows

Published name :            oem1.inf
Driver package provider :   Red Hat, Inc.
Class :                     Display adapters
Driver date and version :   05/28/2017 10.0.0.18000
Signer name :               Microsoft Windows Hardware Compatibility Publisher

Published name :            oem6.inf
Driver package provider :   Red Hat, Inc.
Class :                     Display adapters
Driver date and version :   12/08/2016 10.0.0.15000
Signer name :               Red Hat, Inc.

Published name :            oem4.inf
Driver package provider :   Cisco Systems
Class :                     Network adapters
Driver date and version :   02/26/2014 3.1.6019.0
Signer name :               Microsoft Windows Hardware Compatibility Publisher
 

cybermcm

Active Member
Aug 20, 2017
95
10
28
I did a full cleanup on the virtio drivers (uninstalled and removed old versions) and my servers ran for hours but then bluescreen again
C:\Windows\system32>pnputil -e
Microsoft PnP Utility

Published name : oem2.inf
Driver package provider : Red Hat, Inc.
Class : System devices
Driver date and version : 07/19/2017 100.74.104.14100
Signer name : Red Hat, Inc.

Published name : oem4.inf
Driver package provider : QEMU
Class : System devices
Driver date and version : 10/21/2016 1.0.0.0
Signer name : Red Hat, Inc.

Published name : oem3.inf
Driver package provider : Red Hat, Inc.
Class : System devices
Driver date and version : 07/19/2017 100.74.104.14100
Signer name : Red Hat, Inc.

Published name : oem8.inf
Driver package provider : Red Hat, Inc.
Class : Storage controllers
Driver date and version : 07/19/2017 100.74.104.14100
Signer name : Red Hat, Inc.

Published name : oem7.inf
Driver package provider : Red Hat, Inc.
Class : Network adapters
Driver date and version : 07/19/2017 100.74.104.14100
Signer name : Red Hat, Inc.

Published name : oem1.inf
Driver package provider : Microsoft
Class : Printers
Driver date and version : 06/21/2006 10.0.14393.0
Signer name : Microsoft Windows

Published name : oem0.inf
Driver package provider : Microsoft
Class : Printers
Driver date and version : 06/21/2006 10.0.14393.0
Signer name : Microsoft Windows
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 stable?
 

talos

Active Member
Aug 9, 2015
63
8
28
Yep, for me the new drivers solved my problems. All VMs with updated drivers still running. I startet some other unused VMs with older VirtIO and all of them crashes after some time. I think something changed in the Hypervisor and this change is not compatible with older VirtIO drivers, which worked fine in 5.0.
 

cybermcm

Active Member
Aug 20, 2017
95
10
28
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...
 

Lonnie

Active Member
Sep 16, 2014
67
6
28
Windows 2012 R2 on Proxmox 5.1-36:
2017-11-03_002_782x202.png


I'm currently trying to upgrade my Virtio drivers to see if that fixes the issue.
 
Last edited:
  • Like
Reactions: canove

biax

New Member
Aug 30, 2017
6
0
1
40
i dont know if this helps but i had similar issues with 5.0 (4.10 kernel) when i used cputype=default(kvm64)

after changing it to cputype=host... no further issues.

i didnt do kernel testing and so forth. is there any downside using cputype=host?
 

talos

Active Member
Aug 9, 2015
63
8
28
i dont know if this helps but i had similar issues with 5.0 (4.10 kernel) when i used cputype=default(kvm64)

after changing it to cputype=host... no further issues.

i didnt do kernel testing and so forth. is there any downside using cputype=host?

Host expose the whole CPU type and features to your VM. kvm64 is limited in feature flags and always show the same type to the VM. kvm64 is nice if you live migrate between hosts with different CPU types, it also helps not loosing windows activation because CPU Type, SMBIOS and stuff stays the same.
 

cybermcm

Active Member
Aug 20, 2017
95
10
28
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...
 

biax

New Member
Aug 30, 2017
6
0
1
40
Host expose the whole CPU type and features to your VM. kvm64 is limited in feature flags and always show the same type to the VM. kvm64 is nice if you live migrate between hosts with different CPU types, it also helps not loosing windows activation because CPU Type, SMBIOS and stuff stays the same.

understood, why choose kvm64 and not qemu64 then?
 

canove

Member
Jan 29, 2017
5
1
8
31
Same problem here, I'm running a Intel(R) Xeon(R) CPU E3-1220 v5 @ 3.00GHz with just one VM Windows Server 2012 R2. In my case, blue screen seems to just happen when system "stop" and "resume" to do the scheduled backup.

I'm changing CPU type to "host" now.

Thanks.
 

mac.linux.free

Active Member
Jan 29, 2017
223
18
38
46
perhaps it's still related to the multiqueue...please try this kernel option.. scsi_mod.use_blk_mq=n
 

canove

Member
Jan 29, 2017
5
1
8
31
@canove: Don't forget to update your VirtIO drivers, it seems that
this is also necessary...


I am already at virtio-0.1.141. Changing the CPU type doesn't work.

I installed the old kernel (4 4.10.17-3) and until now no more blue screen.

Thanks to tall.
 

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 your own in 60 seconds.

Buy now!