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'm looking at a crash dump. The location of the crash (an access violation) is where the driver is looking at the driver object's device object's device extension.
I'd like to examine these objects, but I can't find a way (after an hour of internet searching) to simply find them. I did use winobj to find the name I gave to the device object, but !devobj failed (Unable to get value of ObpRootDirectoryObject).
I'm in DriverUnload. Can I find the address of the driver object that it was called with?
Now I did finally find my Driver Object address as a parameter to the call to DriverUnload.
But I'm looking for the magic command that will display a device or driver object when all I know about my driver is the name "mydriver" from the file "mydriver.sys". Or even a command that will list all driver objects.
|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||30 Mar 2020||OSR Seminar Space|
|Developing Minifilters||15 Jun 2020||LIVE ONLINE|
|Writing WDF Drivers||22 June 2020||LIVE ONLINE|
|Internals & Software Drivers||28 Sept 2020||Dulles, VA|