Assume that you have multiple client applications that connect to an instance of Microsoft SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014. Additionally, the Multiple Active Result Sets (MARS) feature is enabled in the connection strings or the applications are configured to use Distributed Transaction Coordinator (DTC). When multiple requests are being sent from these applications at the same time, deadlocks may occur when data is manipulated. In this situation, an access violation may occur in the SQL Server internal deadlock monitor.
This issue occurs because the transaction mutex is not updated with the new workspace. The deadlock monitor thread accesses this old workspace during lock enumeration, and the access violation occurs if the old workspace has been released or if it was not cleaned up properly.
Cumulative update informationThe issue was first fixed in the following cumulative update of SQL Server.
Hotfix informationThe hotfix updates the transaction mutex to use the new workspaces when workspaces are changed.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.