Home All Groups Group Topic Archive Search About

Error: memory at "0x00000003"

Author
20 Jul 2006 2:29 PM
ciccio erisud
Hi all,
I recived the following error:

The instruction at "0x00000003" referenced memory at "0x00000003".
The memory could not be "read"
Click on OK to terminate the program

How can I fix it ?
Could you say me somethings ?
Thanks in advance.
//Luca

Author
20 Jul 2006 2:38 PM
Barry Kelly
ciccio erisud <ciccioeri***@discussions.microsoft.com> wrote:

> The instruction at "0x00000003" referenced memory at "0x00000003".
> The memory could not be "read"
> Click on OK to terminate the program

Did you get this in a program you wrote yourself? Or in the IDE? Can you
give more information?

-- Barry

Author
21 Jul 2006 7:54 AM
ldHH
Hi Barry,
Thank you for your help,
This program is started from a "scheduling application"
It doesn't have a graphic interface and it use an SQL Database.
The very strange thing is that I installed it on 5 machines;
On 3 machines the application work well, and on 2 machines the
application failed every 2/3 day (!).... with the error in subject

[Application info]
App. C# ... start at least 1 thread (max 3)
Read/Write on SQL Server.
"Speak" with a C++ application throught a C++ wrapper.

Thank you very much.
//Luca



Show quote
"Barry Kelly" wrote:

> ciccio erisud <ciccioeri***@discussions.microsoft.com> wrote:
>
> > The instruction at "0x00000003" referenced memory at "0x00000003".
> > The memory could not be "read"
> > Click on OK to terminate the program
>
> Did you get this in a program you wrote yourself? Or in the IDE? Can you
> give more information?
>
> -- Barry
>
> --
> http://barrkel.blogspot.com/
>
Author
21 Jul 2006 9:48 AM
Barry Kelly
ldHH <l***@discussions.microsoft.com> wrote:

> > > The instruction at "0x00000003" referenced memory at "0x00000003".
> > > The memory could not be "read"
> > > Click on OK to terminate the program

> "Speak" with a C++ application throught a C++ wrapper.

If I had to guess, I would say that the C++ application / wrapper is
running into something unexpected, and that's causing the error.
However, it's impossible for us (on the newsgroup) to tell without
having the program narrowed down to a reproducible case - i.e. a program
small enough to put in a post which reproduces the error.

-- Barry


AddThis Social Bookmark Button