FIX: SQL Server 2012, SQL Server 2008 R2 or SQL Server 2008 stops responding and a "Non-yielding Scheduler" error is logged

Article translations Article translations
Article ID: 2699013 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 (SP1), Microsoft SQL Server 2008 R2 and Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack (SP1), Microsoft SQL Server 2008 R2 and SQL Server 2008 fix release.
Expand all | Collapse all

On This Page

Symptoms

When you use Microsoft SQL Server 2012, Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2008, a "Non-yielding Scheduler" error might occur, and SQL Server might stop responding. When this issue occurs, one or both of the following error messages are logged in the Application log.

Error message 1

DateTime PM MSSQLSERVER Information Server 846 N/A ServerName A time-out occurred while waiting for buffer latch -- type 4, bp 0000000098FC1F00, page 1:7158252, stat 0xc00009, database id: 13, allocation unit Id: 72057594050969600, task 0x0000000005C31948 : 0, waittime 300, flags 0x1018, owning task 0x0000000000000000. Not continuing to wait.

Error message 2

DateTime AM MSSQLSERVER Information Server 17883 N/A ServerName Process 0:0:0 (0xb6c) Worker 0x0000000008F641A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12971505305687. Approx Thread CPU Used: kernel 31 ms, user 38240375 ms. Process Utilization 7%%. System Idle 92%%. Interval: 38243440 ms.


Additionally, one or both of the following error messages are logged in the SQL Server Error log.

Error message 3

DateTime Server Using 'dbghelp.dll' version '4.0.5'
DateTime Server ***Unable to get thread context for spid 0
DateTime Server * *******************************************************************************
DateTime Server *
DateTime Server * BEGIN STACK DUMP:
DateTime Server * DateTime spid ID
DateTime Server *
DateTime Server * Non-yielding Scheduler
DateTime Server *
DateTime Server * *******************************************************************************
DateTime Server Stack Signature for the dump is 0x0000000000000069
DateTime Server External dump process return code 0x20000001.
External dump process returned no errors.

Error message 4

DateTime Server Process 0:0:0 (0xb6c) Worker 0x0000000008F641A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12971505305687. Approx Thread CPU Used: kernel 0 ms, user 70062 ms. Process Utilization 30%. System Idle 69%. Interval: 70078 ms.

Additionally, a mini-dump file is generated in the Application log. To recover from this issue, you might have to restart the SQL services.

Cause

This issue occurs because the profiling session is not closed correctly. The profiling session is used to calculate the cost of an object to be cached, and is based on memory usage and CPU usage.

Resolution

Cumulative update information

Cumulative update package 1 for SQL Server 2012 Service Pack 1

The fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2012 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2765331 Cumulative update package 1 for SQL Server 2012 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

SQL Server 2012

The fix for this issue was first released in Cumulative Update 3 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2723749 Cumulative update package 3 for SQL Server 2012
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.

SQL Server 2008 R2 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 2. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2720425 Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2730301 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

SQL Server 2008 Service Pack 3

The fix for this issue was first released in Cumulative Update 6 for SQL Server 2008 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2715953 Cumulative update package 6 for SQL Server 2008 Service Pack 3
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2629969 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 3 hotfix to an installation of SQL Server 2008 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 R2 SP1

The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2703282 Cumulative update package 7 for SQL Server 2008 R2 SP1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack 1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 SP1 was released

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 14 for SQL Server 2008 R2. For more information about how to obtain this cumulative update package for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
2703280 Cumulative update package 14 for SQL Server 2008 R2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

Status

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

Properties

Article ID: 2699013 - Last Review: November 20, 2012 - Revision: 8.0
Applies to
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Web
  • Microsoft SQL Server 2008 Workgroup
  • Microsoft SQL Server 2012 Business Intelligence
  • Microsoft SQL Server 2012 Developer
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Standard
  • Microsoft SQL Server 2012 Web
  • SQL Server 2012 Enterprise Core
Keywords: 
kbtshoot kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2699013

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com