The instruction at x referenced memory at y. The memory could not be written

[Big Dog]

I have been receiving this error message over the past 6-months on our Lookout 5.0 setup. This is shown in a dialog box, with the options 'click OK to terminate program, click CANCEL o debug program'.

Lookout is v5.0 lastest fixes file installed, Citadel is latest also. OS is W2K, SP4. Any ideas. Lookout and Citadel are the only things running on this box. Application is a typical base station talking to 41 remote sites. It seems to happen on our overview screen which has many (41) mouse ojects. We use this object to pop-up a window when you are over a particular communication indicator. The pop-up dialog allows for a more detailed view of the remote site.

I cannot replicate, happens randomly. Sometimes several times a day, other times it will go for weeks or months. The only way to get out of it is to click OK, then restart computer. Checked OS processes prior to shutting down, lookout.exe and the ldcitdl.exe, ldads.exe, and ldtsrv.exe are all running, but at 0% CPU usage. Any suggestions on where to start debugging.

[Rick_K]

This type of error is very hard to troubleshoot.
Here are a few reasons why this might happen and the solutions:

1. Bad installation: perhaps the installation has become corrupted and a reinstall of the software might be the trick.
2. There might be something within your Lookout process that is causing this to happen over time through a memory leak. The way to find it being to begin to eliminating things from the process to see which object is causing the issue. Once you find what is causing the crash, try to come up with a way to not use that object as a workaround.
3. You are experiencing some type of bug in Lookout 5. This would be solved by upgrading to the most current Version, which is now 6.1.

I hope that one of these options will help you solve the issue.

Rick Kuhlman
National Instruments Applications Engineer

[Khalid]

Hi,

In addition to the good suggestions by Rick, you may want to setup Dr. Watson to capture some of the info' when this happens.  This will definitely help the developers in pin-pointing the problem.  See the following for more details and on setting up Dr. Watson: 

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/drwatson_overview.msp...

If you do end up setting this up, and get an error log, feel free to post it here (in addition to mailing it to NI) -- we can try some sleuthing ourselves 

Regards,

-Khalid