It's part way there, filling in some blanks.
Internal inconsistency, type A, detected.
This error is signalled when QlikView gets a general exception when it tries to allocate memory.
This error will not be detected in QV.exe.
Internal inconsistency, type B, detected.
(type F errors were reported as type B in versions before QlikView 9)
This error is signalled when QlikView tries to release memory that it has not allocated.
Typically it is a side-effect of a failure (access violation) and the subsequent clean-up.
This error is detected in QV.exe
Internal inconsistency, type C, detected.
This error is signalled when the run-time terminates QlikView in an unexpected way.
This error is detected in QV.exe
Internal inconsistency, type D, detected.
This error is signalled when QlikView gets a general exception on deletion of a dynamic array
(TDynArray or TObjArray)
Typically it is a side-effect of a failure (access violation) and the subsequent clean-up.
This error is detected in QV.exe
Internal inconsistency, type E, detected.
This error is signalled when QlikView tries to flush memory and it has looped more than
100 000 times on one memory block size. The blocks are tied together in liked lists, so
more than 100 000 elements in one list is and indication of a circular reference in the list of allocated blocks
This error is detected in QV.exe
Internal inconsistency, type F, detected.
(type F errors were reported as type B in versions before QlikView 9)
This error is signalled when QlikView gets a general exception when it tries to allocate memory.
(Same type of incosistency as type A, but detected on another level)
This error will not be detected in QV.exe.
Internal inconsistency, type L, detected.
This error is signalled when QlikView has detected a circular reference in the global memory pool.
This error is detected in QV.exe
