LabVIEW crashing when running NI-DSP VI on Windows XP

I am in the process of upgrading a software application from LabVIEW 3.1 on Windows 3.11 to LabVIEW 7.0 on Windows XP with NI-DAQ 7.2. The hardware has been replaced, the relevant hardware change here is from the AT-DSP2200 to the NI-4551.
The source code uses the NI-DSP libraries to control the DSP2200. I can't find any equivalent in the new LabVIEW (and have assumed that there is none, this is all covered in the MAXX now). The source code has been convereted to LabVIEW 7.
When the source code is opened on the Windows XP machine LabVIEW crashes. I've traced to cause of this crash to the NI-DSP code. Whenever I try to open any VI that contains the DSP code it crashes LabVIEW. I think the problem is the CNI call
inside the DSP library. When I try opening the source code on a computer that doesn't have the NI-4551 installed there are no problems.
What is the upgrade from NI-DSP to? Is there a direct mapping of NI-DSP functions to equivalent NI-DAQ ones? How is it that having the hardware plugged in causes a crash even though it shouldn't be accesssed until I run the VI?
Any help would be appreciated.
Thanks.

Hello EborLance,
The NI-4551 can use either NI-DAQ or NI-DSA as the driver. If you only have NI-DAQ installed, any program that uses the NI-DSA functions may be crashing.
There is no direct mapping of NI-DAQ functions to NI-DSA functions but you can download and install the NI-DSA driver from the website. Current DSA Drivers
Once you have installed the NI-DSA driver, you should see the functionality you were previously used to and your program should run.
Thanks,
C. Flip
National Instruments

Similar Messages

Crashes when running applications from network share - "Windows cannot access the file for one of the following reasons"

Hi,
starting a couple of weeks ago, we get the following error(s) when running applications from a network share. We don't know what causes this, we are not aware of any major changes in our network infrastructure or client/Server configuration. We did upgrade
a lot of machines to Windows 8, but the issue also occurs on older Win7 computers.
We figured out a workaround though: The applications run fine when launching from a FQDN share (like
\\share.domain.Company.com) and only cause problems when running from
\\share directly. They have worked fine for years without FQDN though.
Any ideas?
Error Details (the Kind of error differs greatly):
# 1 #
Log Name: Application
Source: Application Error
Date: ...
Event ID: 1005
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: vmDEV
Description:
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program XYZ
because of this error.
Program: XYZ
File:
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
Additional data
Error value: C000020C [ also seen with code C00000C4]
#2 (German error Messages from now on, we only use German OSes, the above english one is translated based on similar error Messages I found on the web) #
Name der fehlerhaften Anwendung: XYZ.exe, Version: 2015.0.496.5054, Zeitstempel: 0x54ea67c3
Name des fehlerhaften Moduls: clr.dll, Version: 4.0.30319.34014, Zeitstempel: 0x52e0b784
Ausnahmecode: 0xc0000006
Fehleroffset: 0x00026549
ID des fehlerhaften Prozesses: 0x13ac
Startzeit der fehlerhaften Anwendung: 0x01d055a854d36445
Pfad der fehlerhaften Anwendung: \\share\application.exe
Pfad des fehlerhaften Moduls: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Berichtskennung: 949ea933-c19b-11e4-bf04-78542e186754
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
Anwendung: XYZ.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: Ausnahmecode c0000006, Ausnahmeadresse 720B6549
Stapel:
# 3 #
Anwendung: WpfApp.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.Runtime.InteropServices.SEHException
Stapel:
   bei SP.Forms.AutoCompleteSelectionBase.OnEnter(System.EventArgs)
   bei System.Windows.Forms.Control.NotifyEnter()
   bei System.Windows.Forms.ContainerControl.UpdateFocusedControl()
# 4 #
Anwendung: WpfApp.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.Runtime.InteropServices.SEHException
Stapel:
   bei System.IO.UnmanagedMemoryStream.ReadByte()
   bei System.IO.BinaryReader.ReadByte()
   bei System.IO.BinaryReader.Read7BitEncodedInt()
   bei System.Resources.ResourceReader._LoadObjectV2(Int32, System.Resources.ResourceTypeCode ByRef)
   bei System.Resources.ResourceReader.LoadObjectV2(Int32, System.Resources.ResourceTypeCode ByRef)
   bei System.Resources.ResourceReader.LoadObject(Int32, System.Resources.ResourceTypeCode ByRef)
   bei System.Resources.RuntimeResourceSet.GetObject(System.String, Boolean, Boolean)
   bei System.Resources.RuntimeResourceSet.GetObject(System.String, Boolean)
   bei System.Resources.ResourceManager.GetObject(System.String, System.Globalization.CultureInfo, Boolean)
   bei System.Resources.ResourceManager.GetStream(System.String, System.Globalization.CultureInfo)
# 5 #
Anwendung: WpfApp.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.Runtime.InteropServices.SEHException
Stapel:
   bei System.Reflection.RuntimeParameterInfo.get_Name()
   bei System.Diagnostics.StackTrace.ToString(TraceFormat)
   bei System.Environment.GetStackTrace(System.Exception, Boolean)
   bei System.Exception.GetStackTrace(Boolean)
   bei System.Exception.ToString(Boolean, Boolean)
   bei System.Exception.ToString(Boolean, Boolean)
   bei System.Exception.ToString(Boolean, Boolean)
   bei System.Exception.ToString()
# 6 #
Name der fehlerhaften Anwendung: XYZ.exe, Version: 2015.0.496.5054, Zeitstempel: 0x54ea834f
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 6.3.9600.17278, Zeitstempel: 0x53eeb460
Ausnahmecode: 0xe0434352
Fehleroffset: 0x00012f71
ID des fehlerhaften Prozesses: 0xa68
Startzeit der fehlerhaften Anwendung: 0x01d0559cb7ec4ed6
Pfad der fehlerhaften Anwendung: \\share\XYZ.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\KERNELBASE.dll
Berichtskennung: 010514d0-c190-11e4-bf04-78542e186754
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
# 7 #
Name der fehlerhaften Anwendung: XYZ.exe, Version: 2015.0.496.5054, Zeitstempel: 0x54ea7a6e
Name des fehlerhaften Moduls: ntdll.dll, Version: 6.3.9600.17630, Zeitstempel: 0x54b0d74f
Ausnahmecode: 0xc0000006
Fehleroffset: 0x0006db27
ID des fehlerhaften Prozesses: 0x18dc
Startzeit der fehlerhaften Anwendung: 0x01d0559cb08529c3
Pfad der fehlerhaften Anwendung: \\share\xyz.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: ef389186-c18f-11e4-bf04-78542e186754
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Hi,
>>The applications run fine when launching from a FQDN share
It sounds like a DNS suffix issue. When this issue occurs, please try to ping share on the client, then check if the corresponding IP address is correct. If the IP address is wrong, please adjust your settings of DNS to make sure that the client can resolve
the share correctly.
If it's very hard to change the settings of the DNS for some reason, as a work around, we can add the entry into the clients' hosts file.
Best Regards.
Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

LabVIEW crashes when you run a VI that contains a mixed signal graph with a multi-plot cursor.

Hello, LV 8.2.1 notes indicates the following bug fix:
43SAIR2A Fixed an issue where LabVIEW crashes when you run a VI that contains a mixed signal graph with a multi-plot cursor.
I am running this version, and still have this behavior. Is there anything I may be missing, and/or certain circumstances that may still be causing this?
thanks in advance,
Darren

Darren:
I looked at the CAR ID that you mentioned and the issue has been resolved in LabVIEW 8.2.1. To verify something similar, I ran the attached VI and things worked just fine. Please feel free to send me the steps to follow to reproduce the issue you are running into in 8.2.1.
Regards,
Rudi N.
Attachments:
MixedGraphs.vi ‏15 KB

LabVIEW Crashes when Opening Project

Hey Guys,
I'm running into an interesting issue where LabVIEW crashes when opening a project. This is the second time I've run into this issue, on the same project. To get around it the first time I simply deleted and re-made my project, but since it's happened again, I need to figure out how to debug it. The symptom is that LabVIEW will crash when opening the project (sometimes I can see the "vi loading" screen) without any indication that crash has occured. It doesn't even launch the error reporter, the process just dies. Anyone know how I can go about debugging this?
Solved!
Go to Solution.

xkenneth86,
What version of LabVIEW? Have you ever had previous versions of LabVIEW on your computer? Can you attach a screenshot of the crash?
David H.
National Instruments

LabVIEW crashes when I save changes to a particular VI.

LabVIEW crashes when it tries to compile a particular VI. I have managed to get it to work a couple of times by changing a few things and making some subVIs, but the problem keeps returning.
Is there some way to fix this or clean the VI of whatever corruption keeps occurring?
Thank you,
David R. Asher

I can think of address/hardware conflicts or something that LabVIEW cannot provide an error message. I would go with hardware/address conflicts.
Try renaming the file and executing it stand-alone. also try making it as a subvi and run the toplevel code.
Kudos always welcome for helpful posts

Why does LabView crash when unloading my DLL (reentrant calls)?

I have written a DLL in Borland Delphi using multiple threads that exports several functions (stdcall). I am using LabVIEW 6i on a WinXP machine. All functions in the DLL work as expected and return correct values. Everything works fine if I set all Call Library Function Nodes to 'UI-Thread', but as soon as I set one Function Node to 'Reentrant', LabView crashes when I close the VI after it has been executed. I assume the error is caused by the DLL unloading mechanism of LabView. Other C++/Delphi programs using the DLL reentrantly work fine, this only occurs in LabView. In which thread does LabView call FreeLibrary/DLL_PROCESS_DETACH? Has anyone experienced similar problems?

I have never run into this situation myself, but I do know that calling a multi-threaded DLL or CIN from LabVIEW does depend upon the following criteria:
If your CIN/DLL doesn't have any global data storage (global variables, files on disk, etc.), AND it doesn't access any hardware (register-level programming) AND it doesn't call any functions/DLLs/Drivers that are thread-unsafe.
OR
Your CIN/DLL protects (with semaphores or mutex's) access to those global resources.
OR
Your DLL is only called from one, non-reentrant VI
OR
Your CIN is only called from one, non-reentrant VI AND you don't access any global resources from CINInit, CINAbort, CINDispose, etc. procedures.
Hopefully this information can help you out in some way.
J.R. Allen

Use loadSWF load my stage3D game swf and show In AIR , This swf may crash when running

Problem Description:
use loadSWF load my stage3D game swf and show , This swf may crash when running
Steps to Reproduce:
run my Upload Project . Fill in the login box, any account and password . Because of network problems, you may need to wait a long time to show up login box
Actual Result:
this swf crash when running
Expected Result:
this swf do not crash when running
Any Workarounds:
Test Configuration
My Hardware and Environment details:
1.this url's swf load files in worker
2.this url's swf use SDK is Flex 4.6.0(bulid23201)
3.this url's swf is Flex Project
Upload Project Url:
http://fight.fuhuodao.com/fight/testUrl/!FightAirShell.zip

The loading of SWFs from AIR has a different Security model than that of the WebPlayer. There is a workaround to loading plugins in AIR: If you use a static plugin this should work for you. To do this: Link in the plugin at compile time, and pass the PluginInfoResource to the loadPlugin() method.

LabView crash when intensity graph is in P6 of tab control

Any available fixes for LabView crash when intensity graph is put on page 6 of tab control and right-clicked??

Michael,
This has been fixed in LabVIEW 6.1.
Regards,
Cyril Bouton
Applications Engineer
National Instruments
Cyril Bouton
Active LabVIEW Developper

Macbook Pro crashes when running on battery

Hi.
My Macbook Pro crashes when running in battery. It seems it doesn't happen when connected to the power.
Is there any way to know if it's a battery malfunction?
Because Apple changed the motherboard a month ago or so because Nvidia broke. So it could be also the connector to the battery?
Is there any tests I can run?
Thanks

I would take it back to Apple and have them check it. You may have got a replacement logic board with a problem. Apple usually use rebuilt ones.
Dave M.
MacOSG Founder/Ambassador  An Apple User Group  iTunes: MacOSG Podcast
Macsimum News Associate Editor  Creator of 'Mac611 - Mobile Mac Support'

Test Stand crashing when running ESS

Test Stand is crashing when running ESS and one of the test fails. I am able to run that same test alone and there are no issues. I am seeing the following messege in the windows event log.
Faulting application testexec.exe, version 13.0.0.0, stamp 4a9eca49, faulting module cvirte.dll, version 9.0.0.330, stamp 48dd23b1, debug? 0, fault address 0x000ac355.

1) What is ESS?
2) Are you calling a dll from TestStand? If so make sure the settings for passing parameters to the dll are exactly correct or it could cause memory corruption. If not, how exactly is teststand calling the test?
-Doug

Labview crashes when creating large image files

I have a problem with Labview 6.0.2( I've tested evaluation version 7.0 too).
I'm constructing a very large image, for example: 4500x4500 pixels. Labview crashes when converting the pixture to a pixmap. The image is fully constructed on my screen (in a picture control), but when converting it to a pixmap (for saving the image in a known format (bmp, jpg, tiff)), Labview crashes.
I did some testing and when the number of pixels exceeded the limit of 2^24(16777216), the file 'image.cpp' crashes on line 1570. The vi to convert it to a pixmap is: P'icture to pixmap.vi'
Does someone know a workaround for this problem? Or is there a fix for it?
Thank you!

I've tested the 6i version of my VI in Labview 7.0 evalutation version. It raised an error but not the same error:
d:\lvworm\src\lvsource\compatexport.cpp(37) : DAbort: Called a routine not in the compatibility LVRT table
$Id: //labview/branches/Wormhole/dev/lvsource/compatexport.cpp#11 $
0x004BD4CB - LabVIEW_Eval + 0
0x0EB710D9 - lvs248 + 0
0x094C87A0 - + 0
So i replaced the picture VI's with the 7.0 evalutation version VI's, and it worked. It is now possible for me to construct very large image files!
I see no attached VI to test. But i guess it is also solved in Labview 7.0
I used this file to convert the picture to image data:
C:\Program Files\National Instruments\LabVIEW 7.0 Evaluation\vi.lib
\picture\pictutil.llb\Picture to Pixmap.vi
And this file to convert image data to bmp:
C:\Program Files\National Instruments\LabVIEW 7.0 Evaluation\vi.lib\picture\bmp.llb\Write BMP File.vi
I guess i have to write a workaround for this problem:
divide the picture in blocks of 4096 x 4096 and then merge the image data arrays of the bloks together.

Why does system suite pro 12 crash when running file cleaner is running while firefox is installed? If I uninstall firefox then system suite pro 12 won't crash.

When I downloaded the newest version of firefox system suite pro 12 crashes when running file cleaner after I uninstall firefox system suite pro 12 doesn't crash. I have window 7 premium home edition 64 bit.

You should know a few things before before getting started:
1. Registry "cleaners" and "system optimizers" like SystemSuite are very unreliable, cause more problems then they propose to fix, have little to no benefit, and are somewhat of a scam. Running them on a system is almost guaranteeing a crash or hiccups somewhere along the process. running them is never a good idea. all you need is a good, simple, free anti-virus (like Microsoft Security Essentials), and use the built in Windows Utilities to clean and sped up your computer if needed.
2. This is a Firefox forum, so if you are having a problem with SystemSuite, we might not be able to help you.
I'll give you a few things you can do to see if this is just a Windows problem:
Run all Windows Updates, install all needed service packs, etc.
Update your graphics driver (Firefox uses your graphics card for some rendering, and an out of date graphics card driver can cause problems. [https://support.mozilla.org/en-US/kb/how-do-i-upgrade-my-graphics-drivers https://support.mozilla.org/en-US/kb/how-do-i-upgrade-my-graphics-drivers].
Update all your plugins (Flash, Java, etc.): [http://www.mozilla.org/plugincheck/ http://www.mozilla.org/plugincheck/].
Download and Install MalwareBytes Anti-Malware, run a full Scan. [http://www.malwarebytes.org/ http://www.malwarebytes.org/]. This helps check that there are no viruses on your computer causing issues. You can uninstall this program after you clean off any infections.
Plus, I'd strongly recommend removing systemsuite and any other "optimizers" you might have.

JVM will crash when running tomcat4

Hi,
My JVM crash when running tomcat awhile. Any suggestion? Thanks.
Here is my platform info:
linux-2.4.19, glibc-2.2.4-30, jdk1.4.1-rc-b19, tomcat4-4.03
Here is the JVM message:
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0x6C6C75
Function=[Unknown.]
Library=(N/A)
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.
Current Java thread:
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)
- locked <0x4485f568> (a java.net.PlainSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:439)
at java.net.ServerSocket.accept(ServerSocket.java:410)
at org.apache.catalina.core.StandardServer.await(StandardServer.java:293)
at org.apache.catalina.startup.Catalina.start(Catalina.java:794)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:681)
at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243)
Regards,
Steven Chan

Hi Steven
Also post this question at http://www.javaranch.com , there is a special forum for Apache/Tomcat.
Regards.

Why would FCP crash when i click within the effect window?

Why would FCP crash when I click within the effect window?

I have an old system, but have not had this problem before.
It is a MAC G5 tower...
FCP 5.1.4
MAC OS X version 10.4.``
Quicktime 7.6.4

Why does LabView crash when I run it in parallel with a temp/ RH logging probe?

I am running LabView 6.1 on windows 95. Up till now I have had no problems. However, we recently acquired a Temperature / Humidity probe which plugs into the Com1 port of the computer and logs the data using it's own software. Since then, when the two programs are used together, eventually LabView crashes with the following error message: Failure, 'image.cpp, line 5793.
Can you tell me why this occurs and what the solution is?

Taking a shot at this. It could be because the two programs are trying to access the same type of logging program(excel??). Only one link can be active at a time or they crash. Try running it without saving the data and see if it crashes.

LabVIEW crashing when running NI-DSP VI on Windows XP

Similar Messages

Maybe you are looking for