Re: IE6 started to crash randomly

"MET" <MET@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:054DFEF7-34C7-415B-8F8B-05FB18E67AAC@xxxxxxxxxxxxxxxx
Hello Jon

A message informs that the program has to close. This occured now e.g. when
I wanted to open the links you provided or when I wanted to write this
answer. I have to do this now with an other browser...

Ok, I had now a closer look at the error message (mind you it would be
easier if one could copy/paste it):


You can. There is no right-click menu but you can select it
(e.g. either by dragging with the mouse or doubleclicking on a word
and pressing Ctrl-a) and then copy to ClipBoard it by pressing Ctrl-c.



AppName: iexploreer.exe


I hope this was a typo for iexplore.exe?
Otherwise you almost certainly would have a malware infection.


App ver: 6.0.2900.2180
ModName: shdocvw.dll
ModVer: 6.0.2900.2919
Offset: 0006d3cc

If I understand this correct, this shdocvw.dll seem to be the problem. What
is this dll?


It is one of the main components of IE. iexplore.exe is just a shell.
shdocvw.dll and mshtml.dll are the real meat of it.


What can I do? If it is of interest, I also could provide the
text file which goes with the error message; I saved it at one of the last
occasions.


More useful would probably be the Stack Back Trace
for the crashing task as captured by drwtsn32.log.
To find the appropriate SBT (in an English version of Windows)
find the last instance of FAULT -> prefixing a line which seems
related to your crash signature's Offset. E.g. it will probably
look something like this: FAULT -> 7776d3cc
Then scroll down some more to find that task's Stack Back Trace.



Thanks for helping.

Marcel


HTH

Robert Aldwinckle
---



.

Relevant Pages

  • Re: IE6 started to crash randomly
    ... More useful would probably be the Stack Back Trace ... find the last instance of FAULT -> prefixing a line which seems ... Depending on how big your Help window is you may see it just above ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • [crash] Re: [PATCH 1/3] tracing/function-graph-tracer: introduce __notrace_funcgraph to filt
    ... Thread overran stack, or stack corrupted ... Not yet verified on this CPU type. ... The following trace is a kernel self test and not a bug! ... # CAN Device Drivers ...
    (Linux-Kernel)
  • Re: [PATCH] ftrace: Documentation
    ... This is one of the options that change the trace itself. ... the fact that there is no comma before the `that' implies that the rest ... The irqsoff tracer tracks the time interrupts are disabled to the time ... +is with the interrupts stack which has that to be false. ...
    (Linux-Kernel)
  • Re: Msimn.exe Has Generated Errors and Will Be Closed by Windows - Knowledge base no help!!!
    ... It's not just any Stack Back Trace you want to see. ... section in the dump below those interpreted instructions. ... >>> and message rules may have to be edited to point to correct mail folders and you will lose all subscribed newsgroups. ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • [PATCH] spelling fixes: arch/x86_64/
    ... * @cpu: The CPU on which the event occured. ... inside the kernel. ... interrupt stack ... severe exception (double fault, nmi, stack fault, debug, mce) hardware stack ...
    (Linux-Kernel)