Why does closing a .exe cause program to "Not Respond"?

[Wardjw0]

I have generated an executable using the LabView compiler.  The program runs as expected, but when I close the program Windows prompts me with the program stopped working error.  The error information is as follows:

Problem signature:
Problem Event Name: APPCRASH
Application Name: MegaAwesome.exe
Application Version: 1.0.0.0
Application Timestamp: 4e020bac
Fault Module Name: user32.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4a5bdb2f
Exception Code: c0000005
Exception Offset: 691c738f
OS Version: 6.1.7600.2.0.0.256.4
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Please let me know if I have failed to supply enough information to help in troubleshooting this issue.

Thanks,

Jeremy

[RavensFan]

Is this executable in any way related to the other vi you are having problems with?  Why does .vi only work every 3rd run?

Do you have any .dll's being used in this executable or other calls to external code?

[Wardjw0]

Yes, they are one in the same.  The .vi is the main program used within the .exe.  The issues seemed unrelated, at least up front, so I posted a question on each issue.  The .exe does call .dll's, some of which are supplied by LabView and others that were compiled from the sub-vi's that I built.

[RavensFan]

I think you either have a bad .dll or a bad call setup to your dll.  The .dll is stomping all over your LabVIEW memory.

Before worrying about your .exe, I think you need to worry about the problem in your other thread.

[altenbach]

---

@Wardjw0 wrote:

I have generated an executable using the LabView compiler.

---

On a side note:

Just to get some potential confusion out of the way, an executable is created by the application builder, not the compiler.

A VI is always compiled, even if run in the development system. (More information).