FIX: SQL Server 2016 crashes when a Tuple Mover task is ended unexpectedly

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Express


A long-running Data Definition Language (DDL) statement may block the background Tuple Mover task and cause a deadlock. Most likely, the Tuple Mover task will be chosen as the deadlock victim. If this occurs, Microsoft SQL Server may crash. Additionally, you receive error messages that resemble the following in the SQL Server error log:
Error: 1205, Severity: 13, State: 18.
Transaction (Process ID <process id>) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
ex_terminator: Possible termination due to exception during stack unwinding.
Similarly, when the Tuple Mover task is run under severe memory pressure (for example, the memory utilization becomes 100 percent), the Tuple Mover task ends unexpectedly, and this causes SQL Server to crash.


Cumulative update information

The fix for this issue is included in the following cumulative update for SQL Server:


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminology that Microsoft uses to describe software updates.