"Access Violation in MSHTML" Error Message in Internet Explorer 5

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q245096

Expand all | Collapse all

SYMPTOMS

When you are using Internet Explorer 5 and you move between HTML "submit" buttons, you may receive a general protection (GP) fault error message similar to:

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

Click on OK to terminate the application
Click on CANCEL to debug the application

When you view the Dr. Watson log after this error occurs, the logged access violation may be similar to:

Application exception occurred:
App: exe\explorer.dbg (pid=134)
When: 12/12/1997 @ 23:19:42.27
Exception number: c0000005 (access violation)

Back to the top

CAUSE

Three conditions must exist for this behavior to occur:

The FORM tags overlap the TABLE tag.
The HTML FORM submit buttons are very close together.
You move the mouse pointer rapidly between the two buttons.

The following sample HTML code demonstrates the general improper tag format:

This sample code snippet reproduces the problem:

<HTML>
<HEAD>
<TITLE></TITLE>
</HEAD>
<BODY>
Problem:
<FORM>
<TABLE><TR><TD>
<INPUT TYPE="SUBMIT" NAME=Button1"></FORM></TD>
<TD>
<FORM>
<INPUT TYPE="SUBMIT" NAME=Button2">
</FORM>
</TD></TR>
</TABLE>
</BODY>
</HTML>

Back to the top

WORKAROUND

You can avoid this condition by moving the two buttons farther apart, or by placing the begin and end FORM tag outside of the begin TABLE and end TABLE tags or inside the TABLE tags.

Sample workaround:

This sample code snippet demonstrates the workaround in HTML:

<HTML>
<HEAD>
<TITLE></TITLE>
</HEAD>
<BODY>
Work around:
<TABLE><TR><TD>
<FORM><INPUT TYPE="SUBMIT" NAME=Button1"></FORM>
</TD>
<TD>
<FORM><INPUT TYPE="SUBMIT" NAME=Button2"></FORM>
</TD></TR>
</TABLE>
</BODY>
</HTML>

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This problem has been resolved in Internet Explorer 5.01.

Back to the top

MORE INFORMATION

This problem does not occur in Internet Explorer version 4.01.

Back to the top

APPLIES TO

Microsoft Internet Explorer 5.0

Back to the top

kbfix kbprb kbprogramming KB245096

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top