Kyoto

We got a response from our customer that the appcrash errors (in the event viewer) are not showing for several days now. Thanks for the help so far

We are asking for the customer inputs, to confirm whether there are Instacal processes running - previously he said it is not running. Could it be that the Instacal processes are starting automatically somehow? I dont think we start it from the code, unless there is something in Instacal dll that brings it up. The event in the event viewer that I posted in the first thread - does it mean that the Instacal application crashes (it is an Info message and not an error)? if it does crash, what makes it to start again as we saw these events several times and I assume it should gone if it is crashed already. Maybe the Instacal application recover automatically after crash ? Thanks

We decided to connect the two miniLab cards directly using two USB cables to the Win10 machine where the C# program is running. We dont use the USB hub anymore, where it used to connect the two miniLabs and the Win10 together. It is running for the last 24 hours without errors in the C# application, however we still experience the APPCRASH info event in the event viewer as I reported in my first post. The instacal executable is not running so it is strange that it reports it. We are assuming the event can be related to the "cbw32.dll" that is used by the C# application. I uploaded all the files that created as result of the APPCRASH event. Will appreciate if you can review the files and identify what can be wrong. Thank you. Report.wer memory.hdmp WER83A6.tmp.appcompat.txt WER8298.tmp.mdmp WER8326.tmp.WERInternalMetadata.xml WER8346.tmp.xml WER8354.tmp.csv WER8364.tmp.txt

Upgrading might be too challenging. We have same setup working on other deployments so I doubt about the upgrade to 6.74 Can you please explain how DAQami can be used for troubleshoot ? can it run in parallel to the C# program ?

Hello, In our Org. we are using Instacal version 6.7.2 on Win 10 to interoperate with several miniLabs that are connected with USB cables. The miniLabs are connected to USB hub and to the computer - we run C# program we developed to communicate with the miniLab cards. Very frequently we experience an Exception in the code with the following error: "MCC DAQ Error Digital device is not responding. DeadDigitalDev" We also noticed that at the same time in the Win event viewer there is an event from instacal for appcrash (see the attached file). We reimage the windows OS, replaced USB Hub, replaced miniLab cards but the error keep showing. I will appreciate your help with that issue Thanks