Access violations are rough because there are so many possible causes. The best advice I have for you would be to try to narrow down the cause of the issue.
Here are a couple of debugging methods you could start with:
-You said you're running an application/executable - perhaps check if the crash occurs in the LabVIEW Development Environment (ie, http://ae.natinst.com/public.nsf/web/searchinternal/ce69d2c55480900486257b6a0037c327?OpenDocument)
-Thinking about any possible changes you could have made to the system before it started giving you the access violation error (what changed? could this be the cause?)
-Isolating portions of the code and running them to see if there are certain portions of the code that cause the crash
-Isolating hardware (ie, using the instruments individually)
-Using a different computer, if possible
-A LabVIEW repair install can sometimes help
...etc, etc.
Just try and see if you can isolate/narrow the issue down as much as possible.
Another really good resource would be to search "LabVIEW Access Violation" online - you'll come up upon lots of other instances of this problem, and seeing some of the steps other people have tried could point you in a good direction.
Best of luck.
