What were you trying to do that didn't work?
The upstream has a new issue, which tells us BSOD occurs when the driver is verified by verifier.exe. QE has reproduced it in the WS2016 with prewhql266.

Upstream issue: https://github.com/virtio-win/kvm-guest-drivers-windows/issues/1197

Please provide the package NVR for which bug is seen:

• virtio-win-prewhql-0.1-266
• kernel-5.14.0-524.el9.x86_64
• seabios-bin-1.16.3-2.el9.noarch
• swtpm-0.8.0-2.el9_4.x86_64
• qemu-kvm-core-9.1.0-1.el9.x86_64

How reproducible:
90%

Steps to reproduce
1. Boot a ws2016 guest with prewhql266
2. Run verifier.exe in the cmd.exe, then select the "Create custom settings (for code developers)" -> select all individual settings from the full list -> select the "netkvm.sys" driver.
3. Reboot

Expected results
No BSOD, pass through the driver verify.

Actual results
BSOD, an error code as "KMODE EXCEPTION NOT HANDLED."

Addition Notes
1. The memory dump file will be attached to this Jira issue for investigation.
2. Even do not choose the 'systematic low resources simulation' option. QE also encountered this problem two or three times.
3. It could not be reproduced by "verifier.exe /standard /driver netkvm.sys".