10-13-2016 10:31 AM - edited 10-13-2016 10:41 AM
Hi All,
I am facing this non continuable exception but i have no idea how to solve it (searched the forum)
it happend once in around every one hour and half and at vi which run three instrument at the same time
Agilent SMU (VISA)
Radiant Colorimeter (.NET)
Thorlab Spectrometer (VISA)
i would like to get general idea what cause before i posting more code (because my code is a bit complicated to post)
here is the log but i dont think it got any useful information
####
#Date: Wed, Oct 12, 2016 3:14:15 PM
#OSName: Windows 7 Professional Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: LabVIEW
#Version: 14.0.1 64-bit
#AppKind: FDS
#AppModDate: 1/25/2015 01:33 GMT
#LabVIEW Base Address: 0x0000000140000000
InitExecSystem() call to GetCurrProcessNumProcessors() reports: 8 processors
InitExecSystem() call to GetNumProcessors() reports: 8 processors
InitExecSystem() will use: 8 processors
starting LabVIEW Execution System 2 Thread 0 , capacity: 24 at [3559101258.71461630, (15:14:18.714616299 2016:10:12)]
starting LabVIEW Execution System 2 Thread 1 , capacity: 24 at [3559101258.71461630, (15:14:18.714616299 2016:10:12)]
starting LabVIEW Execution System 2 Thread 2 , capacity: 24 at [3559101258.71461630, (15:14:18.714616299 2016:10:12)]
starting LabVIEW Execution System 2 Thread 3 , capacity: 24 at [3559101258.71461630, (15:14:18.714616299 2016:10:12)]
starting LabVIEW Execution System 2 Thread 4 , capacity: 24 at [3559101258.71461630, (15:14:18.714616299 2016:10:12)]
starting LabVIEW Execution System 2 Thread 5 , capacity: 24 at [3559101258.71461630, (15:14:18.714616299 2016:10:12)]
starting LabVIEW Execution System 2 Thread 6 , capacity: 24 at [3559101258.71461630, (15:14:18.714616299 2016:10:12)]
starting LabVIEW Execution System 2 Thread 7 , capacity: 24 at [3559101258.71461630, (15:14:18.714616299 2016:10:12)]
Thread consumption suspected: 3 Try starting 1 threads
starting LabVIEW Execution System 2 Thread 8 , capacity: 24 at [3559102325.17161420, (15:32:05.171614171 2016:10:12)]
Thread consumption suspected: 5 Try starting 1 threads
starting LabVIEW Execution System 2 Thread 9 , capacity: 24 at [3559105310.25035140, (16:21:50.250351429 2016:10:12)]
<DEBUG_OUTPUT>
10/12/2016 4:27:56.514 PM
Crash 0x00000000: Crash caught by NIER
File Unknown(0) : Crash 0x00000000: Crash caught by NIER
minidump id: 0dc45c44-f677-4a38-88d6-0f9664e6e763
ExceptionCode: 0xC0000025
</DEBUG_OUTPUT>
0x000000018000120E - nierInterface <unknown> + 0
0x0000000180006422 - nierInterface <unknown> + 0
0x0000000180006A7A - nierInterface <unknown> + 0
0x000000006F3A52B9 - MSVCR90 <unknown> + 0
0x000000006F3A5315 - MSVCR90 <unknown> + 0
0x000007FEE92C48F1 - <unknown> <unknown> + 0
0x0000000019B26200 - <unknown> <unknown> + 0
0x0000000028EA4E30 - <unknown> <unknown> + 0
0x00000000101AF6A0 - <unknown> <unknown> + 0
0x0000000002020080 - <unknown> <unknown> + 0
0x0000000019B26200 - <unknown> <unknown> + 0
0x000007FEE92C4929 - <unknown> <unknown> + 0
0x0000000000000001 - <unknown> <unknown> + 0
0x000007FEE92C4063 - <unknown> <unknown> + 0
0x00000000101AF7C0 - <unknown> <unknown> + 0
0x000007FEE92C291E - <unknown> <unknown> + 0
0x00000000101AF7C0 - <unknown> <unknown> + 0
0x00000000101AF7D0 - <unknown> <unknown> + 0
0x00000000775103C8 - ntdll <unknown> + 0
0x000007FEE92C40B1 - <unknown> <unknown> + 0
0x00000000101AF7C0 - <unknown> <unknown> + 0
0x0000000019B6E460 - <unknown> <unknown> + 0
0x000000002959DE20 - <unknown> <unknown> + 0
0x000007FEE92C194D - <unknown> <unknown> + 0
0x000000002959DE20 - <unknown> <unknown> + 0
0x0000000019B26200 - <unknown> <unknown> + 0
0x000000002959DE20 - <unknown> <unknown> + 0
0x0000000019B26200 - <unknown> <unknown> + 0
0x000007FE00000001 - <unknown> <unknown> + 0
0x00000000101AF6F0 - <unknown> <unknown> + 0
0x00000000101AF6D0 - <unknown> <unknown> + 0
0x000007FEE92C2504 - <unknown> <unknown> + 0
0x00000000101AF7C0 - <unknown> <unknown> + 0
0x00000000101AF6C0 - <unknown> <unknown> + 0
Solved! Go to Solution.
10-13-2016 04:24 PM - edited 10-13-2016 04:29 PM
Oh, dear -- the dreaded "We apologize for the inconvenience" message. This is an internal LabVIEW error, often because something has gone wrong in the compiled code, possibly a memory leak or something like that. Usually it is a subtle bug, and the best (and almost only) way to eventually get it fixed is to send the Report to NI, with a followup call to LabVIEW Support (the response will not be rapid)!
You are working in the most problematic situation, 64-bit LabVIEW and doing Data Acquisition of some sort, meaning you need also 64-bit driver support. I'm told this sometimes works, and is gradually getting better ...
Your code really is a little complicated. Have you tried simplifying it and testing individual modules to make sure that isolated sub-systems work properly? Have you created a document that describes the overall organization of your code to help you (and perhaps a consultant, or those of us looking at your code in the Forum) understand not only the flow of data, but which sections are critical and which can take a little time without messing your up? In particular, do you know where you need to take advantage of LabVIEW's parallel architecture by writing loops that run asynchronously, like Producer/Consumer pairs?
You will help yourself a lot if you start encapsulating your code into sub-VIs, perhaps even nested several levels deep. Try to get your design such that no VI takes more screen space than a modest Laptop screen. In particular, your Top Level VI should consist of a few loops that say something like "I AM A STATE MACHINE" and have 10-20 32-by-32 pixel sub-VI icons (you do make Icons for all your sub-VIs, don't you?) all sitting on the Error Line and hence instantly recognizable for what they do. If the Code appears to be simple and clear (even it if is not, yet), it will be much easier to "find the flaws".
Bob Schor
P.S. -- I do Practice What I Preach -- my Block Diagrams fit on single screens, and a modest Project will have at least 30-50 VIs and TypeDefs. I recently posted a small Demo somewhere in the Forums that had only 20 VIs/TypeDefs ...
10-13-2016 06:46 PM
I agree with everything that Bob said. From my experience, these issues almost only ever get solved once you have a pretty clear cause and effect (I do this action, I crash LabVIEW). Getting there is easier said than done but I would second sending in a report (preferably many reports) and calling support because every once in a while you'll get lucky and find the silver bullet from the dumps.
On a hunch, I would start testing the Radiant Colorimeter module. I'm not an expert by any means but the dump is listing a lot of <unknown> modules which I would guess is code external to LabVIEW and you mentioned the colorimiter is controlled using a .NET API. I looked at some crashes on my computer and while it won't tell you the function it's running without the necessary symbols, you should see the module (like LabVIEW or LVRT). The fact that it's unknown would make me think that it's in the process of running some external code. I wouldn't take the above for fact but it's as good a place to start as any.
Some other general questions that help get more context are
10-17-2016 03:36 AM - edited 10-17-2016 03:40 AM
Hello Jacob, thank you for your reply
10-17-2016 03:42 AM
Hello Bob,
sorry for the messy vi, it is too costly to reorganised now
I hope to get general idea on what is happenning now
10-17-2016 04:08 AM
03-23-2017 05:35 AM
Hello Guys,
I would like to update the status here
I think i finally have some clue what is going on
nomally when i build exe i use my computer which has vision module 2016 installed, while the on site computer using vision module 2015
i didnt notice any crash for two days using exe built from the on site computer (normally will crash few times per days)
my question is, is it possible that different version of module the cause of the random crash?
03-23-2017 01:28 PM
still crash afterward, seem like it is not related to vision module
however i do found something regarding gc collect (i use gc collect in 4th picture), it seem like it is a not safe function to use, i will try to disable it and keep monitoring
03-27-2017 11:02 PM - edited 03-27-2017 11:03 PM
Hello Guys,
I finally found the root cause of the problem, it is caused by asynchronous VISA in 64bit environment
switch to synchronous VISA will solve it (sacrificing some performance)
similar cases
https://lavag.org/topic/18562-visa-write-read-to-usb-instruments-in-parallel-crashes-labview/