Explorer Application Error

[Guest]

I get the following error when opening a second IE window "how can I fix this?"

Thank you,


Explorer.exe - application error

The instruction 0x62c38167 referenced memory at 0x00000000. the memory could
not be read.

click on OK to terminate the program
click on cancel to debug the program

 

[Don Varnau]

Hi,

Another program is probably interfering with IE. From Control Panel>
Internet Options> Advanced> uncheck "Enable third party browser extensions."
With IE6 SP2, go to Tools> Manage add-ons and disable add-ons. If either of
those steps helps, you need to find the troublesome extension, BHO, add-on
or program and disable it. One of these programs may help:
BHODemon 2.0: http://www.definitivesolutions.com/bhodemon.htm
ToolbarCop: http://windowsxp.mvps.org/toolbarcop.htm

This may be a malware problem. Start by downloading and running CWShredder,
Ad-aware and Spybot. Check for updates before running Ad-aware or Spybot.
See: http://mvps.org/winhelp2002/unwanted.htm
Also note the security tips and other important information on that page.

Additional information at:
The Parasite Fight http://www.aumha.org/a/quickfix.htm
More security tips at http://www.aumha.org/a/parasite.htm
Bugs, Glitches & Stuffups: http://inetexplorer.mvps.org/darnit.html
What you can do about spyware and other unwanted software:
http://www.microsoft.com/athome/security/spyware/spywarewhat.mspx

If unsuccessful with those programs, you may have to post a HijackThis log
for analysis. Start at
http://forum.aumha.org/viewtopic.php?t=4075 Then go to
http://www.aumha.org/a/quickfix.htm Work through the preliminary cleaning
steps then post a HijackThis log to the forum at
http://forum.aumha.org/viewforum.php?f=30

Be patient. It's a busy forum.

HijackThis logs are also analyzed at these (and other) forums. Look for the
proper forum and an "Important- Read This First" message so that you follow
proper procedure.
http://castlecops.com/forums.html
http://tomcoyote.com/forums/
http://www.bleepingcomputer.com/forums/
http://forums.spywareinfo.com/
http://forum.iamnotageek.com/index.php
http://www.spywarewarrior.com/index.php
http://forums.maddoktor2.com/index.php
http://forums.net-integration.net/
http://temerc.com/phpBB2/
http://www.geekstogo.com/forum/index.php

Or...
A legitimate program running in the background may be causing this. Disable
(for diagnostic purposes) programs such as pop-up blockers, security,
anti-virus, etc. You may have to reinstall, or not reinstall, a program.

This (lengthy) troubleshooting process may help:
276393 - Understanding and Troubleshooting Unrecoverable Errors (Faults) in
Internet Explorer: http://support.microsoft.com/?kbid=276393

Hope this helps,
Don
[MS MVP- IE]

 

[Robert Aldwinckle]

I get the following error when opening a second IE window "how can I fix this?"

Thank you,


Explorer.exe - application error

The instruction 0x62c38167 referenced memory at 0x00000000.
the memory could not be read.

click on OK to terminate the program
click on cancel to debug the program

Are you getting the Error Reporting Tool's window too?

If so use the <click here> link and capture the Error Signature

Here is an excerpt from a previous reply about that:

<excerpt>
<title>KB276550 - Description and Availability of Internet Explorer Error Reporting Tool</title>

Once you get a crash click on the <click here> link.
Then drag your mouse over the text under the
Error Signature section title in the resulting message window.
Unfortunately you can't right-click on the selected text
but you can press Ctrl-c to copy it to the Clipboard.
</excerpt>


That would be the simplest way to find out which module
is involved in that crash (assuming it is an identifiable one.)
Alternatives would be to use the XP msinfo32 tool (but you
haven't disclosed your OS so I don't know if that is going
to be useful for you to know how to do that.) or (the most
complicated) to extract the crash context from a drwtsn32.log
(The format of you error message at least tells us that you
likely have some version of NT and that you haven't disabled
drwtsn32.exe.)

The crash context in the drwtsn32.log is also the most useful.
Here is an excerpt from another reply for a terse summary
of how to extract it:

<excerpt>
The location of the crash may not be as significant as the callers
at the time of the crash. If you have a drwtsn32.log look for a line
(e.g. from the bottom) which is prefixed by FAULT -> (assuming an
English version of Windows). The section which follows that is called
the Stack Back Trace and may contain clues about the callers.
Also, the section after that (the Raw Stack Dump) sometimes contains
readable strings in the interpreted portion (the drwtsn32 Help apparently
calls this ASCII data).
</excerpt>


Another diagnostic approach which could be useful is using
Process Explorer to show you the loaded .dlls just before the crash.
Sort the .dll display by Base (unfortunately It isn't a default column.)
and find whatever is loaded at 0x62C30000 (e.g.) FWIW I don't have
a module which loads there in my XPsp2 so I suspect you will find out
as Don said that it is a third-party module. Then either preventing it and
all other such modules from loading or simply removing it would change
your symptom.


HTH

Robert Aldwinckle
---