VB6 caused an invalid page fault in module MSVBVM60.DLL at 014f:6604b3ce 
Author Message
 VB6 caused an invalid page fault in module MSVBVM60.DLL at 014f:6604b3ce

I am having some difficulty with an ActiveX control (.ocx) I have
written in VB6.  Often, when I have the control running on a form and I
close that form (or it's parent) I get the following crashes in
sucession (look below for the specifics of my environment):

==================================================
VB6 caused an invalid page fault in
module MSVBVM60.DLL at 014f:6604b3ce.
Registers:
EAX=00000000 CS=014f EIP=6604b3ce EFLGS=00010246
EBX=00000000 SS=0157 ESP=007ff554 EBP=007ff598
ECX=00000000 DS=0157 ESI=0230d994 FS=0dd7
EDX=00000000 ES=0157 EDI=00000000 GS=0000
Bytes at CS:EIP:
8b 08 ff 51 20 8b 76 20 57 56 8b 06 ff 50 28 33
Stack dump:
00000000 00000000 00000000 0177f5f8 0230d994
6604b369 0230d994 0230d994 6607cd66 0230d994
00000000 0177f5f8 0230d990 00415821 0230d884
0177f5f8

VB6 caused an invalid page fault in
module SSSCC.DLL at 014f:60567702.
Registers:
EAX=00000000 CS=014f EIP=60567702 EFLGS=00010246
EBX=60480000 SS=0157 ESP=0373fbe0 EBP=0373fc10
ECX=00000000 DS=0157 ESI=038607e0 FS=36c7
EDX=815bf1ac ES=0157 EDI=00000001 GS=2afe
Bytes at CS:EIP:
8b 71 04 85 f6 57 74 23 8b 7c 24 0c 33 d2 8b c7
Stack dump:
038607e0 6056b2c9 000002c4 60480000
00000001 038607e0 6056b12b 038607e0
038607e0 0373fc20 6058d804 00000000
0373fc2c 6057bcd9 038607e0 038607e0
==================================================

I attribute the second crash (SSSCC.DLL) to Source Safe.

Now if I run the same program on an NT machine I get the "the memory
could not be read" error, also when I attempt to close.

Here is my environment :
OS : Windows 95a (and Windows NT Workstation SP3)
VB : VB6 Enterprise SP2 with Source Safe 6.0 Integration

Project/Problem :
The control was written in VB and compiled.  I am not doing any wierd
things except maybe rather large arrays and using the DrawText API.  I
then drop the compiled control into another VB project (Standard EXE)
and sometimes (inconsistantly) when I close the form the control is on
(or it's parent form) it crashes.  This happens BOTH in the IDE as well
as when it is compiled.

Things I have tried (without success)
   - Compile in p-code instead of native code
   - Looked for references not set to Nothing
   - Removing the call to DrawText
   - Adding the control as a project in the project group
   - Applying SP2 (Our environment isn't suporting SP3 yet)

 Sorry about the length, but I wanted to cover all the bases.

Thank You,
Jason

----------------------------------------

- Programmer/Analyst                   -
- PPG Industries, Inc.                 -
----------------------------------------

Sent via Deja.com http://www.*-*-*.com/
Share what you know. Learn what you don't.



Tue, 13 Nov 2001 03:00:00 GMT  
 VB6 caused an invalid page fault in module MSVBVM60.DLL at 014f:6604b3ce
Here is a quick update.  For some reason this seems to prevent that
access violation from happening.  In the Form_Unload events of the
forms that contain this control, I set control.Visible = False and that
seems to prevent it from crashing...Who knows why!

Jason


Quote:

> I am having some difficulty with an ActiveX control (.ocx) I have
> written in VB6.  Often, when I have the control running on a form and
I
> close that form (or it's parent) I get the following crashes in
> sucession (look below for the specifics of my environment):

> ==================================================
> VB6 caused an invalid page fault in
> module MSVBVM60.DLL at 014f:6604b3ce.
> Registers:
> EAX=00000000 CS=014f EIP=6604b3ce EFLGS=00010246
> EBX=00000000 SS=0157 ESP=007ff554 EBP=007ff598
> ECX=00000000 DS=0157 ESI=0230d994 FS=0dd7
> EDX=00000000 ES=0157 EDI=00000000 GS=0000
> Bytes at CS:EIP:
> 8b 08 ff 51 20 8b 76 20 57 56 8b 06 ff 50 28 33
> Stack dump:
> 00000000 00000000 00000000 0177f5f8 0230d994
> 6604b369 0230d994 0230d994 6607cd66 0230d994
> 00000000 0177f5f8 0230d990 00415821 0230d884
> 0177f5f8

> VB6 caused an invalid page fault in
> module SSSCC.DLL at 014f:60567702.
> Registers:
> EAX=00000000 CS=014f EIP=60567702 EFLGS=00010246
> EBX=60480000 SS=0157 ESP=0373fbe0 EBP=0373fc10
> ECX=00000000 DS=0157 ESI=038607e0 FS=36c7
> EDX=815bf1ac ES=0157 EDI=00000001 GS=2afe
> Bytes at CS:EIP:
> 8b 71 04 85 f6 57 74 23 8b 7c 24 0c 33 d2 8b c7
> Stack dump:
> 038607e0 6056b2c9 000002c4 60480000
> 00000001 038607e0 6056b12b 038607e0
> 038607e0 0373fc20 6058d804 00000000
> 0373fc2c 6057bcd9 038607e0 038607e0
> ==================================================

> I attribute the second crash (SSSCC.DLL) to Source Safe.

> Now if I run the same program on an NT machine I get the "the memory
> could not be read" error, also when I attempt to close.

> Here is my environment :
> OS : Windows 95a (and Windows NT Workstation SP3)
> VB : VB6 Enterprise SP2 with Source Safe 6.0 Integration

> Project/Problem :
> The control was written in VB and compiled.  I am not doing any wierd
> things except maybe rather large arrays and using the DrawText API.  I
> then drop the compiled control into another VB project (Standard EXE)
> and sometimes (inconsistantly) when I close the form the control is on
> (or it's parent form) it crashes.  This happens BOTH in the IDE as
well
> as when it is compiled.

> Things I have tried (without success)
>    - Compile in p-code instead of native code
>    - Looked for references not set to Nothing
>    - Removing the call to DrawText
>    - Adding the control as a project in the project group
>    - Applying SP2 (Our environment isn't suporting SP3 yet)

>  Sorry about the length, but I wanted to cover all the bases.

> Thank You,
> Jason

> ----------------------------------------

> - Programmer/Analyst                   -
> - PPG Industries, Inc.                 -
> ----------------------------------------

> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.

--

----------------------------------------

- Programmer/Analyst                   -

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.



Sun, 18 Nov 2001 03:00:00 GMT  
 
 [ 2 post ] 

 Relevant Pages 

1. IEXPLORE caused an invalid page fault in module MSVBVM60.DLL

2. VB6 caused invalid page fault in module MSXBSE35.DLL

3. invalid page fault in module MSVBVM60.DLL

4. Invalid page fault in module MSVBVM60.DLL

5. MSACCESS caused an invalid page fault in module VBA332.DLL

6. MSACCESS caused an invalid page fault in module vba332.dll

7. Winword caused an invalid page fault in module VBE6.DLL

8. VB5 caused an invalid page fault in module KERNEL32.DLL

9. VB5 caused an invalid page fault in module KERNEL32.DLL

10. wscript caused invalid page fault in module msado15.dll

11. VB32 caused an invalid page fault in module V32.DLL

12. Faulting module MSVBVM60.DLL v6.0.97.82 causes application to crash

 

 
Powered by phpBB® Forum Software