Unrecoverable Internal Error @ 001B:109A4917

[ASIC_LabRat]

I keep getting this CVI aborted message when working with instrument driver development, no project loaded, just working with the interactive execution, function panels, function tree in edit mode re-compiling the instrument driver and checking the operation of the new callback. What is going on?

[ebalci]

Thanks ASIC, that's also problem for me nowadays.

In my case, a project is loaded and the error pops up during interactive execution, either when the project is code is resting at a breakpoint for debug or just the function panels are run one after the other for development trials.

I searched the forum once or twice to find if someone was having the similar problem but I could not find an exact match and I could live with the burden of restarting the project since it is not occuring too often. So I did not want to bother the NI people for this (really considerate, huh? 😉 ).

But I'll be more than happy to see this issue resolved.

[StevieZ]

Do you have an exact wording for the error message? A screenshot of the message would be helpful if you could post that. In addition, if you can reproduce the issue using specific steps, that process will help me discover the cause.

Regards,

Steven Zittrower

Applications Engineer

National Instruments

http://www.ni.com/support

[LuisG]

Also, the fault address that you reported might be helpful, but only if we know exactly which version of CVI each of you are using (and if it's 9.0 we need the full version number, visible in the Help>>About window).

Thanks,

Luis

[ASIC_LabRat]

Steve, Luis,

    I had to move off this system to move forward. so this seems to be related to the system I was on. The version I am using is 9.0 FDS. the screen shot is attached, cvi_crashing. So if this is a "machine hardware" related problem or a missing code because of an install issue, let me know how to proceed/ de-bug because I am leary of releasing my code and see machine dependant issues keep causing problems.

[StevieZ]

The version information that we are looking for is the full version and build number. I've attached a screenshot for where this information is contained in the Help»About dialog.

Just to clarify, when you are working on a different system you do not see this same error? If that is the case, could you provide the same version information for the system that it works fine on.

 

Regards,

Steven Zittrower

Applications Engineer

National Instruments

http://www.ni.com/support

Message Edited by StevieZ on 04-06-2009 01:28 PM

[ASIC_LabRat]

Yes, crystal clear... build 348... on both systems...

ChipB

[ebalci]

In my case, I have 8.5.1 (356).

I'm not sure I get the same address values on the popup each time.

I'll post the screenshot when it occurs next time.

But it happens %99.9 during interactive execution.

[ASIC_LabRat]

All,

  It seems the more I develope using interactive execution, the more frequent the error begins to occure... so to preceed I must mover to another machine or reinstall LabWindowsCVI... any clue why interactive execution erodes the more I use it?

ChipB....

[nickb]

Hey Chip - 

Without being able to consistently reproduce the issue here, it will be difficult for us to find a solution to the issue.  If you would be willing, I have placed a debug version of the CVI 9.0.0.348 environment on our ftp site at ftp://ftp.ni.com/outgoing/CVIDebug/cvi.zip.  This dll will *only* work with the CVI 9.0 environment.  Using this dll will cause the CVI environment to crash instead of showing you the unrecoverable internal error dialog.  This will allow you to create a crash dump that we can analyze, and hopefully then track down the issue you are seeing.

To use this debug version of the environment, there are a couple things you will need to do: 

1. Replace the existing cvi.dll in the <National Instruments>/CVI90 with the one in the zip file from the ftp site.  When I do this, I usually just rename the existing one to something like cviRELEASE.dll.
2. Enable crash dumping. 
   On an XP machine:
   - Run C:\Windows\System32\drwtsn32.exe -i (this will register Dr. Watson as your "just in time" debugger)
   - Whenever you get a crash and you see the "Please tell Microsoft about this problem..." dialog, click "Don't Send"
   - Browse to the C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson folder.  The dump and log files are there.  Keep in mind that if you have a second crash, it will overwrite the previous dump.
   On a Vista machine:
   - Install the Windows Debugging Tools. (note, if using 64 bit Vista, be sure to install the 64 bit version)
   - Run C:\Program Files\Debugging Tools for Windows\windbg.exe -i (this will register windbg as your "just in time" debugger)
   - When you get a crash, windbg should start up automatically.  At that point, type .dump /ma C:\temp\mydump.dmp into the command window to generate the dump file.
3. Once you get the crash, get the .dmp file from the location listed above an post it to ftp://ftp.ni.com/incoming.  This is a public write only ftp site.  Only NI employees can retrieve files from this site.
4. Post back to this forum with the name of the file you have uploaded to the ftp site.

Thanks!

NickB

National Instruments  

Message Edited by nickb on 04-07-2009 12:14 PM