Error while logging off (ref: 0x77f83aed)

  • Thread starter Thread starter Bill Woods
  • Start date Start date
B

Bill Woods

While logging off one signon session of WinXP+SP1, I got the
following message:

EXPLORER.EXE - Application Error. The instruction at 0x77f83aed
referenced memory at 0x00000067. The memory could not be "written".

Does this mean I have bad system memory? Or is Explorer likely to be
at fault?

What should I do?
 
Hi,
Does this mean I have bad system memory?

No, it means that something tried to write to a protected memory address.
Or is Explorer likely to be at fault?

If it happened just once, it's probably just a glitch and may be nothing to
worry about. If it happens every time, then it's some program that is
loading at logon and is running in resident memory. Logging off terminates
the application, and this process is causing the error, and this is
frequently caused by the installation of spy or add programs into the
explorer shell. These can help:

Adaware www.lavasoft.de
Spybot www.safer-networking.org

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org
 
Good morning,

I've also had this same problem logging off from Internet Explorer 6, which
was discussed earlier in this group - Subject is: IEXPLORE.EXE Application
Error? It happens when I close IE - not when I try to log off from the
computer - but I get a similar message: "The instruction at "0x0125a584"
referenced memory at "0x0125a584". The memory could not be "read". Click on
OK to terminate the program."

It doesn't happen all the time, but occasionally - and it seems, since
downloading the latest Security Updates from Microsoft. I know it never
happened before that. I've been trying to find some correlation between what
I'm doing while browsing such as opening a PDF or a Word Doc, but I can't
replicate the problem.

I run AdAware frequently and have never found any spyware, and as advised in
the other thread, I added Win Patrol yesterday and I don't see anything
"strange" added to my start-up or running.

Does anyone else have this error who has recently downloaded MS Updates
since I'm thinking that may be something to do with the problem?

Any other ideas would be helpful.

Thanks!

TN
 
TN
Yes, I am having the exact same problem which did not occurr until my hard
disk crashed whereupon it was completely re-formatted and an all new install
placed on the computer including all latest updates from microsoft. The
message only occurs upon closing IE or Mozilla Firefox browsers. I have
updated Spybot and tried Java update as suggested in another post all without
correction of the problem.
 
Yes! That's exactly why I came here. I'm having this problem VERY
frequently -- almost every time I close an IE browser window. Sometimes
the problem is simply an application error in IE ; sometimes it is with
something called "Acrobat IE Helper" (I have the most recent version of
Acrobat Reader installed, as well).

I, too, run Spybot frequently, and have McAfee Online Service, and can't
find any spyware.

In addition, I'm having this extreme frustration because with many sites
that have javascript popup windows (not adware -- these are windows that I
want to see!), closing the pop-up window causes IE to crash -- and it takes
every connected window with it (meaning, if I went to a site because of a
message in Hotmail, then the browser windows with Hotmail, the target site,
and the popup will all close simultaneously). Sometimes this also brings
up the error message noted above.

I searched the knowledge base, and could not find a satsifactory answer --
everything that was even close was not written from a user perspective. I
do not know the date this started, but it is recent (within the last month),
and I, too, suspect recent updates.

I've tried different settings within IE Tools, to no avail.

I really wish someone would figure this out -- it's driving me nuts!

Jan
 
Iexplorer.exe is spyware. The Microsoft program is iexplore.exe

First eliminate any spyware.
What You Should Know About Spyware
http://www.microsoft.com/athome/security/spyware/devioussoftware.mspx

CAUTION!!!!! Removing some spyware can damage the Winsock stact. Before
you try to remove spyware using any of these programs , download a copy of
LSP-Fix - a free program to repair damaged Winsock 2 stacks (all Windows
versions)
http://www.cexx.org/lspfix.htm
Winsockfix for W95, W98, ME, NT, 2000, XP
http://www.tacktech.com/pub/winsockfix/WinsockFix.zip
Directions here: http://www.tacktech.com/display.cfm?ttid=257
WinXP:
Get WinSockxpFix
http://www.spychecker.com/program/winsockxpfix.html
How to Reset Internet Protocol (TCP/IP) in Windows XP
http://support.microsoft.com/kb/299357
In WinXP SP2: You can fix Winsock by going to Start | Run and typing
CMD
In the command window type
netsh winsock reset

See
Dealing with Unwanted Malware, Parasites, Toolbars and Search Engines
http://mvps.org/winhelp2002/unwanted.htm

Note that AdAware and SpyBot S & D will each catch some things the other
won't. Also, each needs to be updated with the program's update function
before every use, even when just downloaded. There's also a lot more to do
than just those two programs. CWShredder is also available here:
http://www.intermute.com/products/cwshredder
**Post your HijackThis log to
http://forums.spywareinfo.com/
http://forums.tomcoyote.org/
http://castlecops.com/forum67.html
http://www.wilderssecurity.com/ or the Spyware forum at
http://forum.aumha.org/viewforum.php?f=30 for expert analysis, not here.**
Alternative download pages for Ad-Aware, Spybot, HijackThis and CWShredder
may be found on this page:
http://aumha.org/a/parasite.htm.

See this link for information about malware:
http://arstechnica.com/articles/paedia/malware.ars

If nothing there helps, please post back to this thread.

--
Frank Saunders, MS-MVP, IE/OE
Please respond in Newsgroup. Do not send email
http://www.fjsmjs.com
Protect your PC
http://www.microsoft.com/security/protect/
 
Okay - I did a bit more checking and when I searched the KB for these terms
I came to this page:
http://support.microsoft.com/default.aspx?scid=kb;en-us;189063

It says in part:
SYMPTOMS
A complex serialization scheme when used from Internet Explorer causes
Internet Explorer to stop when exiting. Internet Explorer stops with a
dialog box that reports:

Iexplore.exe - Application Error

The instruction at "0xSomeAddr" referenced memory at "0xOthrAddr". The
memory could not be "read".

This sure sounds like the same problem, although it was supposed to be
corrected in IE 4 - doesn't even list IE 6 as affected, but this seems to be
the same thing. Any other ideas or suggestions?

TN
 
(posted from ie6.browser)

....
....

Okay - I did a bit more checking and when I searched the KB for these terms
I came to this page:
http://support.microsoft.com/default.aspx?scid=kb;en-us;189063

It says in part: ....
The instruction at "0xSomeAddr" referenced memory at "0xOthrAddr". The
memory could not be "read".
....


TNorth,

You would help your own cause more to follow-up in your own thread
with Don Varnau's suggestions:

http://www.microsoft.com/windows/ie...wser&mid=5bc2b21d-f2d9-4e38-8b52-61947b6a4e20

Your problem is almost certainly going to be caused by an incompatible
third-party program. Since you don't have XPsp2 you can't use
its new Manage Add-Ons facility. Therefore you either have to test
by disabling *all* BHO, e.g., by unchecking (in Options, Advanced tab)
Enable third-party browser extensions (requires restart)
<title>KB298931 - How to Disable Third-Party Tool Bands and Browser Helper Objects</title>

OR you need to download and use a tool such BHODemon, as Don
suggested to you.


BTW your symptom is quite different from the problem that Bill Woods (OP)
is reporting. Besides not even being about the same program or the same
circumstance, your crash address and operand address are the same.
In fact your crash address is invalid. That's why they are the same.
IIRC this has been a common symptom of incompatibility for a range of
third-party programs. Unfortunately I can't recall which ones they were
specifically except to note that I don't think that they were necessarily
malware.

I suspect most of the confusion is the cross-posting started by this thread.
OP probably is reading in windowsxp.general and added on ie6.browser
as an afterthought. The original post really has nothing to do with IE6
but by trying to continue your discussion in it you are causing what may be
perceived as an off-topic subthread to continue in those XP newsgroups.


HTH

Robert Aldwinckle
---
 
On Wed 18 May 2005 17:57:12, Robert Aldwinckle wrote:
I suspect most of the confusion is the cross-posting started by
this thread. OP probably is reading in windowsxp.general and
added on ie6.browser as an afterthought.

Hi Robert, I am the OP. I started this thread by crossposting my
original post to all three newsgroups
The original post
really has nothing to do with IE6 but by trying to continue
your discussion in it you are causing what may be perceived as
an off-topic subthread to continue in those XP newsgroups.

I included the IE6 newsgroup because (as I understand it and I may
well be wrong) Internet Explorer and Windows Explorer are different
front ends for essentially same thing.

So I figured that if I got this problem reported from Win Explorer
then those who had encountered it on IE6 might be able to offer some
very relevant advice.
 
Back
Top