IE 6 Error on Browser Shutdown

[Guest]

I have an ASP.NET 1.1 applicaiton that causes an IE6 crash on shutdown with
an error message:

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

Click on OK to terminate the program.

This occurs only on certain client machines but not all. It only occurs
after certain sequences of application execution.

Any ideas on the cause and how to avoid?

 

[Guest]

I have a similar problem with IE 6. Everytime I close a browser window, I
get the following error message:

"The instruction at "0x7c901010" referenced memory at 0x0000001c." The
memory could not be read.

Click OK to terminate the program."

This has begun happening since I installed NetZero High Speed Platnum 3G
ver. 8.0 ISP software from CD a couple days ago on my Windows XP Home Edition
w/SP2 O/S Gateway PC.

No way to debug the program. What's up with that?

 

[Guest]

The addresses you report are privileged while the ones in my case are not.
Hopefully, we will hear from an IE guru on this.

 

[Guest]

Hiya, EagleRed,

Your reply indicates you know what the memory addresses signify--or am I
wrong? See, I have NO CLUE what those stupid numbers mean, so, if you do,
could you please tell me?

I just want to know how to fix the problem, and have become quite
puter-knowledgeable from necessity (reference my nickname!). The only thing
I don't know is what all the codes mean!

Any clue you can provide me would be greatly appreciated. Thanks!

 

[Guest]

I direct to a reference: Richter, Jeffrey "Advanced Windows", Third Edition,
Microsoft Press, 1997, pp. 115-121. (Actually Chapter 5 in the book). This
is a little dated and addresses NT not Windows 2000 operating systems and
later. This states which address ranges are privileged/reserved/restricted
and which are not. Unless things have changed the addresses you report are
not directly available to normal user programs. Note that the numbers are
hexidecimal (base 16) and not base 10 that we normally use.

Having said that I don't know what is going on here. I have opened a case
with MS support for my problem which seems at this point to be related to a
browser plug-in. Apparently there are a number of things that could be
happening and your case on the surface seems to be different from mine.
Because of the following.

1. The memory regions are privileged and mine are not.

2. In my case the instruction address and the referenced address are the
same which is bizarre. In your case the instruction address and the
referenced address are different.

How important is this to you? If no one in this newgroup can or will
address your issue, you may need to open a case with Microsoft support. This
could cost you $ depending upon whether you have some sort of support
arrangement.

Good luck!

 

[Robert Aldwinckle]

I have an ASP.NET 1.1 applicaiton that causes an IE6 crash on shutdown with
an error message:

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

I seem to recall that this symptom (branch to undefined address)
is usually caused by a module version compatibility.
E.g. some third-party program has been installed and downleveled
a common module (such as the MSVC Runtime, etc.)

You might be able to get some clues from the Stack Back Trace
and Raw Stack Dump of the crashing thread. E.g. browse drwtsn32.log
and in an English version of Windows find FAULT -> beside the crash
address then page down to those sections. The Raw Stack Dump
is only occasionally useful for interpreting readable strings that otherwise
only appear in hex.

Click on OK to terminate the program.

This occurs only on certain client machines but not all. It only occurs
after certain sequences of application execution.

Any ideas on the cause and how to avoid?

You need to get a more precise symptom description first. ; )


Good luck

Robert Aldwinckle
---

 

[Guest]

Thanks for the response. I opened a case with MS Support and we have traced
the issue to an Adobe Reader Helper plug-in. This is housed in the file,
AcroIEHelper.dll. I don't have the full details because we have to involve
Adobe. The plug-in is a COM server and it is behaving like there is a
pre-mature release of a COM object. The default behavior upon shutdown of an
application is for all COM clients to call Release() on the COM objects they
are referencing to avoid memory leaks. However, if there are errors in
maintaining the reference count that result in too many calls to Release, the
object will have been deleted and this error would occur. We can disable or
unregister the plug-in and the problem goes away. Both these actions require
action by a knowledgable user which often is not the case.

It does not appear that there is anything that I, as a developer, can do to
prevent this since it is occurring in client's browser. The only "hook" that
I might have would be in a javascript function. I am not real strong in
javascript. If someone knows of a way to check for this plug-in and do
something to turn it off, I would appreciate it.