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

[John_Morrissey]

Hi Rohama,

Thanks for the reply.  Yes, we see the crashes on several PCs and you wouldn't be able to run the sequences without our equipment, so I don't think it's worthwile to send the code at this point, but thank you for the offer.  I think the best option is to have an NI Application engineer remotely connect to our station and see the crashes.  My initial goal is to try to get it to be repeatable, but I haven't been able to do that since it seems very random in nature.

Based on Tom's suggestion to the previous user, I changing my login to one with PC admin privileges and that seems to have improved it, but I just did that on Friday and will need more time to guage the results.  If this is the cause I need to know why it would cause a code crash and not a more graceful shutdown or alert.

John

[Rohama_K]

Hi John,

If you want to talk to an NI Applications Engineer, creating a service request is the way to go. After you changed your login to PC admin, are there no crashes or fewer crashes?

[Stoove]

We appear to be having a very similar problem with LabVIEW 2011. Has there been a solution?

[amezam]

Hello Stoove and others,

Are you using LabVIEW 2011 SP1? I found a similar case in which the problem was solved using LabVIEW 2011 SP1.

Best Regards,

[Stoove]

Hi again Amezam,

No, we are not using SP1. I will see if we can go about updating to SP1. HOWEVER, our Tech Support (who have had a look at this issue) warned us that it would apparrently require a recompilation of any packed libraries we use - the ones we use are 3rd party and we therefore might have trouble with this. For that reason, we're somewhat cautious about upgrading until we know whether this will be a problem.

[Kira_T]

Hi Stoove,

What version of Windows are you running? Do you see the same problem on multiple computers? Have you been able to investigate Outlaw's suggestions of making sure there is no Anti Virus software that could be causing this problem? Thanks!

Regards,

Kira T

[Stoove]

We are running Windows 7 on the PC we see the problem on.

I've raised the problem of antivirus with IT, we're looking into it but no results yet (thanks for the reminder).

We're unable to test the code on other PC's due to the requirement of an attached instrument in the PCI slot, so unfortunately that sanity test isn't achievable.

I'll report back as soon as I know about the AV software.

Thanks for the suggestions, all.

[Stoove]

Further to all of this, I have been able to exclude a section of code that I had suspected might be causing the problem. By disabling the code which updates the main output of my code (a histogram) I've deduced that calling the histogram and plotting VI's extremely often are not causing the problem. Since the majority of the remainder of the code is 3rd party drivers, I will do my best to find out if these are causing the problem.

I have already managed to disqualify some of my sub-vi's for this purpose.

[jtw11]

Have you had any luck with disabling the anti-virus software? I am having the same issue (except with EIP=0x30253410). The problem is very intermittent and frustrating. We have tried disabling UAC without any luck. Right now we are running the VI (in an executable) as an administrator to see if that helps.  Any suggestions would be appreciated. Thanks, Josh.

[jtw11]

Have you had any luck with disabling the anti-virus software? I am having the same issue (except with EIP=0x30253410). The problem is very intermittent and frustrating. We have tried disabling UAC without any luck. Right now we are running the VI (in an executable) as an administrator to see if that helps.  Any suggestions would be appreciated. Thanks, Josh.