BSOD 0x00001a Memory

P

paolone

Member
May 6, 2024
33
2
13
Hello

I've a Windows Server 2022 VM that in some night at 3.00 AM BSOD 0x00001a Memory.
No backup, no snapshot no particoular schedule at that hour.

I've Virtio 0.1285 it can be a problem?
Strange beacause the VM is here from 4 months and only in august 2026 are started the BSOD.
Do you have any suggestions ?

If I want to downgrade virtio 0.1285 to 0.1271 wich is the best practice ?

My best regards
 
hi,

yes there are some known issue with virtio-win 0.1.285, see PVE Wiki - Windows VirtIO Drivers.

Not sure if this is actually the root cause.
Could you please provide some more information about your setup so I can help you troubleshoot the issue:
  1. Your VM configuration: (make sure to replace the <vmid> placeholder with the actual id)
    Code: 
    cat /etc/pve/qemu-server/<vmid>.conf
  2. The version of PVE you are currently running:
    Code: 
    pveversion -v

Regarding downgrading the virtio-win drivers:
  1. Create a backup of your Virtual Guest
  2. Mount the older iso (virtio-win-0.1.271.iso)
  3. Open the Device Manager
  4. Look for the Storage Driver:
    Update Driver -> Browse for drivers -> Let me pick from a list of available drivers on my computer -> Have Disk... -> Browse -> Select the iso you mounted and navigate to the vioscsi\2k22\amd64 folder and install the drivers.
  5. Reboot the VM
 
Hello Driley

thanks for your answer:

Code: 
cat /etc/pve/qemu-server/103.conf

agent: 1
bios: ovmf
boot: order=scsi0
cores: 2
cpu: x86-64-v2-AES
efidisk0: sasvol:vm-103-disk-0,efitype=4m,size=1M
machine: pc-i440fx-10.1
memory: 16384
meta: creation-qemu=10.1.2,ctime=1775896392
name: SERVERNAME
net0: virtio=00:50:56:a2:c9:6b,bridge=vmbr0,tag=1
onboot: 1
ostype: win11
scsi0: ssdvol:vm-103-disk-0,cache=writeback,iothread=1,size=230G
scsi1: sasvol:vm-103-disk-1,cache=writeback,iothread=1,size=200G
scsihw: virtio-scsi-single
smbios1: uuid=42224941-f2c3-b93c-7987-6efbbba29356
sockets: 4
startup: up=30
vmgenid: 3bc17d8a-689e-448a-8a48-34120694329a


Code: 
pveversion -v
proxmox-ve: 9.2.0 (running kernel: 7.0.14-12-pve)
pve-manager: 9.2.10 (running version: 9.2.10/43df2e01f27a1a19)
proxmox-kernel-helper: 9.2.0
proxmox-kernel-7.0: 7.0.14-12
proxmox-kernel-7.0.14-12-pve-signed: 7.0.14-12
proxmox-kernel-6.17: 6.17.13-21
proxmox-kernel-6.17.13-21-pve-signed: 6.17.13-21
proxmox-kernel-6.17.4-2-pve-signed: 6.17.4-2
proxmox-kernel-6.17.2-1-pve-signed: 6.17.2-1
ceph-fuse: 19.2.3-pve4
corosync: 3.1.10-pve3
criu: 4.1.1-1
frr-pythontools: 10.6.1-1+pve3
ifupdown2: 3.3.0-1+pmx12
intel-microcode: 3.20251111.1~deb13u1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-7
libproxmox-acme-perl: 1.7.2
libproxmox-backup-qemu0: 2.0.2
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.1.1
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.1.6
libpve-cluster-perl: 9.1.6
libpve-common-perl: 9.2.1
libpve-guest-common-perl: 6.0.5
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.6.7
libpve-notify-perl: 9.1.6
libpve-rs-perl: 0.15.3
libpve-storage-perl: 9.1.8
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 7.0.0-2
lxcfs: 7.0.0-pve1
novnc-pve: 1.7.0-2
proxmox-backup-client: 4.2.5-1
proxmox-backup-file-restore: 4.2.5-1
proxmox-backup-restore-image: 1.0.0
proxmox-enterprise-support-keyring: 1.1
proxmox-firewall: 1.2.3
proxmox-kernel-helper: 9.2.0
proxmox-mail-forward: 1.0.3
proxmox-mini-journalreader: 1.7
proxmox-offline-mirror-helper: 0.7.4
proxmox-widget-toolkit: 5.2.7
pve-cluster: 9.1.6
pve-container: 6.1.13
pve-docs: 9.2.4
pve-edk2-firmware: 4.2025.05-3
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.5
pve-firmware: 3.18-5
pve-ha-manager: 5.2.5
pve-i18n: 3.10.0
pve-qemu-kvm: 11.0.3-2
pve-xtermjs: 6.0.0-2
qemu-server: 9.2.4
smartmontools: 7.5-pve2
spiceterm: 3.4.2
swtpm: 0.8.0+pve3
vncterm: 1.9.2
zfsutils-linux: 2.4.3-pve1
 
You must log in or register to reply here.
Top Bottom
Back