This documentation is archived and is not being maintained.

Module Contains an Active Lock

Application Verifier stop message

Locks violation detected. Module <module name> loaded at <address> contains an active lock.

Probable cause

This stop is generated if a DLL has a global variable containing a lock and the DLL is unloaded but the critical section has not been deleted.

Information displayed by Application Verifier in Tool Window

Lock – Critical section address

Owner - N/A

DebugInfo – N/A

Description – Module <module name> loaded at <address> contains an active lock

Trace Description – Critical Section Initialization

Additional information

The name of the module that has an active lock is shown in the error message. The Tool Window displays the stack trace for the critical section initialization. Also, check the contents of the current call stack when the DLL with the active lock was unloaded.

Frequency of this error is high.

See Also