Windows Server 2022 VM Crashing BSOD

2

2000gtacoma

Member
Aug 31, 2025
32
3
8
Running PVE 9.1 with ISCSI Dell ME4024

So it all started (I realize I probably should have left well enough alone, lesson learned), when I switched the disk type from scsi to virtio. Using virtio-scsi-single controller. At the time I had virtio .285 drivers installed. I've seen that .285 drivers can have issues with virtio. Had a few issues with BSOD, even corrupted a DC to the point I removed from the domain and built a new one. Was only running AD services and DNS so not a big deal. Loaded a fresh copy of server 22 with virtio .285 drivers. Had some blue screen issues, uninstalled .285 and installed .271 drivers. I also ended up changing the drive back to scsi. I'm still getting random crashes. Windows logs just show the system shut down unclean unless I should be looking elsewhere. What can I look at to narrow down this issue and pinpoint what the problem is. I've where windows may not have initialized the drivers correctly since the disk switch.

I don't feel like my backend storage is having issues as I have other VMs running on the 3 node cluster without issue. I also migrated the VM to another node to try to rule that out. My gut is telling me a driver issue related to the disk change. Just however don't know the best way to prove and correct the issue.
 
Hello everyone!

I'm experiencing the same issue with Windows Server 2022 on Proxmox VE 9.1.2.

I install Windows Server 2022 using a SCSI disk with the virtio-scsi-single controller. After the installation, I install the VirtIO network drivers and the QEMU Guest Agent.

At this point, everything works perfectly. I can change the disk bus from SCSI to VirtIO, change the network adapter type, add or remove additional virtual disks, and the VM remains fully functional.

However, as soon as I install the Active Directory Domain Services role and promote the server to a Domain Controller (this part is important), any subsequent hardware change in the VM configuration causes Windows to become unstable and crash with a BSOD.

For example, after the server has been promoted to a Domain Controller:

  • Changing the disk bus from SCSI to VirtIO causes the issue.
  • Changing the network adapter type causes the issue.
  • Any other hardware-related modification in the VM configuration appears to trigger the problem.

After the change, Windows reboots and reaches the login screen. However, immediately after entering the password, it crashes with a BSOD. The same thing happens when attempting to log in via RDP.

Booting into Safe Mode and removing the VirtIO drivers does not restore the system to a working state.

It seems there may be a bug or compatibility issue specifically involving the Domain Controller role and VirtIO drivers.

I have tested both VirtIO driver versions 0.1.285 and 0.1.271, with the same result.

Has anyone else encountered this issue or found a workaround?

P.S. Translated and edited with GPT. Don't kick me plz :)
 
You must log in or register to reply here.
Top Bottom
Back