Description
This wait is used internally by SQL Server to stop multiple instances from deadlock monitors at the same time. Small values are expected. If values are excessive investigation is required
Resolved by
DBAs
Suggested solutions
- There is a known bug in versions of SQL Server 2005 – 2012 that cause this wait type to be high and lock up the instance. See link below
- Examine the SQL Server error log for more information
Additional research
KB972936 Excess DEADLOCK_ENUM_MUTEX waits with ACCESS_VIOLATION