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/
If you enable the two registry values specified in this MSDN topic, windbg will helpfully pause every time an exceptional condition is encountered in dxgkrnl, letting you choose how to proceed (break, break then repeat message, ignore, ignore all). This works great, and does allow me to see when errors have occurred, but it doesn't allow me to see what errors have occurred.
I can see the callstack (with public dxgkrnl symbols), which does provide some clues, but not nearly enough to understand what specifically the issue might be. I spent some time trying to poke around in the disassembly to see if I might be able to find a pointer to an actual message, but had no luck.
Is there any way to actually get at the log messages being reported here?
|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||16-20 October 2023||Live, Online|
|Developing Minifilters||13-17 November 2023||Live, Online|
|Internals & Software Drivers||4-8 Dec 2023||Live, Online|
|Writing WDF Drivers||10-14 July 2023||Live, Online|