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

Applies To

SQL Server 2016 Developer - duplicate (do not use) SQL Server 2016 Enterprise - duplicate (do not use) SQL Server 2016 Enterprise Core - duplicate (do not use) SQL Server 2016 Standard - duplicate (do not use) SQL Server 2016 Service Pack 1 SQL Server 2014 Developer - duplicate (do not use) SQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Enterprise Core - duplicate (do not use) SQL Server 2014 Standard - duplicate (do not use) SQL Server 2014 Service Pack 2 - duplicate (do not use)

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

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2016

Latest cumulative update for SQL Server 2014

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 terminologythat Microsoft uses to describe software updates.