On Tue, Apr 27, 2010 at 16:01, Norm Dennis <nhdennis@xxxxxxxxxxx> wrote:
Unfortunately, I have always had difficulty interpreting it.
Hopefully Lucas will shed some light ;-)

Here's a quick guide from Microsoft on this issue:

Basically, you analyze the file using windbg and the Microsoft
symbols. If one were a developer that's knowledgeable about Windows
internals, one could exactly find out what the issue is.

I don't. Basically, i look at the backtrace and start guessing who's
at fault, starting with the Vendors i don't like. This has worked
surprisingly well in the past.

However, the issues i see with Jeff's crashdumps is the fact that we
have three different crashes. This makes it more likely to be a
hardware fault than a software, however things can be complicated.

My next approach would be to uninstall the two programs related to the
DLLs in the two crashdumps, and see if the problem happens again.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.