Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
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/
|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!|
|Internals & Software Drivers||19-23 June 2023||Live, Online|
|Writing WDF Drivers||10-14 July 2023||Live, Online|
|Kernel Debugging||16-20 October 2023||Live, Online|
|Developing Minifilters||13-17 November 2023||Live, Online|
5.1.2240.1 ? (see previous messages for more info about this).
The error messages you mention are somewhat different than what comes out
in the current debugger (unless you reworded them)
It's normal to get erorrs about checksums and timestamps in certain cases.
win32k.sys and a number of other drivers are paged by the OS, and when you
crash we can't page in the image header to get this information. So you
get warnings about this when loading symbols - it just means the debugger
can not verify if it's loading the correct symbol file. But the symbols
should load fine if they are in the symbol path.
I have written a miniport driver for usb device on Windows 2000.
How do I use Windbg to debug my driver?
Please can anyone send me details information regarding on Debugging?
Thanks in advance,