The Lock Verifier checks for errors in the file critical section usage.
Following is a list of verifier stops that may occur when running the Lock verifier against a project on different platforms:
Error Message
Critical Section Over-Released or Corrupted
Memory Location Contains an Active Lock
Module Contains an Active Lock
Released Virtual Memory Containing An Active Lock
The Lock Count is Invalid
The Lock has Already been Initialized
The Lock Is Being Used Without Having Been Initialized
The Lock is Corrupted
The Owner of the Lock is Invalid, Owner Was Expected
The Recursion Count is Invalid
The Region of Memory about to be Freed Contains an Active Lock
The Region of Unmapped Memory Contains An Active Lock
The Thread Cannot Own a Lock in this Context
Thread Not Supposed To Own a Lock