"novice" <novice@discussions.microsoft.com> wrote...
> Thank you for your reply. The driver is intermediate NDIS driver developed
> by
> us. The original developer of this driver has left the job and I need to
> fix
> this issue. My question is:
> 1. How do I debug this and how to get additional information about the
> crash?
Hi novice,
This is not a job for novices!
You need to install the Windows Debugging Tools:
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
You'll also want the Windows Device Driver Kit:
http://www.microsoft.com/whdc/DevTools/WDK/WDKpkg.mspx
Hopefully your company already has access via an MSDN Subscription (trying
to write drivers without MSDN is, uh, difficult).
The key things you need to do:
- find the STOP error
- look up the STOP error in the DDK docs. Eg: was it a STOP 0x7C and if so,
what was the first paramer? And so on.
- get a memory dump of the STOP error (should be thrown, automatically).
- load up the dump in the WinDBG debugger
- examine the dump to see why the driver crashed.
The DDK docs are also available online. A good starting point would be:
Interpreting Bug Check Codes
http://msdn2.microsoft.com/en-us/library/ms789396.aspx
Apart from that ... well, kernel mode debugging is not something which can
be taught, via newsgroup support. You need an experienced mentor to sit down
with you for a couple of weeks and work through a few examples with you. If
you can't arrange that, try the Debug Resources page:
http://www.microsoft.com/whdc/devtools/debugging/resources.mspx
and I highly recommend anything produced by OSR:
http://www.osr.com/
A better newsgroup to try would be
microsoft.public.development.device.drivers.
Good luck with it!
--
Andrew McLaren
amclar (at) optusnet dot com dot au