×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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:
http://support.microsoft.com/kb/315263
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.
midrange.com
