Windows 7 - User-friendly: Analyzing your first BSoD!

Thank you guys!
This is what's keeps me motivated.

Sledge, I added your suggestion to the main post and the change-log. I was actually looking for something like this as you can't copy text from the Modules list.

Fred.

Great, now users only have to study further and gain experience in debugging crash dumps

In Windbg? Au contraire, my friend Try mark the modules in question with the mouse cursor and press CTRL-C. Now they should be in the paste-buffer and you can post them with CTRL -V. Tedious, I know but possible non the less.

-DG

Nice tutorial- very helpful


I am trying to learn the ins and outs of this as we speak.
I was wondering if you might be able to explain the above to me as I must be missing something here.

If I run the !analyze -v command it appears similar to a command line window. I then go back to the main GUI of the windbg program and click Debug Tab->Modules-> New window appears. From here, how do you arrange the items in date as you have mentioned and is it possible to determine from that output whether any of the drivers are indeed out of date and in need of updating - if so, how? Are the dates mentioned the driver release dates and one would simply find if there is a later driver through the appropriate search channel?

Thanks in advance.

The "crux" is that an outdated driver doesn't necessarily have to be a bad driver.
But you can safely assume that drivers which publishing date lies before the release of Windows 7 are outdated.
I use above mentioned code to get an output sorted alpha-numerical.

-DG

Windows OS Driver Base Timestamps - sysnative.com - MVP