Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.More Info on Driver Writing and Debugging
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/
Logging Trace Messages after Blue Screen
Is there anyway of logging trace event messages after a BSOD?
Howdy, Stranger!
| 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 |
Comments
I'm not sure, but I kind-of doubt it. Have you tried registering for one of the bugcheck callbacks and issuing a trace message request from there?
Peter
Peter Viscarola
OSR
@OSRDrivers
I found a workaround. As it is a DPC watchdog violation there is time from the computer freezing to the BSOD. Therefore I just run the trace viewer full screen and I can see what the last trace events are before the BSOD.
Hmmmm... But that's not logging trace event messages after a BSOD. That's simply "recalling the trace event messages that were generated BEFORE the BSOD"... and you can do that from the crash dump file, no?
In the end, all that matters is that you've gotten what you need!
Peter
Peter Viscarola
OSR
@OSRDrivers