An error with labview

[hallwang]

Last Friday my computer crashed when I was using labview Daqmx. After that,
each time I start Labview, a message box poped up saying:
"The last time you ran labview, an internal error or crash occured at lvexcept.cpp, line 127. "

Then I received another message:
An exception occurred within the external code called by a call library function node. This might have corrupted labview's memory. Save any work to a new location and restart labview. VI"GSW_Main.vi" was stopped at node "" at a call to "NI_FileType.lvlib:GetFileType.vi".

I reinstalled labview several times, but the error still exists.

Below is the log file of the error:
####
#Date: Sun, Aug 29, 2010 4:17:32 PM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 8.2
#AppKind: FDS
#AppModDate: 07/27/2006 17:08 GMT



.\manager\lvexcept.cpp(127) : DWarn: Caught unknown exception
$Id: //labview/branches/Europa/dev/source/manager/lvexcept.cpp#7 $
0x004730F0 - LabVIEW <unknown> + 0
0x00473869 - LabVIEW <unknown> + 0
0x004A5F7E - LabVIEW <unknown> + 0
0x007F77C5 - LabVIEW <unknown> + 0
0x00D01F20 - LabVIEW <unknown> + 0
0x058D40E7 - <unknown> <unknown> + 0
0x042A6FBC - <unknown> <unknown> + 0
0x00C4BE60 - LabVIEW <unknown> + 0
0x000594EC - <unknown> <unknown> + 0

How could I fix my labview? Must I format my harddrive? Thank you.

Hall

[Vt133]

Hello

I had the same error last week, also lvexcept.cpp(127).

There was a corrupt file in my project directory. I tried to copy the hole directory in the windows explorer, but it doesn't work. The projects main VI was corrupt (CRC error). So I have copied the good files, and recover the bad one from an older version.

 Then I have started LabVIEW by doubbleclicking another (good) project in the windows explorer. This was successful. After that I have started the bad project - also successful.

I have lost 1 day with this error.

Regards, Vt

[hallwang]

Hello Vt,

Could you please tell me which files you copied?

The project files or labview lib files?  I didn't find the CRC file you mentioned.

Thanks.

Hall

[jareds]

Hi Hall,

When the first message comes up what option do you select?  Is this when starting LabVIEW by double-clicking a project or VI or by opening LabVIEW fresh?  When you've reinstalled LabVIEW, have you reinstalled the DAQmx drivers?

[hallwang]

Hi Jared,

I choose not to investigate the error when I see the first message. Then the second error message pops up. This occurs no matter how I start Labview.

I only reinstalled LabView, not the DAQmx drivers.

However, if I delete my recent opened files or move them or rename them, LabView could start as normal. Is this a bug with LabView?

I am using Labview 8.2

Hall

[jareds]

Hi Hall,

I'm unaware of a bug that would do this consistently.  You may want to try reinstalling the DAQmx drivers just to be sure that everything is clean.  Also, can you tell us a little bit more about the computer you're working on?

[hallwang]

Hi Jared,

My computer is from Dell. The OS is Windows XP home edition.

The CPU is P4 2.6GHz. The memory is 1Gb. What else details do you need?

Hao

[jareds]

Hi Hall,

That should be fine.  I just wanted to make sure the computer was properly set up for this.  You mentioned that you can start LabVIEW after deleting or renaming the recently opened files.  Is this repeatable?  Are you still seeing the issue after doing this?  Once LabVIEW is up, can you open any of the recent files if you renamed them?