LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Access Violation (0xC0000005) at EIP=0x3032E7D5

That's a bummer Cat Sad. If you're curious, maybe you can look into some source code control to help manage some of your software revisions and keep nice backups? I am a big fan of TortoiseSVN as a client, and hosting your code on a a cloud based server like Assembla.

 

From what I was able to see. It looks like the frequency of the crash went down in newer versions of LabVIEW, so it would be interesting to check. So, I would definitely recommend trying a newer version of LabVIEW. This recommendation goes beyond this current application as well. It is a good idea to keep your code updated to the newest versions as they release, because they add new features and fix many issues.

 

A couple clarifying questions. This crash happens when your code first starts running, correct? Does it happen everytime you run the code, or only sometimes?

 

 

Tim A.
0 Kudos
Message 11 of 11
(863 Views)