J
Jeanne Hedge
I've been getting the following intermittent error messages from
IEXPLORE.EXE.
IEXPLORE.EXE Application Error
The instruction at "0x1001d10e" referenced memory at "0x00000004". The
memory could not be "read".
The only option presented by this pop-up window is to click an OK
button. When I do that the pop-up closes, then I immediately get a
2nd pop-up message:
IEXPLORE.EXE Application Error
The instruction at "0x77f57bd2" referenced memory at "0x02180010". The
memory could not be "read".
Again, the only option presented is to click an OK button. When I do
that both the pop-up and IE close.
This problem first appeared about a month ago (mid-October). It is
intermittent, the only commonality I can find is that when it happens
it happens when I close IE. I can't find any other common
circumstances, such as websites visited, etc.
I can (and have) immediately re-opened IE after getting it closed
after one of these "error events". It always works fine and I've never
gotten the error messages on closure of this "2nd run".
I have gotten the error messages when closing after having several IE
windows open at once, AND I've had several IE windows open at once and
NOT gotten the error messages on closure. I have also gotten the
error messages when closing after having only 1 IE window open, AND
I've had one IE window open and not gotten the error messages on
closure.
I am running Internet Explorer 6.0.2800.1106.xpsp2_gdr.040517-1325
(128 bit) on Windows XP Pro, SP-1 (SP-2 has never been installed).
Both are up-to-date with the patches and updates Windows Update says
it's supposed to have. Virus and spy/tracking "scumware" scans have
not identified anything (and the programs that run these scans are
up-to-date too). I'm not getting any BSODs. My paging file size is set
to the System Managed option.
I note that the IE version contains "sp2", but XP is not running SP2,
and wonder if it's related. I did install several updates via Windows
Update in mid-October (pre-problem) and also wonder if they could be
related: KB842773, KB841873, KB840215, KB839645, KB834707
This is more irritating than anything else, but I'd like to see it
resolved.
Regards,
Jeanne Hedge
IEXPLORE.EXE.
IEXPLORE.EXE Application Error
The instruction at "0x1001d10e" referenced memory at "0x00000004". The
memory could not be "read".
The only option presented by this pop-up window is to click an OK
button. When I do that the pop-up closes, then I immediately get a
2nd pop-up message:
IEXPLORE.EXE Application Error
The instruction at "0x77f57bd2" referenced memory at "0x02180010". The
memory could not be "read".
Again, the only option presented is to click an OK button. When I do
that both the pop-up and IE close.
This problem first appeared about a month ago (mid-October). It is
intermittent, the only commonality I can find is that when it happens
it happens when I close IE. I can't find any other common
circumstances, such as websites visited, etc.
I can (and have) immediately re-opened IE after getting it closed
after one of these "error events". It always works fine and I've never
gotten the error messages on closure of this "2nd run".
I have gotten the error messages when closing after having several IE
windows open at once, AND I've had several IE windows open at once and
NOT gotten the error messages on closure. I have also gotten the
error messages when closing after having only 1 IE window open, AND
I've had one IE window open and not gotten the error messages on
closure.
I am running Internet Explorer 6.0.2800.1106.xpsp2_gdr.040517-1325
(128 bit) on Windows XP Pro, SP-1 (SP-2 has never been installed).
Both are up-to-date with the patches and updates Windows Update says
it's supposed to have. Virus and spy/tracking "scumware" scans have
not identified anything (and the programs that run these scans are
up-to-date too). I'm not getting any BSODs. My paging file size is set
to the System Managed option.
I note that the IE version contains "sp2", but XP is not running SP2,
and wonder if it's related. I did install several updates via Windows
Update in mid-October (pre-problem) and also wonder if they could be
related: KB842773, KB841873, KB840215, KB839645, KB834707
This is more irritating than anything else, but I'd like to see it
resolved.
Regards,
Jeanne Hedge