"_prefix" <prefix@discussions.microsoft.com> wrote in message
news

CFAAA75-AA2D-49B8-A94D-A6FAFFDEA692@microsoft.com...
> Faulting application name: iexplore.exe, version: 8.0.7600.16385, time
> stamp: 0x4a5bc69e
> Faulting module name: mshtml.dll, version: 8.0.7600.16535, time stamp:
> 0x4b83889f
> Exception code: 0xc0000005
> Fault offset: 0x001bc615
FWIW I had one of these recently. Same module and version. Offset:
0x003481f6
My only symptom was a message that IE had stopped and was being closed.
(Useless diagnostics.) I had to open Event viewer and wade through the new
ridiculously complicated and unusable W7 UI to find these details. (E.g.
try finding the filter dialog without having the "Console Tree" on. Why?)
After that I found out that some of the functionality that we used to have
in DrWtsn32 may still be available by tweaking the registry. E.g. hopefully
from now on I may be able to at least get a prompt advising me of a crash by
having changed DefaultConsent to 1 (from 3) in HKCU. And if necessary I
could even request a full local dump by adding the necessary subkeys and
values in HKLM. Both are options that DrWtsn32 made available to us
trivially.
I'm waiting for my next application crash to see if these ideas help me at
least get closer to a relevant Stack Back Trace by using ProcExp when I
get a prompt. With a DrWtsn32.log that detail used to be simple to get and
it seemed more relevant than the minimal diagnostics I am now aiming for in
W7.
Robert Aldwinckle
---