2011SP1f1 crash

[instrumento]

Labview 2011SP1f1 64 bits crashes repeatedly on one of our programs (too large to post, calls a couple of external DLLs).

Windows 7 catches the crash and posts the event below to the logs.

Any hope to find out what's causing it?

Log Name:      Application
Source:        Application Error
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
Description:
Faulting application name: labview.exe, version: 11.0.1.4015, time stamp: 0x4f7e1ecc
Faulting module name: tdcore_11_0.dll, version: 11.0.0.49155, time stamp: 0x4e973b0b
Exception code: 0xc0000005
Fault offset: 0x0000000000007755
Faulting process id: 0x1760
Faulting application start time: 0x01cd63f8c2d495cb
Faulting application path: c:\progra~1\nation~1\labvie~1\labview.exe
Faulting module path: c:\progra~1\nation~1\labvie~1\resource\tdcore_11_0.dll

[Dominik-E2]

When a VI crashes while using dlls, it is frequently because the paramters that are being passed to the dll are different from what the dll function expects. I would recommend using the “Highlight Execution” to step through your code and seeing where exactly the program crashes. With that information we may be able to get a better idea about how to troubleshoot.

[instrumento]

This is a random crash and not necessarily on our DLL (which works fine in other machines, as it contains the core of some of our code).

Stepping through it is not an option in large programs, and I suspect this is one of those errors where things go puff and disappear.

I'm actually going to run memtest on the machine first, just in case, but was wondering if the event viewer crash report pointing to something, as the error is inside a NI DLL.

[instrumento]

And here is part of the report of two crashes NI err actually caught:

####
#Date: Tue, Jul 17, 2012 2:57:43 PM
#OSName: Windows 7 Professional Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: XXXX
#Version: 11.0.1f1 64-bit
#AppKind: AppLib
#AppModDate: 07/17/2012 20:49 GMT
#LabVIEW Base Address: 0x0000000030000000
 
 
 
7/18/2012 8:27:10.743 AM
DWarn 0xF8FDE404: CopyDataConvert elts=3, eltssrc=2
c:\builds\penguin\labview\components\tdcore\trunk\11.0\source\tdcore\TDCluster.\
cpp(1121) : DWarn: CopyDataConvert elts=3, eltssrc=2
minidump id: c2807856-fc66-40a0-870e-9dee7669cc50
$Id: //labview/components/tdcore/trunk/11.0/source/tdcore/TDCluster.cpp#7 $
0x0000000030090FE9 - lvrt <unknown> + 0
0x00000000309EB535 - lvrt <unknown> + 0
0x00000000309C7C10 - lvrt <unknown> + 0
0x00000000309833C5 - lvrt <unknown> + 0
0x0000000030939CF5 - lvrt <unknown> + 0
0x000000003093A09B - lvrt <unknown> + 0
0x00000000303C4DC2 - lvrt <unknown> + 0
0x0000000030261189 - lvrt <unknown> + 0
0x0000000030222D41 - lvrt <unknown> + 0
0x0000000030261443 - lvrt <unknown> + 0
0x0000000030222A61 - lvrt <unknown> + 0
0x00000000302AAA3E - lvrt <unknown> + 0
0x00000000302298B6 - lvrt <unknown> + 0
0x0000000030248BA1 - lvrt <unknown> + 0
0x000000003029CAD8 - lvrt <unknown> + 0
0x0000000030633FA4 - lvrt <unknown> + 0
0x00000000306350A7 - lvrt <unknown> + 0
0x0000000030635CD6 - lvrt <unknown> + 0
0x000000003063616E - lvrt <unknown> + 0 0x0000000030637E7F - lvrt <unknown> + 0
0x00000000306373D7 - lvrt <unknown> + 0
0x000000003056E79F - lvrt <unknown> + 0
0x00000000307A652B - lvrt <unknown> + 0
0x0000000007CB7D0E - <unknown> <unknown> + 0
0x0000000007CB24F8 - <unknown> <unknown> + 0
0x0000000007CB2480 - <unknown> <unknown> + 0
0x0000000003F18580 - <unknown> <unknown> + 0
0x0000000003F18580 - <unknown> <unknown> + 0
 
7/18/2012 10:01:31.412 AM
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash: Crash caught by NIER
minidump id: 90bd320d-6d20-488e-b966-f52f7d4f14d1
^YExceptionCode: 0xC0000005
0x00000000308FD2EB - lvrt <unknown> + 0
0x00000000308FD570 - lvrt <unknown> + 0
0x0000000076B09450 - kernel32 <unknown> + 0
0x0000000076F843B8 - ntdll <unknown> + 0
0x0000000076F085A8 - ntdll <unknown> + 0
0x0000000076F19D0D - ntdll <unknown> + 0
0x0000000076F091AF - ntdll <unknown> + 0
0x0000000076F41278 - ntdll <unknown> + 0
0x0000000030927315 - lvrt <unknown> + 0
0x000000003093024A - lvrt <unknown> + 0
0x000000003093DB4E - lvrt <unknown> + 0
0x0000000030939CF5 - lvrt <unknown> + 0
0x000000003093A09B - lvrt <unknown> + 0
0x00000000303C4DC2 - lvrt <unknown> + 0
0x000000003025D3DB - lvrt <unknown> + 0
0x0000000030222D41 - lvrt <unknown> + 0
0x000000003025EB64 - lvrt <unknown> + 0
0x00000000302298B6 - lvrt <unknown> + 0
0x0000000030248BA1 - lvrt <unknown> + 0
0x000000003029CAD8 - lvrt <unknown> + 0
0x0000000030633FA4 - lvrt <unknown> + 0
0x00000000306350A7 - lvrt <unknown> + 0
0x0000000030635CD6 - lvrt <unknown> + 0
0x000000003063616E - lvrt <unknown> + 0
0x0000000030637E7F - lvrt <unknown> + 0
0x00000000306373D7 - lvrt <unknown> + 0
0x000000003056E79F - lvrt <unknown> + 0
0x00000000307A652B - lvrt <unknown> + 0
0x000000000A5AC39F - <unknown> <unknown> + 0
0x000000000811AF00 - <unknown> <unknown> + 0
0x0000000008111700 - <unknown> <unknown> + 0
0x00000000307A670F - lvrt <unknown> + 0
0x0000000003F18580 - <unknown> <unknown> + 0
0x000000000811AE80 - <unknown> <unknown> + 0

[GuenterMueller]

---

@instrumento wrote:

This is a random crash and not necessarily on our DLL (which works fine in other machines, as it contains the core of some of our code).

---

How long do you usually have to wait for a crash?  Minutes? hours? 

Identifying the culprit might be quite tedious.  However I would consider

- writing to a logfile before and after each DLL call.  If is is not the DLL the logfile should contain always pairs of entries (e.g. "before" and "after").

- Setting the "Error Checking Level" for all Call Library Function Nodes to "Maximum".  (I have never faced a scenario to benefit from this setting so I have not seen LabVIEW's behaviour in case of an error.)