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/
A new windows developer here. Excuse me for any mistakes!
We have a kernel mode driver which after a sequence of hibernate stress tests resulted in one of the driver module repeatedly loading and unloading.
The resulting error code on device manager is 38 - which according to MSDN is that driver prior unloading failed.
From the WPP logs, all modules seem to cleanup and unload properly. Not sure how to debug this problem
Also we have a crash dump collected after we see this error on driver. I can see the error node which failed to unload ( using the command - !devnode 0 1 or !pnptriage.)
Many other posts and articles suggest that this could point to leaked reference on Driver Object itself rather than simple memory leaks.
If turning on Object Reference Tracking is the way, how do I enable it for a particular driver ? Example only show for dll files or executables.
Appreciate any help. Thanks
|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!|
|Writing WDF Drivers||24 January 2022||Live, Online|
|Internals & Software Drivers||7 February 2022||Live, Online|
|Kernel Debugging||21 March 2022||Live, Online|
|Developing Minifilters||23 May 2022||Live, Online|