LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

program forced to shut down

I have developed an application with LabWindows\CVI 2012. The program is running on laptop with XP. I am communicating with some devices on GPIB. One of the devices is a Agilent 3458a. On one computer I get a dialog which forces me to shut the program down. It happens intermittently. Sometimes it happens in a hour or two and sometimes the program will run overnite. It happens when I am communicating with the Agilent 3458a. I send it a command to start a current measurement and when I try and read the data it gets a error which says it could not collect the data. I also get a dialog that says:

 

"

nrdim_ana_cal.exe (Release X86 has encountered a problem and needs to close. We are sorry for the inconvenience.

If you are in the middle of something, the information you were working on might be lost.

For more information about this error. click here.

"

 

When I click here I get a bunch of information that looked like the old blue screen of death. It tells me what dlls are running and then has a memory dump.

It also has a Debug button but when I push it I do not get any information from it. The dialog has a CVI logo in the top right-hand corner  which makes me think it is something sent by some LabWindows dll.

 

Has any one seen anything like this? How can I derive any information from the click here memory dump?

 

I have an old Dell 610 laptop that never has this problem. The laptop I am having problems is a bit newer; it is a Dell Presario M4300.  We have tried it on other computers that were newer then the Dell 610 and they have similar problems.

 

Looking for a little help from someone who has had a similar experience or knows something about this program shutdown dialog.

The problem happens so randomly and infrequently it is hard to troubleshoot, any advice is appreciated.

 

thanks,

Don Pearce

0 Kudos
Message 1 of 3
(2,896 Views)

Please see all your pointers and other dynamic memory handling.

Also increase program stack from "option -> build option -> maximum stack size" from CVI menu bar as per memory(in bytes) you are using in program and in communication.

May this will help you.

0 Kudos
Message 2 of 3
(2,881 Views)

I increased the stack from 250000 to 300000. Did not make any difference. I have looked at my arrays to see if I made any out of boundary writes. Do not see anything like that.

0 Kudos
Message 3 of 3
(2,777 Views)