Crashing LabView when running DAQ assistant.

[TheSuperFive]

I am running labview with NIDAQ.mx drivers. When dropping the DAQ assistant into my program is freezes the program. Attached is the error file. The Ni-dax is connected via the USB port.

[Bob_Schor]

Error 1097 occurred at an unidentified location

Possible reason(s):

LabVIEW: (Hex 0x449) An exception occurred within the external code called by a Call Library Function Node. The exception might have corrupted the LabVIEW memory. Save any work to a new location and restart LabVIEW.

To provide any more insight without seeing the code that was running (fortunately, many experienced LabVIEW users should be able to open a LabVIEW 2020 set of VIs) will be basically a WAG.  Also, please describe the "external code" that was called by a Call Library Function Node (and maybe attach that, as well).

Bob Schor

[TheSuperFive]

Thanks for responding Bob, I cant save the vi since it crashes when i add it but its a simple one to make. All i do is drop in the daq assistant from the NIDAQ.mx driver template. I will attach a screen shot to hopefully assist you.

[Bob_Schor]

Thanks, all Five of you.

     I opened LabVIEW 2021 (32-bit), created a New VI, opened the NI DAQmx Palette and dropped down a DAQ Assistant.  I didn't choose any options (since I didn't have anything particular connected to my PC), and was left with the following:

The text you provided included "Got corruption with error 1097 calling library mxwLVAPI.dll function mxwOutEditTask3".  Where does this come from?  It certainly didn't pop out when I followed your suggestion of placing a DAQ Assistant on an empty VI. 

I'm sorry I'm unable to replicate the error you are having.  Maybe your entire LabVIEW installation is faulty.  Does the same thing happen if you go to another PC with LabVIEW, open a VI, and drop in a DAQ assistant?  [Seems to me that NI has been getting LabVIEW beginners to do this for more than a decade without too many serious crashes ...].

Bob Schor 

[TheSuperFive]

Yes it seems my computer is the only one with this issue. I am in a labview class and we all installed it the same way. It may be something i messed up while installation. The corrupt DLL I have no idea since it is mostly a vanilla install. I have reinstalled twice and even attempted to repair all of the applications. One thing to note is that labview works perfectly except for when it comes to calling upon the DAQ.mx items. Below is what i have installed incase that helps.