Error: Access violation (0xC0000005) at EIP=0x00764624

[John_Morrissey]

Disabling the Anti-Virus had no effect.  From what I've been told the root of the problem is related to the function in LabVIEW that recompiles VIs.  We've been told that it will be fixed in a patch release of LabVIEW in February.  I think you are seeing something different based on the error code you mentioned.

John

[dstrandb]

Hi jtw11,

Have you attempted the suggestions from earlier in this thread? If you're still expriencing this issue, you might try completely uninstalling the antivirus program. It seems like this error is most often associated with conflicts with an antivirus program.

[juannand1]

Try deactivate DEP

http://www.vistax64.com/tutorials/120778-dep-enable-disable.html

maybe it works!!

Good luck!!!

[QFang]

I just had one of our customers running a compiled program compiled with version 11.0.1f2 (32bit).  The program is running on Windows 7 computers.

The EIP code is different, EIP=0x35054168 but since ni.com search did not provide any hits for this or even EIP=0x3 I decided to post it here.

Also, the customer environment is not conducive to "diabling anitvirus" or "make user the admin" or similar.. The software has worked fine for several weeks, with several users starting to report the issue today.

[jtw11]

QFang,

I found that the issue went away after upgrading to LV2012 (or it may have been one of the service packs in 2012). I have since upgraded to 2013 and I have not seen the error there either. 

Good luck,

Josh

[QFang]

Thanks for the update.. 

I will try this approach.. unfortunately the customer company requires that all software be "compiled" or "built" into install packages by their IT, so after our recompile (and QC testing), it will be days before the update will reach them.. still.. this gives me hope!

Thanks!!

Q

[John_Morrissey]

QFang,

Our issue also went away, but it was with LV 2012 SP1.  We saw it with the initial version of LabVIEW 2012 and were able to get a special build with a patch in September last year, and then got the real fix when SP1 came out in March.

John

[QFang]

Thanks again for this feedback.. my wish would be to go straight to LV2013.. Has anyone had significant run-time with this version yet, or is 2012 SP1 the last "proven" good version for this issue?

[jtw11]

I have had fairly limited run-time but I have not found any "surprises". 

[John_Morrissey]

No run time on 2013 from our end.