Locks violation detected. The region of unmapped memory at <location> of size <size> contains an active lock.
This stop is generated if the current thread is calling UnmapViewOfFile on a memory block that contains an active critical section. The application should call DeleteCriticalSection on this critical section before it releases this memory.
Lock - Critical section address.
Owner - N/A
DebugInfo - N/A
Description - The region of unmapped memory at <location> of size <size> contains an active lock.
Trace Description – Critical Section Initialization
The call stack in the tool window shows where the critical section was initialized.
Check the current call stack where the virtual memory is released using UnmapViewOfFile.
Frequency of this error is low.