(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
---