Error on running a certain simulation method on an open source software

0

The software I am using is an open source geostatistics package called SGEMS. There are many simulation methods and many of them work fine, however when I am trying to use one multi-point simulation method then it shows me the general windows error along with the following error:

The instruction at "..." referenced memory at "...". The memory could not be "read"

My computer details are:

Microsoft XP
Professional
Version 2002
Service Pack 3

6400 @ 2.13GHz

user42307

Posted 2010-09-09T18:11:39.747

Reputation:

possible duplicate of Error: The instruction at "..." referenced memory at "...". The memory could not be "read"

– heavyd – 2010-09-09T18:44:33.767

2@Heavyd - It's a duplicate but he is adding more info this time. Last one was closed for lack of info. Let's not discourage him :) – JNK – 2010-09-09T18:56:00.913

@JNK, the only difference I see is the title, looks like an exact dupe to me. – heavyd – 2010-09-09T19:01:13.647

@heavyd - I see that now. The original he EDITED after it was closed. It was closed orignally because he had almost no info in it. Take a look at the timestamps for closing and editing. – JNK – 2010-09-09T19:08:48.683

1@JNK Instead of harping on whether it is a duplicate or not, why not vote to re-open the original and vote to close this one. – BinaryMisfit – 2010-09-10T11:55:00.510

@heavyd Nice catch. I have closed the previous one as a duplicate of this one solely because this one has an accepted answer. In future, please vote to re-open the original as well. – BinaryMisfit – 2010-09-10T11:55:52.177

@Diago - Apologies, I didn't mean to harp. I saw the original thread get closed and this one opened with more info, so assumed it was fine to leave this one open since it was more complete. – JNK – 2010-09-10T12:27:46.840

Answers

1

This is a bug in the program: it's trying to access memory that it's not supposed to. (Strictly speaking it could be a bug in Windows, or a hardware problem, but they're a lot less likely.) This is a very generic kind of bug, so your best option is to report it to the authors (giving them the full data you've passed to the program — it's better if you can reproduce the bug with a small amount of input data — and the full error message).

Gilles 'SO- stop being evil'

Posted 2010-09-09T18:11:39.747

Reputation: 58 319

I too suspect the problem to be related with memory. Thanks for the input, though I know it's hard to identify what's the problem. – None – 2010-09-10T00:02:21.217