Hi,
I am not an an expert in debugging the windows driver for blue screens.
I would like to get a good understanding of how to analyze a dump file using !analyze -v command in windbg.
Can anybody point me in right direction, so that i can get good idea on the topic?
Nisheedh
A very basic tutorial on using windbg is available with installation of
Windbg. check the windbg installation folder for a word document. if you
want to read in general about debugging windows you must go for this book
http://www.amazon.com/Advanced-Debugging-Addison-Wesley-Microsoft-Technology/dp/0321374460/ref=sr_1_1?ie=UTF8&qid=1248419428&sr=8-1
search the archives of this forum, i m sure u will come across some more
sources
-rtshiva
On Fri, Jul 24, 2009 at 12:38 PM, wrote:
> Hi,
>
> I am not an an expert in debugging the windows driver for blue screens.
> I would like to get a good understanding of how to analyze a dump file
> using !analyze -v command in windbg.
>
> Can anybody point me in right direction, so that i can get good idea on the
> topic?
>
>
> Nisheedh
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> Can anybody point me in right direction, so that i can get good idea on
the topic?
I’ll give you the same response to someone else recently:
It’s definitely tough to get started. The problem is that in order to
successfully root cause Windows system crashes you first and foremost need
to understand both Windows and the architectures on which Windows runs. From
there, you need to learn to use the tools available to extract the
information necessary to find the cause. All of these are difficult and can
require significant ramp up time.
So, my recommendations for those getting started always include:
Read the Windows internals book several times (ISBN: 0735625301). This
will start to get you comfortable with the Windows architecture
The debugging package installs a tutorial that has good getting started
information (kernel_debugging_tutorial.doc). This will start to get you
comfortable with how to use the debugger.
In The Basics section on OSR Online we had a series a while ago titled
covers some common bugcheck codes and walks through how we solved examples
of them in the debugger, it might be helpful as a reference to those getting
started.
Practice. Debugging is self reinforcing, so the more you do it the better
you get. I always recommend telling your friends/family/significant other(s)
to enable crash dumps on their systems and send them to you whenever they
crash. It’s a good way to practice and if you figure it out you’ll be their
hero
Good luck!
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
wrote in message news:xxxxx@windbg…
> Hi,
>
> I am not an an expert in debugging the windows driver for blue screens.
> I would like to get a good understanding of how to analyze a dump file
> using !analyze -v command in windbg.
>
> Can anybody point me in right direction, so that i can get good idea on
> the topic?
>
>
> Nisheedh
>
In addition to what Snoone just said, you find excellent advice about specific problems at either or both of:
http://www.analyze-v.com
http://www.nynaeve.net
Good luck,
mm