Current thread does not own any critical sections.

This break is generated if the current thread calls LeaveCriticalSection but, according to the internal application verifier bookkeeping, it does not own any critical section.

If the number of locks owned is 0, the current thread is attempting to release a critical section it did not acquire or it is calling LeaveCriticalSection more often than it called EnterCriticalSection for a given critical section.

Parameter1 - Critical section address. Run !cs �s address to get more information.

Parameter2 - Number of critical sections owned by current thread

Parameter3 - Not used

Parameter4 - Not used

Description - Current thread does not own any critical sections

Verifier stop code 0214.

Call Stack � Current call stack when the thread attempts to release a lock it does not own.

Frequency of this error is low.

If parameter2 is zero, probably this is a bug in the current thread. It either tries to leave a critical section that it didn�t enter, or maybe it is calling LeaveCriticalSection more times than it called EnterCriticalSection for the same critical section.

If parameter2 is not zero (it is a negative integer number) the internal verifier data structures are probably corrupted.