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/
Hi all. Help me please. What is the best way to figure out the problem in the NDIS driver I developed. It works for a while, and after some non-fixed time a blue screen appears with different messages. I know that I have several problems. Since it works fine for a while, it means that something is happening all of a sudden. With Windbg, I can't resolve this issue due to the blue screen. I can periodically write some debugging information to the file and watch after reboot. I don't know. Is this method enough to get approximate problem locations. If so, how to create a debug file. Is NdisOpenFile suitable for this purpose. Thank you.
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 January 2023 | Live, Online |
Developing Minifilters | 20 March 2023 | Live, Online |
Internals & Software Drivers | 17 April 2023 | Live, Online |
Writing WDF Drivers | 22 May 2023 | Live, Online |
Comments
In fact, this will be your best path to resolve your problem as WinDbg has a bunch of helpful extensions to analyze your failure; especially if it's an NDIS device.
I recommend you read the following information regarding how to set up kernel debugging.
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/setting-up-kernel-mode-debugging-in-windbg--cdb--or-ntsd
thank you vary much