Ways to anlayze crash dump files

When I get a BSOD, I use Visual SOFTICE and a Kernel memory dump to
try and trace the error.
If one of my driver's function is in the stack trace, I can goto its
source and try to find the error.

My problem starts when I don't see my driver in the stack trace, and
even when I disassemble "Parameter 4: Address of instruction
executing"
I can't see any of my driver's function.

Any way I can get more informant from the dump?
Does WinDbg can be more helpful in analyzing dump files ?
Any way to know if the win32 user mode app caused the crash? (Then I
need to use a complete memory dump?)
Any other tips on debugging BSODs?

Arkady
Thu Jun 30 09:33:06 CDT 2005

Yes , look WinDbg's Open Crash Dump... option in menu but if it will be
helpful that's the question :)
Additionally look at
http://support.microsoft.com/default.aspx?scid=kb;EN-US;314084
but that never worked for me
Arkady
P.S. How analize BSOD itself look at
http://support.microsoft.com/default.aspx?scid=kb;en-us;130802 ( that for
STOP 0x0000000A e.g. )


"Omer" <Omerb99@gmail.com> wrote in message
news:1120136669.197796.68090@g44g2000cwa.googlegroups.com...
> When I get a BSOD, I use Visual SOFTICE and a Kernel memory dump to
> try and trace the error.
> If one of my driver's function is in the stack trace, I can goto its
> source and try to find the error.
>
> My problem starts when I don't see my driver in the stack trace, and
> even when I disassemble "Parameter 4: Address of instruction
> executing"
> I can't see any of my driver's function.
>
> Any way I can get more informant from the dump?
> Does WinDbg can be more helpful in analyzing dump files ?
> Any way to know if the win32 user mode app caused the crash? (Then I
> need to use a complete memory dump?)
> Any other tips on debugging BSODs?
>