Re: Right-click causes crash in OE 6

From: Robert Aldwinckle (robald_at_techemail.com)
Date: 09/17/04 

Date: Thu, 16 Sep 2004 21:53:08 -0400

"eddieb" <anonymous@discussions.microsoft.com> wrote in message
news:16c201c49c06$80b6ffb0$a401280a@phx.gbl...
> Thanks for your suggestions, Mike, I've been offline for a
> couple of days. There is no details button or link in the
> message box, but there is an error log in Dr. Watson that
> says:
> Application exception occurred:
> App: (pid=1580)
> When: 9/16/2004 @ 08:40:37.687
> Exception number: c0000005 (access violation)
>
> this is followed by several thread state dumps and stack
> back traces, etc.

Ed,

This summary unfortunately does not include anything useful.
The important information is the crash address and the name
of the module which contains that address. It is also useful
to know the version of the crashing module. A good way to
capture that information is with the Error Reporting Tool but
it looks as if you don't have that feature enabled on your system.

If you get the IE Error Reporting Tool window you can click
on the Click here button and capture the Error Signature on
the next window. Unfortunately this window is not shown in the
following article nor is the (arcane) method of capturing the Error
Signature given by the article. (Drag your mouse over the text and
and press Ctrl-c to copy the selected text to your ClipBoard.)

<title>KB276550 - Description and availability of Internet Explorer Error Reporting tool</title>

Apparently the procedure for activating that feature on your OS
requires a registry hack.

If you don't get that information that way you might be able to get it
by starting drwtsn32 or you may find an Event log entry in Event
Viewer's Application log. Either should give a better summary of
your crash than you have found so far.

However, since you have a drwtsn32.log the best details would
be the last FAULT -> line (for the crash address) and that task's
Stack Back Trace (maybe). A slight problem with that is that most
drwtsn32 logs that I have seen from your OS unfortunately never
seem to include module names anywhere in the standard dump.
For that reason I have suggested to such users that they check
the Dump Symbol Table option in the drwtsn32 options dialog.
It's not really a full Symbol Table (just external entry points) but
it is often enough to make some sense from an otherwise bare
Stack Back Trace.

HTH

Robert Aldwinckle 

---
>
> Yes, it occurs in all folders, not just the inbox.
>
> Thanks again,
>
> Ed
>
>>-----Original Message-----
>>It's important to know the Details.  When you get
> an "Illegal Operation" or  "encountered
>>a problem" message, there is usually a Details button (In
> WinME press Alt/D), or a "click
>>here" link to see the error report.  When you click on
> the button/link, it will give a
>>message like:  XXXX caused an error in YYYY and a bunch
> of register nonsense or it will
>>list the Appname XXXX and Modname YYYY.  The XXXX and
> YYYY are important to identify the
>>cause and solution.  You can ignore the rest of the
> message.
>>
>>MSIMN is the XXXX part.  The YYYY part will help narrow
> down the problem cause.
>>
>>Also, does that happen with any mail folder, or is it
> specific to one, such as the Inbox?
>>
>>-- 
>>
>>Mike -
> http://pages.prodigy.net/michael_santovec/techhelp.htm
>
Quantcast