CVI crash in Win2000

Hi there,
I've got a serious problem:
System:
- new laptop (ACER 522 TX) with Win2000 German preinstalled
- CVI 5.5 is the only app that is installed on that machine
- CVI 5.5 Servicepack 1 is installed
Problem:
CVI works correctly (edit / compile...) but:
- compile menudemo.prj for debugging (or any other project with menus): OK
- run menudemo from the IDE: OK
- open menus: OK
- open the file open menu entry: SYSTEM CRASH
- compile menudemo for release and start it from the IDE: same behaviour
- run menudemo from the prompt: everything works correctly!
SYSTEM CRASH means:
An empty window opens; hourglass mouse cursor. The mouse cursor
can still be moved. No other Win2000 application can be
started. Occasionally I can click the X butt
on to close the window,
but I will only get a message that I try to kill a running application; this
window is equipped with two incomplete buttons. Pressing
Ctrl-Alt-Del causes the system to hang completely,
the mouse can't be moved anymore. I can only turn off
the system by the shutting down the power.
I've tried to install CVI 5.5 on Win98SE and WinNT4.0 on the
same machine: no problems! Somehow it seems as if Win2000
handles the file open dialogs different and CVI is not
capable of dealing with this (I think the text on the package
says: for Win NT AND Win 2000....?)
Hope somebody can help!

Hello Erwin,
Your best bet would be to contact National Instruments email support staff at http://www.ni.com/ask
Please provide us with detailed information about your Windows 2000 system including its detailed hardware and software configuration.
Jeremiah Cox
Applications Engineer
National Instruments
http://www.ni.com/ask

Similar Messages

CVI crashes when calling function from external DLL

I'm calling a CVI library from Test Stand 4.1. In that CVI library I load an external DLL (using LoadLibrary) and create a few function pointers (using GetProcAddress). The DLL loads successfully, and I get addresses for all of the imported functions.
However, when I one of the functions is called CVI crashes (Test Stand says it lost the ActiveX connection to CVI) when executing in an external CVI instance. If executed in the Test Stand process I get a system level exception.
If I step through the code in CVI, it hangs after trying to step into or over the call to the function pointer from the external DLL.
I am able to call the functions in a small test project I created in CVI, however when integrating it into an existing test library and calling it through Test Stand it fails.
Any ideas on how to go about debugging this issue?

Have you tried calling into the dll that CVI calls directly from TestStand? I am curious to know if this also crashes.
I am also curious to know if there are any path references in the dll that is called by the CVI program. If so are they relative, or absolute paths?
I ask because one of the possibilities is that relative paths are being used to specify a path from the location of the code that is called, and they are not working because the current working directory is being specified by TestStand, and the paths are not relative to the working directory given by TestStand.
Jensen
National Instruments
Applications Engineer

CVI crashes when compiling with VISA

LabWindows/CVI does not compile when I try to use VISA:
For a very simple program (only UI, no multithreading, instrument communication whatsoever), when I include "visa.h", it does not compile anymore and crashes occasionally:
- When I hit "Compile File", it states "A custom callback raised an exception.".
- When I hit "Debug Project" (green Triangle), CVI crashes without explanation.
VISA itself seems to work fine, since I can do basic communication with a USB-connected oscilloscope by using [Tools > Create Instrument I/O Task"] as well as generic VISA Interactive Control.
CVI itself seems to work fine, too, since I can compile & run programms which for example use direct access to GPIB without VISA.
I'm running: Windows 7 (64bit AMD), LabWindows/CVI 9.1.0. (428), VISA Interactive Control (5.0.3 / 4.0).
Thanks in advance..
asIHM
Solved!
Go to Solution.

Hi
try to repair of your CVI installation by choosing Control Panel » Add or Remove Programs » National Instruments Software and opting to repair the Development System that you have
installed.
Select National Instruments Software and click Change/Remove. This will open a new window with all of the National Instruments software you have installed on your computer.

IviSwtch Compliance Test IVI Specific Driver in CVI crashing

I have problem with IviSwtch Specific driver. I have finished all code for this driver and try to test in CVI tool called "Test IVI Specific Driver". Structure and Function panel test runs without any error. Problem is with Compliance test which returns:
the driver could not be initialized through the class driver.
Compliance Test was halted.
Error returned: bffa0011
Error Message: Function or method not supported.
I tried to add exports to dll in according to this solution http://digital.ni.com/public.nsf/allkb/1DCA138862E75119862576C5006EA144
After doing this Compliance test just crashing and I have to close it down.
Does anybody met this kind of problem? I would be grateful for any help.
Regards
Tomasz
Solved!
Go to Solution.

>>The DLL version format is valid.
ERROR: The DLL version is inconsistent with the version in the header file.
All attributes have correct names.
All attributes have correct data types.
This error means the revision of the generated <driver_prefix>.dll does not match the Major and Minor version defined in header. This should not be a conern if you will not release the driver to customers and you take care of revision.
>>ERROR: The driver is not c>ompliant with the Inherent group because:
-The following Inherent attributes are not implemented:
INSTRUMENT_MANUFACTURER
INSTRUMENT_MODEL
It is hard to tell the root reason of this issue, but there might be something doesn't work in your code. How about post these attributions' definition? OR send your project to [email protected] I think NI could help to take a look into it.
Thanks,
Charles

CVI crashes - event log shows [FATAL] [LW_UAE_Handler] [..\jeff\i386\except.c:161] Assertion failed: 0.

Hello,
When calling lua_error(L) (pushing a Lua error in an embedded lua interpreter in my CVI code), I have been encountering a complete crash. Not only does my code stop running, but the full CVI 9.1.1 IDE crashes without even an error message. When I look in the windows xp event log I find the following:
The description for Event ID ( 0 ) in Source ( CVI ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [16:45:30.768] [FATAL] [LW_UAE_Handler] [..\jeff\i386\except.c:161] Assertion failed: 0.
When I recompile my project with visual studio, the identical code does not crash or cause any problems. Any insite on this problem would be greatly appreciated.
thanks,
Alex Corwin

Hello Alex,
Could you try to generate a crash dump? Also, here is a community example of code using an embedded interpreter LUA in a LabWindows/CVI Project.
Regards,
Jeff L.
Applications Engineer | National Instruments

Java Plug-In 1.4.1 Crashes in Win2000 IE6.0.2600

Hallo
Please can somebody help with information on why the Java Plug-in ver 1.4.1 just crashes when I try to run an applet under windows 2000 Professional using IE6.0.2600. Also I cannot run the Java Console nor the Java Plug-in Control panel, all of which crash or do nothing. The console shows signs of wanting to run by displaying its window by it never completes this process and then it crashes, killing the browser in the process. When it does this, it resets the Internet Option "Java Console ENabled" in IE Internet Options>Advanced>Microsoft VM.
Why cant I run the Java Console, the Java Plugin Control Panel or any applet no matter how simple.
Any help will be greatly appreciated!!!
Thanks

I have the same machine configuration and Java Plug-in reboots my machine when download my application from a website. It also reboots machine when i click on 'Get Update' button on the Java Plug-in Control panel. Please help.
Dose anybody know how to report this Critical bug to Sun.

Breakpoints cause CVI to crash

I am using LabWindows CVI version 8.1.0. When I set a breakpoint and run the debugger the program will stop at the breakpoint, but when I click on "GO" CVI crashes. I can't get back to my application window. I can switch back and forth between the project window and the source code window but the project window doesn't work right. Clicking the "x" in the upper right corner of the window just gives me the Microsoft error message "Program not responding". On the same computer I also have an older copy of LabWindows CVI version 6.0.0 which behaves exactly the same. What happened and how do I fix it?

Rebooting the computer fixed the problem.

Cvirte.dll application crash

When running CVI full interface operator interface I receive the following error:
AppName: testexec.exe      AppVer: 1.0.0.0     AppStamp:4f2c478b
ModName: cvirte.dll      ModVer: 9.1.0.428      ModStamp:4b566705
fDebug: 0       Offset: 0012c87e
I have even rebuid the applicaiton and the crash still happens. Using LabWindows 8.5 (lower right corner displays 8.5.1 (356)) and TestStand 4.1.
Any suggestions to resolve the error?
Thanks
RK.

On further inspection, the .NET error event may be a red herring, or a second bug. Let's look at the CVI crash first. The information provided so far looks like you may be hitting a bug in our run-time engine, but we do not have enough information to find which one. Could you create a crash dump and send it to us. Instructions for Windows XP copied below:
If you have been using a program other than Dr. Watson as your default debugger, such as Visual C++ or you were not using any debugger:
Go to Start » Run
Enter drwtsn32 -i to install Dr. Watson as the default debugger.
By default the utility only creates the Dr. Watson log file (drwtsn32.log). You have to instruct Dr. Watson to create a crash dump when an application crashes. Launch the Dr. Watson:
Go to Start » Run.
Enter drwtsn32
Make sure the Create Crash Dump File is checked and make a note of the path specified in the Crash Dump edit box. Default Paths:
Windows XP: C:\Documents and Settings\All Users\Documents\DrWatson\user.dmp
The dump file may be too large, so you can upload it to ftp://ftp.ni.com/incoming and let me know the file name.
Addtionally, it is possible that if this is a bug, it may have been fixed in a later release of the CVI Run-Time Engine. I would recommend downloading and installing the latest version from CVI Run-Time Engine 2010 SP1. The CVI RTE is fully backwards compatible and will run your application. It could also be helpful if we then know if this is a bug that has been fixed or if we are dealing with a new bug.
National Instruments
Product Support Engineer

Need help with an error report

Attached is an error report from a VI that normally crashes with Error Checking set to Default in the VI's LCFN configuration dialog box. Can't debug it when it crashes; LabWindows CVI comes up for debug but CVI crashes too.
The attached error report was only available after setting Error Checking to 'No Error Checking'.
Any ideas what's going on with this DLL function called by the LCFN?
Platform: Windows 7-32 + LV2013 Pro SP1-32.
Jeff
Jeffrey Bledsoe
Electrical Engineer
Solved!
Go to Solution.
Attachments:
1607b431-02ef-4672-a138-c2ebc4a16c2b.zip ‏20 KB

Connor,
Sorry, I meant CLFN.
This isn't an executable.
It's good LV2009 code (ran okay with LV2009) that I'm trying to execute with LV2013. I ran a mass compile on all the VIs.
I posted this issue a few months ago when using an evaluation copy of LV2013 but have only recently begun looking at it again after I installed our purchased copy of LV2013.
I can prevent LV crashes from this VI by changing its calling convention from "C" to "StdCall." However, the value returned from the DLL function is invalid. While the DLL function returns an invalild value, I added "unbundle by name" VIs to the error stream on the input and the output of the CLFN. Results: the error 'code' at the input and the output of the CLFN = 0.
The supplier of the DLL said the DLL functions are written in either C or C++. I've found notes at ni.com that indicate a "Wrapper DLL" (written in C) might be required to provide a "C to C++" translation interface between the CLFN and the DLL functions.
Another approach I've found on ni.com appears to be replacing the CLFN with a Code Interface Node (CIN) having C code to interface LV with the C++ code of the DLL function, thus eliminating the CLFN.
There are also some notes on ni.com concerning CLFN settings causing crashes in the LV2009 to LV2010 transition; apparently, other changes between LV2010 and LV2013 are causing my issue.
The supplier of the free DLL now has a LV developers kit (for purchase) that might solve these issues but we can't go that route.
Thanks,
Jeff
Jeffrey Bledsoe
Electrical Engineer

When using the new controls of CVI 7 in my DLL it crash on the DisplayPanel call

I have a CVI DLL that was build under CVI 6. When I recompile it in CVI 7 everything works fine when I load the DLL from my application. But If I add a button on my uir file with the new CVI 7 style (no event code associated, just a plain button) my DLL crash and hang my main application on the DisplayPanel call. If I don't use the new controls (use the classic-style controls) everything works fine. I use LoadPanelEx to load my uir file. The returned panel handle is good (> 0) But when I call DisplayPanel it doesn't show me any error but just crash my DLL and jump back in the DLLMain function saying that my process is detaching and hang my main application.
I am running on Win2k. I have
LabVIEW 7 and LabVIEW 6.0.2 installed also. The main application that calls the DLL is made in Delphi 6.
I have re-installed the run-time engine from the CDs but this didn't do the trick. Is there something else that I must include with my DLL to use thoses new controls styles. The DLL is running from the same place where it was build.

Hi,
I have created another cvi DLL and it create the same behavior in my application (crash on DisplayPanel). But if I do a standalone CVI executable with thoses new buttons everything is fine. Also I have created another application(in Delphi) to load the cvi-dll and it works fine in that one. So I would tend to say that it is in my application but on the other hand everything works fine if I don't put thoses LabStyle controls...Weird I know...
In shorts It is just crashing with a specific application but for any UI project that I create. If I don't put thoses buttons everything is ok...Any other advises would be helpful because I'm kind of out of ideas...
Gilles Hache

Crash in application by using TestStand 4.0 and CVI labWindows 8.01

Our application often crashes in two areas:
1) Often crash in the case:
    During running, if there is poop, like error message, you want to debug by opening other programs,like notepad.
    It shows error signature:
    AppName: operator Interface.exe     AppVer. 4.0.0.326, ModName cvirte.dll
    ModVer: 8.1.0.271         Offset : 000b9c8a
2) Often crash at the end of test, when generating TSV file.
     AppName: operator Interface.exe     AppVer. 4.0.0.326, ModName msvcr80.dll
    ModVer: 8.0.40727.762       Offset : 00008a8c
We use TestStand 4.0 and CVI LabWindows 8.01. The program is running in our customized operator interface.
But I tried using the default TestStand operator interface, it crashed too.
Also we found it is related PC too. One PC in our lab crashed often, but it actually newer PC with bigger RAM. (Pentium(R) 4 CPU 3.2GHz), 3.19GHz, 0.99 GB of RAM)
The one crashed Less often is Pentium(R) 4 CPU 2.80GHz, 2.79 GHZ 504 MB of RAM.
Hope you can help us to find out root cause.
Thanks

Hi Doug,
Thanks for your reply.
Answers to your queries:
1. We are not calling any DLLs from our sequences.
2. We are only using LabVIEW modules and the VIs are called under LabVIEW development environment and not using Run Time engine.
3. In our case it is always seqedit.exe which crashes. LabVIEW never crashed. Hence I think its TestStand whose memory is getting corrupted.
We are trying to narrow down the issue as suggested by you.
By the time, we have observed a strange thing while the sequence editor crashed.
In our sequence we call a thread which calls a VI to run continuously and collect the data from other modules.
What we observed is that, when the sequence editor crashed (the popup appeared), it was still executing the sequence (running a loop). I was able to break the execution and debug it. All the variables were also having proper values.
But the VI which was running in a separate thread was in surprising state. That VI was showing as executing but actually it was not running any of its code. I tried to put probes inside that VI but they were not updated (meaning that part of code was not runnning). I tried to stop the VI using the abort button but no help. It was not having any effect. I also clicked on the Pause button. The button turned red but the VI didn't halt at any part of code (actually the VI was not at all executing). An other VI which was called by another thread was working properly. I could see it by putting probes in that VI.
If your thought about the memory corruption is correct, is it possible that this VI is somehow corrupting the sequence editor memory?
I am not sure, but I think wherever the sequence execution may be, but the above mentioned VI is always in this state at the time of crash.
I tried to reproduce this scenario locally but it ran without problem for hours
Probably I am still not able to properly reproduce it. I'll work on it further and let you know the outcome.
Regarding your last question, We are using LabVIEW notifier. A VI is called which waits on LabVIEW notifier from another VI. That code is pretty simple it just obtains a notifier and waits on it indefinitely.
Please let me know your views on the above mentioned issue.
Thanks,
- Kaustubh

CVI dll crashes when it uses RefNum var passed in from other CVI code or from LV 2009. Why?

Hi, all--I am pretty much a LabVIEW beginner, but starting to dry a little behind the ears. Currently working on a project where the original LV code called VC CINs. We want to convert the CINs (lvsbutil.exe--ick) to Call Library Function nodes and so I am working to convert the CIN code to a DLL. Finally got everything compiled happily and went to run my VI calling the DLL--as far as I could tell, at the DLL call, CRASH! So then, I fiddle around making a CVI main that I can use to call my crashing DLL(debug mode) from and I find the crash happens when I call FRefNumToFD, even though the RefNum seems to be legit. I even tried inserting FIsARefNum in front of the conversion routine, and FIsARefNum crashes now too. Is there a problem with these file manager functions? Is there something freaky with RefNum passing between CVI and LV?
I am using CVI 9.0 and LV 2009. Thanks for all input!

OK: here is a screen shot of my vi, and some of the code from my CVI dll--
//#include "extcode.h"
#include "ShareLib_ProcessEF.h" //The commented out stuff is in this header file
/*typedef struct
int32_t dimSize;
uint16_t elt[1];
} TD1;
typedef TD1 **TD1Hdl; */
#define CHECKSUM ChecksumNew
extern void CHECKSUM (uInt8 *pData, int32 Size, uInt16 *pXOR, uInt16 *pChk_sum);
uInt8                 **hRead_buf;
int32 __declspec(dllexport)ProcessEFBlock(LVRefNum *hFile, uint16_t *pChksum, uint16_t *pXOR, TD1Hdl hData_block,
TD1Hdl hHdr_block, LVBoolean *pEOF, LVBoolean *pDLOK, LVBoolean *pSEND);
int32 __declspec(dllexport)ProcessEFBlock(LVRefNum *hFile, uint16_t *pChksum, uint16_t *pXOR, TD1Hdl hData_block,
TD1Hdl hHdr_block, LVBoolean *pEOF, LVBoolean *pDLOK, LVBoolean *pSEND)
MgErr                 mgError;
File                  fd;
int32                 byte_count;
uInt8                 size_buffer[2];
int32                 read_buf_size;
int32                 offset;
uInt8                 *pRead_buf;
uInt16                *pData_buf;
uInt16                tmpChksum;
int32                 i;
uInt16                fill_count;
int32                 DataBlockSize;
uInt8                 **hTemp_buf;
uInt8                 *pTemp_buf;
uInt8                 fill_byte;
BYTEWORD              byteword;
BYTELONG              bytelong;
Bool32    iRefNumErr;
mgError = 0;
// Convert file reference to file descriptor
iRefNumErr = FIsARefNum(*hFile); //This is where the code leaves to think things over
if (mgError = (FRefNumToFD (*hFile, &fd)))
    goto out;
} // if
Attachments:
dll_call.jpg ‏45 KB

CVI.dll crashes 2013 when trying to browse

If I attempt to anything that requires a browse/file select LabWindows crashes with the following report:
Problem signature:
Problem Event Name: BEX
Application Name: cvi.exe
Application Version: 13.0.0.632
Application Timestamp: 51cb679b
Fault Module Name: CVI.dll
Fault Module Version: 13.0.0.632
Fault Module Timestamp: 51cb6792
Exception Offset: 00a4bb50
Exception Code: c0000409
Exception Data&colon; 00000000
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional Information 1: 7d8b
Additional Information 2: 7d8b59960e847456f719cf8b76eb40a7
Additional Information 3: 1aa0
Additional Information 4: 1aa00fb74513a107a85e25616fae3f2c
Cannot add existing files to project, open new project or open workspace.
Started after loading NI-VISA.

Hi jimbrown60,
Do you see this problem after upgrading to LabWindows/CVI 2013 SP2?
Can you provide system information such as OS, OS-bitness, other software currently installed?
Have you tried running LabWindows/CVI as an Administrator (i.e., right-clicking LabWindows/CVI and selecting Run as administrator)? Does this cause a change in behavior?
Are there any errors logged in Windows Event Viewer? If so, could you clear the event log, reproduce the issue, and send the list of events logged?
Thanks,
Daniel D.
National Instruments
Automated Test Software R&D

Appserver 7.0 crashes every time I logout console on Win2000

Hi all,
I use appserver on a few Win2000 Servers. Everything works fine except that appserver crashes every time I logout Windows console on any server.
I receive the message in the Event Viewer:
Server: SunAppServer7.0-domain1_server1 CORE0125: The server terminated abnormally with error code 0. An attempt will be made to restart it.
After restarting the appserver works as usual until next logout.
What's the matter?

Welcome to the forum.
Unfortunately, you have posted to the Tip & Tricks Forum, and few will see your post here. I will try to have it moved to the main PrE Forum.
I would start with this ARTICLE, which begins with a checklist on getting PrE setup on one's computer. It then goes into steps to tuneup the computer, and OS, and finishes with many links to help one troubleshoot issues.
Good luck,
Hunt

CVI 9.1.0 crashes when looking at variables window

I get the following crash when I have my program at a breakpoint and I pop open the variables windows and try to scroll down to see my globals:
EventType : BEX     P1 : cvi.exe     P2 : 9.1.0.427     P3 : 4afcd035
P4 : cvi.dll     P5 : 9.1.0.427     P6 : 4afcdb5b     P7 : 009d730e
P8 : c0000409     P9 : 00000000
Can anyone help with this?

I am getting the exact same crash every time all of a sudden. It seems to occur now that I've created a viSession variable and viFindlist variable..
My main looks like:
int main (int argc, char *argv[])
int error = 0,j;
static short addrList[31];
static short listList[31];
static int portList[255];
int nPorts,index;
char port_name[7];
ViSession resourceManager;
ViFindList findList;
char desc[256];
int numDevices;
/* initialize and load resources */
nullChk (InitCVIRTE (0, argv, 0));
errChk (instHandle = LoadPanel (0, "Test Application Generator.uir", INST_SETUP));
/* display the panel and run the user interface */
errChk (DisplayPanel (instHandle));
/*for (j=0;j<31;j++) {
addrList[j] = j;
addrList[30] = -1;
SendIFC(0);
FindLstn(0,addrList,listList,30);
//Get list of available COM ports
nPorts = LocateCom("",portList,255);
for (index = 0; index < nPorts; index++) {
sprintf(port_name,"COM%d",portList[index]);
InsertListItem(instHandle,INST_SETUP_PORT_TYPE,-1,port_name,index); //Add to list
index = viOpenDefaultRM(&resourceManager);
viFindRsrc (resourceManager, "?*INSTR", &findList, &numDevices, desc);
errChk (RunUserInterface ());
Error:
viClose(resourceManager);
/* clean up */
DiscardPanel (instHandle);
//DiscardPanel (mainPanel);
return 0;
And I have a break on the viOpenDefaultRM function so it hasn't been ran. And my variable looks fine except the variable resourceManager is blank.

CVI crash in Win2000

Similar Messages

Maybe you are looking for