Freeing heap block containing an active critical section. Memory location at <lock address> of size <size> contains an active lock.

This break is generated if a heap allocation contains a critical section, the allocation is freed and the critical section has not been deleted.

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

Parameter2 - Critical section initialization stack trace. Run dps address to dump the stack trace.

Parameter3 - Heap block address

Parameter4 - Heap block size

Description - Freeing heap block containing an active critical section

Verifier stop code 0202.

Check the contents of the current call stack. The culprit is usually the caller of HeapFree or HeapDestroy on the current stack trace.

Frequency of this error is high.

To debug this stop use the following debugger commands:

!cs �s parameter1 - dump information about this critical section.

ln parameter1 � to show symbols near the address of the critical section. This should help identify the leaked critical section.

dds parameter2 � to dump the stack trace for this critical section initialization.

parameter3 and parameter4 might help understand where was this heap block allocated (the size of the allocation is probably significant).