Recommendations when investigating Windows BSOD issues

Red Hat supports components for virtualizing Windows guests, including virtio-win drivers and the qemu guest agent. However, for issues related to the Windows operating system, its configurations, and components, Microsoft support may be needed. If a Windows stop error (also known as BSOD) occurs on OpenShift Virtualization, Red Hat OpenStack Platform, or RHEL KVM, it is important to determine the issue's origin and the correct vendor to contact for diagnosis and resolution.

Recommendations to effectively troubleshoot Windows BSOD Issues

If you did not recently update your virtualization host or change the VM configuration, Red Hat recommends opening a support case with Microsoft for initial analysis. If this analysis indicates the virtio-win drivers or the hypervisor are the cause, please also open a support case with Red Hat, referencing the Microsoft support case number. However, if there are signs that the problem is related to the hypervisor or virtio-win drivers, Red Hat advises contacting Red Hat support first.

In some cases, Microsoft and Red Hat need to collaborate to resolve the issue. Note that in unclear or difficult-to-reproduce problems, this investigation may take time.

The following list provides examples of which vendor Red Hat recommends contacting first in the given circumstances:

When contacting Red Hat Support, please collect and provide the information described in How to collect information from Windows Guests to troubleshoot issues?.

List of recent known issues that cause BSODs

Please refer to List of known Windows BSOD issues on OpenShift Virtualization and RHEL KVM.