Access Violation + VI failed to compile error

[FKhueson]

Recently, a project I've been working on crashes labview when opening, resulting in:

Exception: Access violation (0xC0000005) at EIP=0x0000000140E6D53F

Attached is the failure log and the offending file.  Opening the "FP Refs.ctl" shows an error in the error list, stating "VI has failed to compile" and I'm not positive how to diagnose that.  Any advice is appreciated@

[Jacobson-ni]

It might be more helpful to attach the full zip file that gets created when a crash occurs in addition to sending the report in to NI when prompted. I don't know exactly what the crash is but the lvlog you attached is telling us that FP Refs.ctl is an insane object.

http://digital.ni.com/public.nsf/allkb/AFA28DCC3DE89839862566B200594E8C

I would try just opening the control file to see if that also crashes LabVIEW or also hiding the control in a folder where LabVIEW can't load it when you are working from the project. That may tell us if the insanity is causing the crash or if there is something else. The easiest way to fix the insanity is almost always to just recreate the object.

[mikeporter]

Is it just this one project, or any project?

Is FP Refs.ctl a control you created?

Mike...

[kashiruvana]

I had that problem recently when I was trying to open a large VI, having lost track of the fact that I created the VI on a 64-bit machine and was trying to open and edit it in a 32-bit machine.  At first I could at least open it, but it wouldn't let me make any changes or build it.  If it got bigger, I wasn't even able to open it, but when I figured out why it was so big and fixed it, I was able to open, edit, and build no problem.  Could your issue be a memory issue as well?