Re: IE6 started to crash randomly

"MET" <MET@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F0DEC16A-571A-49DB-BC57-9B0C7DF79300@xxxxxxxxxxxxxxxx
Hi

"Robert Aldwinckle" wrote:

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.

Thank you. Yes that works on the window with the general error information,
unfortunately it doesn't work with the detailed eror information...


No but that isn't what you were having trouble copying anyway.

Supposedly there is a way to intercept that detailed information:
(I have never tried it.)

<title>KB310116 - How to disable or redirect Internet Explorer error reporting</title>




AppName: iexploreer.exe


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

Yes, it's a typo and not a malware

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

I tried this by using again the IE and a new crash. However, the data file
is so large that I wasn't able to locate the fault (with the new offset).


That is why I specifically hinted that if you were using a non-English
version of Windows you would have to use its localization of the word
FAULT. If you aren't sure how FAULT would translate in your language
see if there is a clue in the drwtsn32 help. E.g. Run... drwtsn32.exe
and then click on its Help link. When I do that the third Related Topics
article is Using the Dr. Watson log file. Scroll to the bottom of that
and see if you can figure out what the analogous keywords will be in your log.
Depending on how big your Help window is you may see it just above
some searchable text containing the words: stack back trace.
Press Ctrl-a to see all searchable text; otherwise it won't be clear that most
of the text in that page originates as graphic images. In fact, the line
I'm referring to is the only place where the string trace. occurs.
(I.e., the word trace suffixed by a period.)


Without being able to copy/paste this content of this detailed report and
being able to search for the place in the text file, I don't seem to have a
chance to find the corresponding place and to copy it here into a posting.
The saved text file doesn't contain the stack information. It really looks as
I have to get used now to an other browser....

MET


Good luck

Robert
---


.

Relevant Pages

  • Re: IE6 started to crash randomly
    ... find the last instance of FAULT -> prefixing a line which seems ... related to your crash signature's Offset. ... Then scroll down some more to find that task's Stack Back Trace. ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • [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)
  • Re: Stop Error: 0x0000007F (0x00000008,0x80042000,0x00000000,0x00000000)
    ... call to the handler for a prior exception. ... double fault. ... A kernel stack overflow. ... One of three types of problems occurred in kernel-mode: Hardware ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: XP crashing - system errors - details
    ... call to the handler for a prior exception. ... double fault. ... A kernel stack overflow. ... One of three types of problems occurred in kernel-mode: Hardware ...
    (microsoft.public.windowsxp.basics)
  • Re: [PATCH] i386: improve double fault handling
    ... Make the double fault handler use CPU-specific stacks. ... others' kernel stack is a theoretical possibility - but is handling it ... task gates are really a relic that should not be proliferated. ...
    (Linux-Kernel)