docbea...
There are several possibilities as far as resolving this problem.
Essentially the message is saying that some other process has the
memory at that location locked, thus making it unreadable, and
interfering with IE's shutdown process.
This possiblity is discussed in this post on Experts Exchange, by
sunray_2000, in the Accepted Answer:
"If this is happening predictably it could be:
1. a bad memory module.
2. A conflict with another dll or ocx control trying to compete
for the same memory area."
"If you have Dr Watson running and trapping errors, you can gain
some additional insight into what is happening at the 'moment of
impact'"
http://www.experts-exchange.com/Databases/MS_Access/Q_20809500.html
This article in the Microsoft Knowledge Base notes that the error
message you're receiving was a problem with IE 5.5 and earlier,
but this would not seem to apply to your situation. For the sake
of clarity though, are you using Microsoft's Java Virtual Machine,
or a Sun Java Virtual Machine? If you are still using Microsoft's
I would recommend uninstalling it and using the Sun machine, and
seeing if that makes a difference:
http://support.microsoft.com/default.aspx?scid=kb;en-us;189063
Another possibility is some form of malware, particularly one
which is interfering with your Winsock LSP stack. It would be
helpful if you could download HijackThis (HJT), run it on your
machine, and post the log back here so that I can see if this
might be the case. This sort of situation is documented on the
following thread, also at Experts Exchange, which also suggests
another way to isolate the program which is causing the conflict
with IE. You might want to try this before using Hijack This:
Go to:
"Start --> run --> Type in 'msconfig' and press 'Enter'
goto Startup tab
Disable all the applications there except anti-virus.
Reboot the machine and check if the issue continues.
If not, then enable one at a time in the same startup
tab and find the application or process that might cause
this at startup"
http://www.experts-exchange.com/Web/Browser_Issues/Q_21103256.html
HijackThis is available here, for free:
http://www.spywareinfo.com/~merijn/downloads.html
Due to the ambiguous nature of trying to fix computer
problems at a distance, please don't consider that your
question has been answered until the issue has been
resolved or we've done all we can.
Please do not rate this answer until you are satisfied that
the answer cannot be improved upon by way of a dialog
established through the "Request for Clarification" process.
sublime1-ga
Searches done, via Google:
"The instruction at" "referenced memory at" "The memory could not be read"
://www.google.com/search?q=%22The+instruction+at%22+%22referenced+memory+at%22++%22The+memory+could+not+be+read%22
"The instruction at" "referenced memory at" "The memory could not be
read" iexplore.exe
://www.google.com/search?q=%22The+instruction+at%22+%22referenced+memory+at%22++%22The+memory+could+not+be+read%22+iexplore.exe
"closing IE" "The instruction at" "referenced memory at" "The memory
could not be read" iexplore.exe
://www.google.com/search?q=%22closing+IE%22+%22The+instruction+at%22+%22referenced+memory+at%22++%22The+memory+could+not+be+read%22+iexplore.exe
Hijack This
://www.google.com/search?q=Hijack+This |
Clarification of Answer by
sublime1-ga
on
11 Sep 2005 19:57 PDT
docbea...
I'm pleased you found my answer thorough and instructive,
if not immediately practicable, and I'm glad the error
seems to have resolved itself.
As far as deleting the files you burnt to CD, I can't
see where there would be any connection with the way
IE shuts down, or that those files could create any
conflict with memory IE is attempting to access.
Since they are passive files, and not active files
such as executables like .dll and .ocx files, they
would not be accessing memory, and competing with IE
for memory, just by virtue of being on your hard
drive.
The same reasoning applies to files which were in
the Recycle Bin. I can see no likelihood of a file
in the trash bin maintaining any connection to
active memory.
I'd assess the disappearance of the error message
as a happy coincidence. Hopefully it will remain
absent, but if it should re-appear, the suggestions
I offered may yet prove useful.
Best regards...
sublime1-ga
|