Wrox Programmer Forums
Go Back   Wrox Programmer Forums > Visual Basic > VB 6 Visual Basic 6 > Pro VB 6
|
Pro VB 6 For advanced Visual Basic coders working in version 6 (not .NET). Beginning-level questions will be redirected to other forums, including Beginning VB 6.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Pro VB 6 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old January 27th, 2005, 04:35 PM
Registered User
 
Join Date: Jan 2005
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default Visual Basic 6.0 - Application Error

Application popup: vb6.exe - Application Error : The instruction at "0x0043f08f" referenced memory at "0x608af85c". The memory could not be "read".


Its only happening when I m closing VB.

System Config
Windows 2000 Server
Visual Studio 6.0 SP6
Visual Studio .Net

Checked for all known virus which could do tht like blaster and sasser
 
Old February 4th, 2005, 03:15 PM
Authorized User
 
Join Date: May 2004
Posts: 83
Thanks: 0
Thanked 1 Time in 1 Post
Default

Hi miqbal,

The problem you've specified does occur due to errors in DLLs used by VB itself. A straight forward solution to this is to simply uninstall visual studio 6 or VB 6 (if you've only vb 6 installed), restart your computer and then reinstall visual studio 6. I am sure it will solve your problem.

Regards,


ejan
 
Old February 5th, 2006, 03:57 AM
Registered User
 
Join Date: Feb 2006
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via MSN to Rizzle-Q
Default

I get the same error except is is this:

"
Application popup: VB6.EXE - Application Error : The instruction at "0x0055d683" referenced memory at "0x00000000". The memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program
"

This doesn't happen when I close VB but instead when I RUN my application. This error pops up and I can't click on anywhere on my program.

I am running:
Windows 2000
Pentium 3, 450 MHz ~ 230 MB RAM
Visual Basic 6.0 Enterprise Edition (SP6)

This hasn't happened before and has only happened recently. I haven't used VB in a long time and this just happened now when I opened it. I have checked for viruses using AVG 7.1 Network Edition and I got nothing. I have tried to uninstall it and reinstall it and I get the same thing.

Any help!

Thanx in advance! :)
 
Old February 6th, 2006, 08:13 AM
Friend of Wrox
 
Join Date: Dec 2005
Posts: 132
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via MSN to nalla Send a message via Yahoo to nalla
Default


Hi,
I faced the same problem.
Uninstall VB. Do a registry clean and re-install worked for me. And install Sp6 also.


nalaka hewage
 
Old February 6th, 2006, 09:12 AM
Registered User
 
Join Date: Feb 2006
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via MSN to Rizzle-Q
Default

Ok. That sounds like a good idea. What do you recommend for a tool to clean the registry. I have Registry Mechanic 5.0...
 
Old February 6th, 2006, 04:07 PM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 627
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I do not think this is a registry or installation problem.

Usually the "memory cannot be read" is an error that cannot be changed into a VB error, and therefore cannot be trapped, and it is caused by a component that is not written in VB, or a bad call to a Windows API.
Things to look for: because the problem is on exiting the application, look for all the allocated resources, all API calls, third party components, database connections, etc. The problem is not in the Unload code: when the app exits, under the scenes VB tries to deallocate all resources, close file handles and database connections, disconnect to server atc. It is not easy to find. Usually what I do is to remove (or commenting out) parts of code, one oer time, until the error disappear

Good luck,
Marco
 
Old February 6th, 2006, 04:39 PM
Registered User
 
Join Date: Feb 2006
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via MSN to Rizzle-Q
Default

I see what you're saying about trying to isolate the problem but I don't even have any code! I can't comment anything out to even isolate the problem... I have just re-installed VB 6.0 and opened a new Standard EXE and just pressed the Run button without any code at all and that same error pops up.

I think I know what is causing this problem: I just recently installed DirectX for Visual Basic between using VB a while ago and now. The only problem is that I cannot un-install that DirectX so I think I am just going to re-format my computer. This will definately fix many things, lol.

I don't have many thing to backup anyways...

Thanks for all your help Marco, ejan, & nalaka hewage anyways. :)
 
Old March 6th, 2006, 10:54 AM
Registered User
 
Join Date: Mar 2006
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Has anyone figured this out yet? I am also getting a similiar error. My vb6 app. runs fine until I add a fourth crystal report to the app. It doesn't seem to matter which report is the fourth. Once the fourth is added I start getting this error:

"The instruction at 0x0f3051d8 referenced memory at 0x0f3df670. The momory could not be written."

This application worked fine with a total of 11 reports in it until we moved over to Active Directory and I had to change references to the servers within the app.

Running:
vb6 svcpk 5
win 2000 svcpk 4
active directory

Confused?
Read the Directions.
 
Old September 2nd, 2006, 01:54 AM
Registered User
 
Join Date: Sep 2006
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via ICQ to tekidum Send a message via Yahoo to tekidum
Default

Hi..i also face the same problem
this happen when i connect to smart reader and
write coding to retrieve data from reader..I use dll
to connect reader and vb...

when i run this form, msgbox will appears and said
"the instruction at "0X7c93426d" referenced memory at "0X00000000". The memory could not be "read".

and then my vb will be close.

sometime, this msgbox not appears but it also close my vb when I
run this form (send error or dont send)..

did someone can help with to handle this problem please??









Similar Threads
Thread Thread Starter Forum Replies Last Post
Visual Basic Express 2005 SQL error thomas38 Reporting Services 0 February 16th, 2006 02:53 PM
Visual basic excel application momowu0701 Beginning VB 6 1 December 15th, 2005 01:44 PM
Visual basic run time error. rushikesh_mistry Access VBA 2 October 22nd, 2004 07:05 AM
Beginning Visual Basic 6 Application Development kacheek All Other Wrox Books 1 March 7th, 2004 05:30 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.