after close my exe,crash occured 0xc0000005

[Yuanxj]

KEY_VALUES_STRING: 1

    Key  : AV.Fault

    Value: Read

    Key  : Analysis.CPU.mSec

    Value: 10531

    Key  : Analysis.Elapsed.mSec

    Value: 255651

    Key  : Analysis.IO.Other.Mb

    Value: 31

    Key  : Analysis.IO.Read.Mb

    Value: 15

    Key  : Analysis.IO.Write.Mb

    Value: 95

    Key  : Analysis.Init.CPU.mSec

    Value: 2390

    Key  : Analysis.Init.Elapsed.mSec

    Value: 105983

    Key  : Analysis.Memory.CommitPeak.Mb

    Value: 193

    Key  : CLR.BuiltBy

    Value: NET48REL1LAST_C

    Key  : CLR.Engine

    Value: CLR

    Key  : CLR.MissingMetaData

    Value: clr!g_pConfig

    Key  : CLR.Version

    Value: 4.8.4515.0

    Key  : Failure.Bucket

    Value: NULL_INSTRUCTION_PTR_INJECTED_CRASH_c0000005_lvrt.dll!Unknown

    Key  : Failure.Hash

    Value: {22c98b3c-6c00-0716-970b-eac6365079a7}

    Key  : Timeline.Process.Start.DeltaSec

    Value: 403

    Key  : WER.Process.Version

    Value: 1.0.0.32

dmp file is attached

please help me, any help are appreciate

[zou]

Are you making dll call in your VIs?

[billko]

---

@zou wrote:

Are you making dll call in your VIs?

---

Just to expand a bit on this, some instrument drivers make calls to dlls.

[Jacobson]

If I'm interpreting the dump correctly it looks like it's trying to execute the function at 0x0 which would be an issue. Without the PDBs you can just tell that the functions before that are from lvrt so not sure there's much information to be gained from just looking at the dumps.

Even if you had the appropriate symbols there's a good chance there isn't enough information in the dump itself.

[Yuanxj]

yes,ZLG-CAN uses DLL

it has CAN:ZLG(周立功),RT,PLC

[zou]

You need to check dll calls to make sure NO null pointer pass to them.

[Yuanxj]

I will reduce the drivers one by one to see which driver reports the error

[Yuanxj]

its ZLG-CAN（周立功），after i remove ZLG，crash not occured

[rolfk]

---

@Yuanxj wrote:

its ZLG-CAN（周立功），after i remove ZLG，crash not occured

---

There are a number of possible culprits.

The most likely is that whoever wrote the VIs that call the DLL functions made one or more errors in configuring the Call Library Node or is not handling data buffers or data types correctly.

The second is a bug in the DLL.

The third is a bug in LabVIEW.

Depending on the C experience of whoever wrote that LabVIEW wrapper, chances for the problem to be in there is anywhere from 50% to 99% with the reminder being almost completely a bug in the DLL. While bugs in LabVIEW do exist it is in the field of using the Call Library Node extremely rare in comparison to the other two reason!

[zou]

ZLG-CAN driver and its wrapper VIs are widely used.  It's unlikely the culprit.

@Yuanxj

There are many post about ZLG-CAN driver.  See if you can find some examples.