Download the latest WinDbg … version 1.00.0006.0. It works quite well.
Try doing
!drvobj yourdriver
dt _DRIVER_OBJECT
Gary
-----Original Message-----
From: Smith, Joel [mailto:xxxxx@ntpsoftware.com]
Sent: Thursday, November 09, 2000 12:30 PM
To: NT Developers Interest List
Subject: [ntdev] There’s got to be an easy way to do this… getting
_DRIVER_OBJE CTs from a crash dump using WinDbg
I wasting a lot of time trying to get the _DRIVER_OBJECT that were
in memory at the time of a system crash using WinDbg (analyzing a crash dump
file). The !drivers command lists some information, but I’m trying to get
my actual _DRIVER_OBJECT as it existed at the time of the crash. Can
someone explain how I should go about doing this?
Also, the version of WinDbg (version 5.0 build 2195) crashes quite
often. Is this normal or is it more likely there is some sort of
environmental thing with my system that is causing WindDbg to be unstable?
Thanks,
Joel