FIX: "Non-yielding Scheduler" condition occurs on spinlock contention in Microsoft SQL Server 2014 or 2016

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core

Symptoms


A "Non-yielding Scheduler" condition may occur on spinlock contention in Microsoft SQL Server 2014 or 2016. Additionally, the SQL Server may crash. 

Resolution


This issue is fixed in the following cumulative update for SQL Server:

       Cumulative Update 8 for SQL Server 2016 RTM

       Cumulative Update 5 for SQL Servre 2016 SP1

       Cumulative Update 6 for SQL Server 2014 SP2

Status


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

References


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