Who knows about windbg

[lbhskier37]

Please dont lock this, I have yet to find anyone in other forums that know anything about windbg and hope that someone in here knows how to use it.

Ok, I have been haveing bunches of driver errors and I finally decided to get windbg to look at the dump files. Here is part of the dump file:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: f888dac0, The address that the exception occurred at
Arg3: f8974c88, Exception Record Address
Arg4: f8974988, Context Record Address

Does anyone know how to find what driver that address is refering to using windbg?

 

[Peter]

It's all dynamic. You need to find out what driver is occupying that part of memory.

Usually windbg is useful when you're debugging your own driver while you're developping it - for troubleshooting a malfunctioning box or someone else's driver binary you'll find it rather useless.

 

[lbhskier37]

is there a way to find out what driver is in that part of the memory?

 

[Peter]

The bluescreen should tell you.

 

[lbhskier37]

do you know how I can find out what is in that memory address from the windbg program? I dont get bluescreens, but reboots.

 

[Peter]

Set XP to not reboot upon crash.