Getting famous bugcheck code 0xD1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KVM Guest Drivers for Windows |
New
|
Undecided
|
Unassigned |
Bug Description
When using the bus=virtio for my Windows 2019 Server VM, I am getting DRIVER_
The CD image I was using to install the driver was: virtio-
Unfortunately this also means I am unable to retrieve a dump of any kind for you, since that is being generated from the pagefile.sys at next boot.
The only thing I could attempt is to attach WinDbg if I find a way to forward a suitable port for debugging. But I think that would require some dabbling with the BCD which I'd have to perform offline (since, after all, the system isn't able to boot).
Alas, I guess it may be due to the age of the driver. After all there were three major Windows Server versions between if my count is correct (2012, 2012 R2, 2016).
Good news is, that the driver got accepted, even though (going by the date) it was created before Microsoft introduced attestation signing (as opposed to the old-style counter-signing) for drivers. But of course any newly built driver would become subject to attestation signing.
If you think there's any further information I can provide, please let me know.
The latest versions of this driver are only available to Ubuntu Advantage customers. I would probably suggest trying the openly available drivers from the Fedora project (which as far I can tell, is just a newer version of the same drivers published in this project - the commercial Ubuntu Advantage driver may be different, I am not sure): /docs.fedorapro ject.org/ en-US/quick- docs/creating- windows- virtual- machines- using-virtio- drivers/ index.html
https:/