The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
I am hitting a very strange problem with driver verifier. Here are the steps that I am following:-
Manual, Power-managed, PowerOn, Can accept, Can dispatch, ExecutionLevelDispatch, SynchronizationScopeNone
Number of driver owned requests: 0
Number of waiting requests: 1
!wdfrequest 0x000043f5b0ef1488 !irp 0xffffbc0a52497cb0
31: kd> !wdfrequest 0x000043f5b0ef1488
Treating handle as a KMDF handle!
This is a manual KMDF queue, which should be flushed automatically and all the requests in it should be cancelled by IoManager when the application is terminated.
Are we supposed to do something with these KMDF queues/requests when the application closes?
What are we missing here?
Any thoughts appreciated.
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!|
|Kernel Debugging||13-17 May 2024||Live, Online|
|Developing Minifilters||1-5 Apr 2024||Live, Online|
|Internals & Software Drivers||11-15 Mar 2024||Live, Online|
|Writing WDF Drivers||26 Feb - 1 Mar 2024||Live, Online|