LV2013 crashes when opening VI developed in LV2009

[MinerHokieRamp]

I tried using LV2013 to open a VI developed with LV2009. After compiling VIs for a couple of minutes, there was an error notification:

Problem signature:

  Problem Event Name: BEX
  Application Name: LabVIEW.exe
  Application Version: 13.0.0.4047
  Application Timestamp: 51d23238
  Fault Module Name: StackHash_9762
  Fault Module Version: 0.0.0.0
  Fault Module Timestamp: 00000000
  Exception Offset: 0012f6c3
  Exception Code: c0000005
  Exception Data: badc0de1
  OS Version: 6.1.7601.2.1.0.256.48
  Locale ID: 1033
  Additional Information 1: 9762
  Additional Information 2: 97628f8a611d21a2f9fa75d21e3a59e7
  Additional Information 3: ec46
  Additional Information 4: ec460a9aede0c4c22dc560bb0d2a629a

Here's a screenshot of the problem dialog box:

I found another discussion concerning a 'BEX Event' with LV2010.

The PC is running Windows 7 Professional SP1 (32 bit).

Appreciate any help I can get.

Thanks,

Jeff

[JÞB]

Well,

that there is a buffer overflow exception thrown by the OS not LabVIEW.  Is it possible that large data sets are stored as default values?  Can you open and save subvis?  Did you try a Mass Compile?  (I'd try mass compile first but, branch your source code repository if you will also need the 2009 version)

Someone over at Microsoft has a sense of humor, I got a kick out of the munge of "Bad Code 1" in the exception report

[MinerHokieRamp]

Thanks for the reply.

I peformed the mass compile. Now, when I open the vi, it immediately crashes. Results look about the same; I didn't record the details.

Here are the contents of the mass compile log:

#### Starting Mass Compile: Mon, Oct 07, 2013 3:05:24 PM
  Directory: "C:\Users\ADIT\Desktop\Version 4_FOR_TEST\ADIT Source\IVSC"
Search failed to find "user32" previously from "user32"
Search failed to find "kernel32" previously from "kernel32"
#### Finished Mass Compile: Mon, Oct 07, 2013 3:06:36 PM

Jeff

[JÞB]

Turn on NIER (NI Error Reporting) attach the code that caused the crash.  Is your SSP up to date?  Open a ticket - this needs attention to identify the cause of the crash.

[Tortu]

Greetings Jeff.

Does this behaviour happens when you try to update a simple VI from LabVIEW 2009 to LabVIEW 2013?

After you did the mass compile, does the BEX error still appears?

Here are some suggestions that might help you with the BEX error.

http://social.technet.microsoft.com/Forums/windows/en-US/48f17381-531d-4ae5-8ea5-c289ec09857f/bex-er...

http://www.sevenforums.com/gaming/39174-bex-error.html

http://answers.microsoft.com/en-us/windows/forum/windows_other-windows_programs/problem-event-name-b...

Greetings

Luis J.

Applications Engineer

National Instruments

[MinerHokieRamp]

---

@Tortu wrote:

Greetings Jeff.

Does this behaviour happens when you try to update a simple VI from LabVIEW 2009 to LabVIEW 2013? I tried opening 2 subVIs (ones that hadn't been recompiled) and there were no errors, the VI opened with no issues.

After you did the mass compile, does the BEX error still appears? After mass compile, the BEX error still occurs when I open the top-level VI.

Here are some suggestions that might help you with the BEX error.

http://social.technet.microsoft.com/Forums/windows/en-US/48f17381-531d-4ae5-8ea5-c289ec09857f/bex-er...

http://www.sevenforums.com/gaming/39174-bex-error.html

http://answers.microsoft.com/en-us/windows/forum/windows_other-windows_programs/problem-event-name-b...

I see some recommendations to change the DEP settings. I'll try it.

Thanks for your help,

Jeff

---

[MinerHokieRamp]

I tried turning off Windows 7 DEP (Data Execution Prevention) for LV2013. 

Opened the top-level VI and received the same BEX error.

[Tortu]

Greetings Jeff

Since you had no problems opening other subVIs, what happens if you create a fresh project, and add all the VIs that your older project has? It is possible that the LabVIEW project became corrupt with the version change.

Let us know how it goes, and what other troubleshooting steps you have taken.

Regards

[MinerHokieRamp]

I didn't attempt to open my only copy of the top-level VI. So, I haven't lost the original code.

I just can't get to that top-level code with LV2013.

[MinerHokieRamp]

Here's something I tried with Windows on the Microsoft forum:

http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/bex-error-crashes-labview-201...

Thanks,