LabVIEW
Could anyone give some suggestions about the Internal Warning?
Recently this error has been troubling me frequently.
I have no idea in which situation it happened and the error code seems not the same every time. The picture in the following shows one example of these errors.
So is there some tips for resolving this problem? thanks!!
Is this a crash or just a message?
You can turn off internal error notifications on exit in Options>Environment>NI Error Reporting.
If it is a crash, something might got permanently corrupted, or you're doing something that rubs LV the wrong way. Could be anything... Had to say without code and a way to reproduce.
Search LabVIEW like a graph! 
There are many things that could be the cause of this.
- Corrupted LabVIEW installation
- Corrupted Windows installation
- You are using VIs with Call Library Nodes that are not properly configured or implemented and every time that VI is executed it silently and secretly corrupts memory that will further down the path throw a wrench in LabVIEWs wheels as it tries to access that corrupted memory.
If it is always in the same module (window.cpp) then I would tend to guess that it is one of the two first. A complete forced LabVIEW reinstall might help then.
If the module name changes too, then I would more think of the two latter causes.
I recently was involved in a case where a system suddenly would crash randomly. This was a bit special as not only was LabVIEW involved which would crash consistently either in its lvrt.dll or ntdll.dll when trying to allocate memory, but also that one of the two GigE cameras would not be visible anymore at all both in LabVIEW and in the manufacturers own app. And this app (which was not LabVIEW based) tended to crash regularly too in ntdll.dll.
We did some analysis but couldn't really find the root cause of this. A complete HD wipe with new install from a system image backup seems to have solved that issue. RAM and other hardware stress test programs didn't indicate any problem, so our current guess is that the system got corrupted at some point when it was shutdown with the main power instead of properly shutting down Windows itself first.
