469,357 Members | 1,857 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,357 developers. It's quick & easy.

Memory could not be read errors

The error message: 0x791f0d83 referenced memory at 0x0000000003. The memory could not be "read". Click OK to terminate and Cancel to debug.
When I debug, it states that it is an unhandled exception and the debugger can not trap the error (or something similar). Interesting enough the same exact error message has been reported on the web for a completely unrelated .NET project. The address is closest to two open DLLs in memory, mscoree.dll and mscorwks.dll both associated with the Framework. The other error I seem to get a lot is ExecutionEngine Exception

I've been trying to track this spurious error down. I've modified the app to do the same exact tasks, in order, repeatedly to generate some type of duplication pathway. What I have found is my .NET app throws the error at what appears to be a random piont in the code. It is not trappable, and from the log files, it never occurs at the same point twice.

The other thing is is that the same exact sequence runs without problems on a laptop computer but not a the dual processor. The dual proc has 2GB of memory. Both have the same security structure. The dual is also on RAID.

To me, its a system issue so I've tried to remove completely Studio and the Framework and then reinstall. No luck. I've scanned the disk for errors and that's fine. I've taken out each of the DIMMs and managed to reproduce the error with each DIMM by themselves. Other than a system rebuild, I don't know what else to try.

It was also suggested that interop could play a role on a dual proc with threading errors. To this end, I've finally removed all my old interop code and upgraded it to managed except for an old grid control which is not displayed.

Can anyone tell me what the possible sources of memory could not be read errors and how to do anymore diagnostics?
Jul 21 '05 #1
1 2305
Has this code worked before? Does it run if it's not doing anything?

Main()
{

}

Can you get other code to run properly? From what you've said, it sounds
like you've just got some code that's not working. Crashing on one machine
but not another may not be significant; if it crashes on 5 dual processor
machines but doesn't on 5 single processors then it is more significant. If
you're doing threading, that would be a big thing to look at, especially if
you're trying to use UI elements from different threads.

See if you can disable big chunks of the code and run it for a bit, see
which chunks seem to cause problems.

Good luck!

Steve

"Sean" <Se**@discussions.microsoft.com> wrote in message
news:B5**********************************@microsof t.com...
The error message: 0x791f0d83 referenced memory at 0x0000000003. The memory could not be "read". Click OK to terminate and Cancel to debug. When I debug, it states that it is an unhandled exception and the debugger can not trap the error (or something similar). Interesting enough the same
exact error message has been reported on the web for a completely unrelated
..NET project. The address is closest to two open DLLs in memory,
mscoree.dll and mscorwks.dll both associated with the Framework. The other
error I seem to get a lot is ExecutionEngine Exception
I've been trying to track this spurious error down. I've modified the app to do the same exact tasks, in order, repeatedly to generate some type of
duplication pathway. What I have found is my .NET app throws the error at
what appears to be a random piont in the code. It is not trappable, and
from the log files, it never occurs at the same point twice.
The other thing is is that the same exact sequence runs without problems on a laptop computer but not a the dual processor. The dual proc has 2GB of
memory. Both have the same security structure. The dual is also on RAID.
To me, its a system issue so I've tried to remove completely Studio and the Framework and then reinstall. No luck. I've scanned the disk for
errors and that's fine. I've taken out each of the DIMMs and managed to
reproduce the error with each DIMM by themselves. Other than a system
rebuild, I don't know what else to try.
It was also suggested that interop could play a role on a dual proc with threading errors. To this end, I've finally removed all my old interop code
and upgraded it to managed except for an old grid control which is not
displayed.
Can anyone tell me what the possible sources of memory could not be read

errors and how to do anymore diagnostics?
Jul 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

31 posts views Thread by lawrence | last post: by
6 posts views Thread by Ganesan selvaraj | last post: by
1 post views Thread by Sean | last post: by
2 posts views Thread by Mike | last post: by
13 posts views Thread by kolmogolov | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.