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/
we have a product deployed to a large customer base. By large I mean half a billion large! Needless to say, a lot of crash dumps come our way, and they are mostly minidumps. Unless the crash point is self indicative and obvious, it is hard to track down the root cause in many cases.
Adding to those are the difficulties of acquiring all dumps from Microsoft, it is a complex process altogether.
I am trying to see, if there is a way to enhance the output of a minidump itself in case the crash is pointing to our driver. I am trying to find smarter ways to get more info dumped, will registering a bugcheck handler here help in any way?
|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!|
|Developing Minifilters||24 May 2021||Live, Online|
|Writing WDF Drivers||14 June 2021||Live, Online|
|Internals & Software Drivers||2 August 2021||Live, Online|
|Kernel Debugging||27 Sept 2021||Live, Online|