Deleting critical section with invalid lock count

This break is generated if a critical section is owned by another thread and the critical section is being deleted by the current thread. If the owning thread is 0, the critical section has not been initialized.

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

Parameter2 - Lock count

Parameter3 - Expected lock count

Parameter4 - Owning thread

Description - Deleting critical section with invalid lock count

Verifier stop code 0208.

Call Stack � current call stack when thread exited.

Frequency of this stop is high

To debug this stop:

!cs �s parameter1 - dump information about this critical section. If the owning thread is 0 the critical section has not been initialized.

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