I've never used a .dmp before nor a traceback. right now (on the HP) I have searched and found the most recent .dmp (6-1-2011) and amazingly I got it to connect - a tiresome process not for the impatient). Im looking for a way to open the .dmp now.
Actually the dump will provide information on the faulting module that isn't otherwise available as well as a stack trace back. That in itself makes it easy to diagnose a bad driver versus a hardware error. The trace back also shows what code was in memory and executed recently. It is much more specific than simply recalling that text was being edited, an email client and a browser was also running.