Difference between revisions of "Microsoft KB Archive/171514"

From BetaArchive Wiki
(importing KB archive)
 
m (Text replacement - """ to """)
 
Line 53: Line 53:
 
<div class="errormessage">
 
<div class="errormessage">
  
&quot;Access Violation: Unhandled exception in VB5.EXE 0xC0000005: Access Violation&quot; (Windows NT4)
+
"Access Violation: Unhandled exception in VB5.EXE 0xC0000005: Access Violation" (Windows NT4)
  
 
</div>
 
</div>
Line 64: Line 64:
 
<div class="errormessage">
 
<div class="errormessage">
  
&quot;VB has caused an invalid page fault in module VB5.EXE at 0137:00419f1e&quot; (Windows 95, Windows 98, and Windows Me)
+
"VB has caused an invalid page fault in module VB5.EXE at 0137:00419f1e" (Windows 95, Windows 98, and Windows Me)
  
 
</div>
 
</div>

Latest revision as of 11:05, 21 July 2020

Knowledge Base


Article ID: 171514

Article Last Modified on 5/12/2003



APPLIES TO

  • Microsoft Visual Basic 5.0 Control Creation Edition
  • Microsoft Visual Basic 5.0 Learning Edition
  • Microsoft Visual Basic 6.0 Learning Edition
  • Microsoft Visual Basic 5.0 Professional Edition
  • Microsoft Visual Basic 6.0 Professional Edition
  • Microsoft Visual Basic 5.0 Enterprise Edition
  • Microsoft Visual Basic 6.0 Enterprise Edition



This article was previously published under Q171514

SYMPTOMS

Closing a modal form in the Visual Basic 5.0 design environment may cause one of the following errors:

"Access Violation: Unhandled exception in VB5.EXE 0xC0000005: Access Violation" (Windows NT4)

-or-


"VB has caused an invalid page fault in module VB5.EXE at 0137:00419f1e" (Windows 95, Windows 98, and Windows Me)

CAUSE

Visual Basic is trying to get the thread data from a control after it has been unloaded. The error code that signaled that the control got unloaded is not handled properly.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual Studio 97 Service Pack 2.

For more information on the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:

170365 : INFO: Visual Studio 97 Service Packs - What, Where, and Why


For a list of the Visual Basic 5.0 bugs that were fixed in the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:

171554 : INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2


MORE INFORMATION

The Threed32.ocx control shipped with Visual Basic 4.0 is required in order for this behavior to occur.

A sample that reproduces this behavior is not available because this behavior tends to occur sporadically, and usually only in large, complex projects.

Keywords: kbbug kbfix KB171514