Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Explorer.EXE - Application Error ,memory could not be read

Jul 6, 2005 11:14PM PDT

Description:
Application popup: Explorer.EXE - Application Error : The instruction at "0x63638176" referenced memory at "0x00000130". The memory could not be "read".

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

This is the error i get when i close one of my Visual Basic Based Application evertime.
Please give me a solution

Discussion is locked

- Collapse -
I've done that.
Jul 6, 2005 11:25PM PDT

I also wrote some VB code that evoked such an error. It took me a few weeks to find the bug in my code.

Best of luck,

Bob

- Collapse -
hi bob
Jul 10, 2005 5:12PM PDT

but what was the error excatly about in the code?
was it with any API's used in code?

plz do tell me bob

bye
Ritesh

- Collapse -
In my case...
Jul 10, 2005 11:02PM PDT

It was creating objects but due to my blunder, it never destroyed the old ones. It was a program logic error.

Best of luck finding your issue which is unlikely to be what I did. In closing, some won't apply the latest Visual Studio and OS patches. Those kind get to suffer too.

Bob

- Collapse -
I am getting this same error using Windows XP
Jul 15, 2007 3:34AM PDT

Please let me know if you found a solution to your problem. I am getting this very same error. I am using the Dell 2400 with Windows XP. I have 768 MB of RAM with a 2.8 Pentium.

- Collapse -
"Visual Basic Based Application" ???
Jul 15, 2007 3:38AM PDT

It's possible your VB app has that same error. For me I had to walk through my code. But what VB app is doing this on your machine?

Bob

- Collapse -
Easy solution
Sep 4, 2007 12:06AM PDT

Hi! It seems that you have an Visaul Basic script problem.
Type regsvr32 vbscript.dll in run and you will be free of your "little Problem".

//Hakan