This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

LabVIEW Crash with Debug Output 'DAbort 0x89B93EF0: Bad Image in ValidateImage'

Updated Jan 11, 2019

Reported In


  • LabVIEW

Issue Details

When trying to run my VI in LabVIEW, the program crashes. The .dmp file generated from the crash cites the following line: DAbort 0x89B93EF0: bad image in ValidateImage.


The most common cause of this crash is due to attached comments (Figure 1) not being implemented correctly, with the arrows not pointing to objects they are intended to point to and/or are missing (Figure 2).

Figure 1 - Correct implementation of Attached Comments

Figure 2 - Incorrect Implementation of Attached Comments

In order to avoid this type of issue, it is important to ensure any floating arrows of the comments of the object it is intended to point to are reconnected (Figure 3). This will remove the open reference and prevent the crash from occurring. Note that this issue is a known bug that was discovered in LabVIEW 2013 and 2014, and has been fixed from LabVIEW 2015 onwards. Later versions should not crash due to this issue.

Figure 3 - Ensure Attached Comments Point to Intended Object

Another possible cause of the crash is linked to LabVIEW's internal image table. LabVIEW uses this to store images it uses, one example of this being VI icons. When this table becomes full, it can cause LabVIEW to crash. To avoid this issue, ensure that you are using LabVIEW 2011 f2 Patch onwards, as a fix was added to only load VI icons when they are needed. Additionally, the image table capacity was increased for LabVIEW 2015 SP1 f5 to reduce Image Table errors.