Invalid TLS Index In The Current Operation

Application Verifier stop message

Handle violation detected. Invalid TLS index in the current operation.

Probable cause

This stop is generated if the function on the top of the stack passed an invalid TLS index to TLS system routines. The typical issue here is to assume a certain value for a TLS index instead of calling TlsAlloc. This can happen by assuming you always get TLS index value N, therefore there is no need to call TlsAlloc, or it may be due to an un-initialized variable.

Information displayed by Application Verifier in Tool Window

Handle - N/A

Description - Invalid TLS index in the current operation

Additional info - Index used <index> : expected lower part of the index <lower_part_of_the_index>

Additional information

Examine the current call stack to see where the invalid TLS index is being used.

See Also

Concepts

Handle Verifier