Labview 8.0.1 crash code 0xc0000005

[petitprince]

Hi, This crash happens it seems mainly when may Zeiss Axiovert 200 is connected. I use the Zeiss MTB to drive it. It seems not to happen always at the same place in my code! In attached file are the info provide by windows : the offset is 00cadd7e and the error is located in Labview.exe module (Version 8.0.1.4000) thanks for your help

[Andy F.]

Hey petitprince! 

Honestly, I am not sure what code 0xc0000005 means.  Are there any LabVIEW error messages that go along with this?  You say this happens when your Zeiss Axiovert is connected, correct?  How is this connected?  How are you communicating?  It is entirely possible that this is a corruption that can be taken care of by copying the code on the Block Diagram to a new blank VI.  Does this help?  Please let me know if you have any additional information. 

Thanks!
Andy F.

[petitprince]

Hi,

Thanks for your comment. Unfortunately not, since this is a crash, there is no message in Labview (Labview is hang, and windows display the error report dialog)! Now I found that one function of the MTB seems buggy and not using it seems to help. I had this morning again this error despite this new way of doing. It's communicating through a com port fully handled by the Zeiss Microscope Tool Box (MTB). Then I just call the dll functions documented in the SDK. I also tried to put my stuff in a new VI at the same time. So maybe this participated in reducing the occurences of the crash. Actually, sometimes I already had "insane node" messages. But usually after saving the VI once, they no longer appears.

[AESulzer]

Hello,

I would recommend contacting NI and investigating the error that way. Typically, after LabVIEW crashes, it will give you an "investigate" dialog the next time you open it. If you continue through this dialog and report the crash to NI, then LabVIEW will generate an error log that you can send in. Also, the Applications Engineer that you work with might be able to narrow down where the problem is coming from. So, the next time you encounter a crash, go ahead and jot down what steps you took to bring it about and then use the "investigate" dialog to report it to NI.

Kind Regards,

[rolfk]

---

@Andy F. wrote:
Hey petitprince! 

Honestly, I am not sure what code 0xc0000005 means.  Are there any LabVIEW error messages that go along with this?  You say this happens when your Zeiss Axiovert is connected, correct?  How is this connected?  How are you communicating?  It is entirely possible that this is a corruption that can be taken care of by copying the code on the Block Diagram to a new blank VI.  Does this help?  Please let me know if you have any additional information. 

Thanks!
Andy F.

---

0xc0000005 is a Windows exception. In this case meaning a STATUS_ACCESS_VIOLATION. Windows should have displayed a dialog box with some information that there has been an Access Violation.

Somewhere the software is accessing an invalid pointer and chances are very high that it is happening in the Zeiss Axiovert software somewhere. It could  be a bug in that software or if it is a DLL a badly configured Call Library Node.

The insane node errors make it even more likely that you have not configured the Call Library Node correctly or are providing to short of buffers from LabVIEW for the DLL to write in resulting in the DLL to overwrite data it definitely shouldn't, destroying vitale information LabVIEW is using internally. You will have to go through all Call Library Nodes and check, double check and triple check that you are providing the correct datatypes and for buffers the DLL is supposed to write in you are preallocating the buffer in LabVIEW with the right size before passing the pointer to the Call Library Node.

Rolf Kalbermatter

Message Edited by rolfk on 04-11-2006 10:03 AM