LabVIEW Support

Commonly Occurring Internal Errors and Resolutions

Back to Main LabVIEW Internal Error Page

Errors occurring while printing or editing in LabVIEW

National Instruments has found that internal errors reported in the following files may be related to problems with video and/or printer drivers:

drawmgr.c image.c textmgr.c

color.c image.cpp fontmgr.c

panel.c panelsup.c

These errors commonly occur when editing, but may also occur when printing. If you receive an error in one of these files, we recommend contacting the manufacturer of your video hardware or printer and requesting the latest driver. Most hardware manufacturers post such drivers on their web sites. These drivers are updated frequently; even a new video card or printer may have a more recent driver than the one with which it shipped.

If using the latest driver does not resolve the problem, try one of the following:

Certain video drivers also support "acceleration" modes. We have found that using a non-accelerated mode often eliminates the error.
In Windows, the standard VGA driver provided by the operating system is very stable. Try using this driver in place of the specific one written for your video hardware. If the error is eliminated, there is likely a problem with your vendor-provided video driver.
Try adjusting the color palette your driver uses (i.e. 256 color, high color, true color). The error may occur only in one of these modes.
If the error occurs while printing, try adjusting the printing options in LabVIEW's Edit >> Preferences >> Printing menu.

Other common causes for internal errors

National Instruments has also found that other hardware drivers, such as mouse drivers, may cause internal errors in LabVIEW. If you begin to notice these errors after installing such hardware, be sure you have installed the latest driver available for the hardware. As with video hardware, there may be advanced features of the driver that can be disabled that will eliminate the error.

LabVIEW creates temporary files during execution. In the event of a system crash, these temporary files may become corrupted, and you may receive an internal error as a result. One common solution is to delete all files in your temporary directory. For example, in Windows 95, the temporary directory is commonly Windows\Temp. It is also a good idea to use whatever disk diagnostic tools you have available to verify that there are no problems with the hard drive. Windows 95, for example, provides the Scandisk utility that can repair many common disk errors.

Conflicts may also arise between LabVIEW and other software. In trying to determine the cause of internal errors, you should minimize the software that is running concurrent with LabVIEW. If the errors cease under these conditions, there is evidence that a conflict occurs with such software. National Instruments has found this to be the case most often with TSR (terminate and stay-resident) software that runs in the background, especially TSRs that constantly monitor or manipulate the file system. File system acceleration utilities and virus scanners are examples of such software. Note that utilities provided by the operating system itself may cause these problems as well as those provided by third-party vendors.

Resources