The Owner of the Lock is Invalid, Owner Was Expected
Application Verifier stop message
Locks violation detected. The owner of the lock is invalid, owner <thread id> was expected.
Probable cause
This stop is generated if the owner thread ID is invalid in the current context.
Information displayed by Application Verifier in Tool Window
Lock – Critical section address
Owner – Owning thread – current owning thread (invalid owner)
DebugInfo – Critical section debug info address
Description – The owner of the lock is invalid, owner <thread id> was expected
Trace Description - Blank
Additional information
Check the contents of the current call stack where the thread calls EnterCriticalSection or LeaveCriticalSection. Examine the call stacks of the current owning thread and the expected owner thread.
Frequency of this stop is low.