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 dealing with a KMDF driver that I suspect has a memory leak in one of the WDF objects. I enabled the driver verifier for it, as well as the WDF verifier. The issue is that the driver in question does not seem to support unloading.
To test if the verifier can catch memory leaks when the OS is rebooting (and all the drivers are unloading) I wrote a small KMDF driver, introduced an intentional memory leak in it, enabled the verifier for that driver and tried to unload it manually. True to its form, the verifier then created a BSOD.
So I tried the same with my leaky driver but during the OS reboot. Unfortunately at that point, the verifier did not cause a BSOD.
Thus I'm wondering, if I need to do anything additional to enable verifier checks during the reboot?
Or, maybe there's a way to force a driver to unload?
Any other suggestions.
|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!
|13-17 May 2024
|1-5 Apr 2024
|Internals & Software Drivers
|11-15 Mar 2024
|Writing WDF Drivers
|20-24 May 2024