Sign in with Microsoft
Sign in or create an account.


You may experience non-yielding scheduler in Microsoft SQL Server that's the primary replica of the Always On availability group (AG) when the SQL Server instance is under low memory. Additionally, the following entry is logged in the SQL Server error log:

DateTime Server      Process 0:0:0 (0x1fa4) Worker 0x000001024B232160 appears to be non-yielding on Scheduler 3. Thread creation time: 13215777539641. Approx Thread CPU Used: kernel 4932703 ms, user 5961140 ms. Process Utilization 15%. System Idle 81%. Interval: 10902277 ms.


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


This problem is fixed in the following cumulative updates for SQL Server:

About cumulative updates for SQL Server:

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:

Service pack information for SQL Server 2016

This problem is fixed in the following service pack for SQL Server:

Service packs are cumulative. Each new service pack contains all the fixes that are in previous service packs, together with any new fixes. We recommend that you apply the latest service pack and the latest cumulative update for that service pack. You do not have to install a previous service pack before you install the latest service pack. Use Table 1 in the following article to find more information about the latest service pack and latest cumulative update.

Determine the version, edition, and update level of SQL Server and its components


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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!