Search results
-
C
Blue screen with 5.1
pve-kernel-4.10.17-5 works well. FWIW, the problem was MOST pronounced on ZFS drives with the 4.13 kernel. As in, Windows was seldom able to boot without BSODs. The error occurred on my XFS drive as well, but only a handful of times, and performance seemed to be the same. On ZFS drives with...- cpierr03
- Post #102
- Forum: Proxmox VE: Installation and configuration
-
C
Blue screen with 5.1
Xeon E5-2683-V3 (Haswell) i5 machine is a Core i5-3470 (Ivy Bridge)- cpierr03
- Post #58
- Forum: Proxmox VE: Installation and configuration
-
C
Blue screen with 5.1
This is on a clean Win 10 1709 build with nothing but stable VirtIO drivers installed and the only KB available for this platform: KB4043961. The image came from Microsoft and is SHA1 verified. Really don't think this is a Windows problem here, as others have booted the 4.10 kernel and had no...- cpierr03
- Post #55
- Forum: Proxmox VE: Installation and configuration
-
C
Blue screen with 5.1
Can confirm I also have this bug on two machines running PVE 5.1 One Xeon E5-2683 V3, one i5-3470. Only Windows VMs crash, BSOD is CRITICAL_STRUCTURE_CORRUPTION. All VMs are using VirtIO devices/drivers, and are using the host CPU config.- cpierr03
- Post #46
- Forum: Proxmox VE: Installation and configuration