LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Unrecoverable Internal Error at 001B:105E7624.

Hello friends,

I get error in LabWindows 9.0 as :

 

Unrecoverable Internal Error at 001B:105E7624.

LabWindows/CVI will be aborted.

 

And when when I cancel that pop up,

next pop up comes which says :

 

Panel,pop-up or menubar handle is invalid.

 

 

It comes for all files which are open and when I cancel  one pop up,application closes one file.

It happens for all open files then finally closes Labwindows.

 

 

It mostly happens when I am dealing with ".uir" file or tracing callbacks from ."uir" file.

 

It had happened lots of time.

 

What could be the problem???

 

 

0 Kudos
Message 1 of 8
(4,098 Views)

@MAPJ wrote:

 

Panel,pop-up or menubar handle is invalid.

 

What could be the problem???



You gave the answer yourself... Smiley Wink

 

Have a look at the line generating the error using CVI's debugging tools and use a correct panel / menu bar handle...

0 Kudos
Message 2 of 8
(4,097 Views)

No that I understood but what is 001B:105E7824 error.

because that error comes most of the time.

Handles error come today.

I corrected that.

 

main problem is 001B:105E7824 error.

and it closes complete application.

 

 

 

0 Kudos
Message 3 of 8
(4,093 Views)

Hi MAPJ,

 

having one but well defined question is preferred over general statements that the program is crashing... Smiley Wink I admit that this is easier said than done but program crashes can have quite a few reasons and it will be difficult for everyone trying to assist you without more detailed information...

 

So as suggested first steps it might be helpful if you could

  • try to localize the problem, e.g. using breakpoints
  • try to provide a minimum example allowing reproducing the issue
  • search the forum for related issues: searching 'Unrecoverable Internal Error' gave more than 30 posts on this subject, may be one of them could be of use for you?
0 Kudos
Message 4 of 8
(4,089 Views)

Yes sorry,actually I could not explain question.

That was not problem in our project .

That problem was in LabWin,it crashes even for small program sometime.

Now I am reading all posts.

 

Smiley Very Happy

 

0 Kudos
Message 5 of 8
(4,070 Views)

Hi MAPJ,

 

Error at 001B:105E7624 indicates the memory location in the program where the crash occurred. Sometimes this is useful for debugging, but most of the time it is not. Unfortunately, this is a bit of a difficult thing to debug. Likely something on your system is corrupt, have you tried reinstalling or repairing the CVI installation? Another thing we can try is a CVI debug log: Generating Debug Logs for LabWindows/CVI 9.0 and Later. The log may give us a clue as to when the error is occurring.

National Instruments
0 Kudos
Message 6 of 8
(4,049 Views)

I've had this problem regularly in all versions of CVI since at least v7. I don't remember if I've had it with v12. I remember writing an error report a LONG time ago about this. The CVI IDE crashes, but is nice enough to let you save the files you were working on so it's not TOO annoying. I suspect it has to do with some corruption in the prj files, but it's hard to pinpoint and triggers randomly.

0 Kudos
Message 7 of 8
(4,040 Views)

I agree with gdargaud - I have seen similar crashes off and on with at least the last two versions of CVI I've used.  I commented on it several times years ago, no real resolution to it.  I think I recreated projects / workspace to avoid it, never could correlate the crashes with anything specific.  I seem to associate it loosely with adding or deleting files in a project - it's as if there's some latent state that doesn't get reconciled in the project or workspace metadata that gets into trouble.  I remember discussing here on the forum whether or not it had anything to do with the autosave facility that NI added to CVI - in fact, someone from NI asked me if I was using autosave (autobackup?) at the time.

 

 

0 Kudos
Message 8 of 8
(4,021 Views)