Assume that you have some tables that contain clustered columnstore indexes in a Microsoft SQL Server 2012 instance. When you run a workload that executes concurrent queries against the tables, the following error messages about the Resource Monitor task are logged in the SQL Server error log:

<Date><Time> Server      Using 'dbghelp.dll' version '4.0.5'
<Date><Time> Server      **Dump thread - spid = 0, EC = 0x0000000000000000
<Date><Time> Server      ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\LOG\SQLDump0860.txt
<Date><Time> Server      * *******************************************************************************
<Date><Time> Server      *
<Date><Time> Server      * BEGIN STACK DUMP:
<Date><Time> Server      *   <Date><Time> spid #
<Date><Time> Server      *
<Date><Time> Server      * Non-yielding Resource Monitor
<Date><Time> Server      *
<Date><Time> Server      * *******************************************************************************
<Date><Time> Server      * -------------------------------------------------------------------------------
<Date><Time> Server      * Short Stack Dump
<Date><Time> Server      Stack Signature for the dump is 0x00000000000002FF
<Date><Time> Server      External dump process return code 0x20000001.
External dump process returned no errors.

Additionally, you may encounter 100 percent CPU utilization, and the instance of SQL Server freezes. You have to restart SQL Server to resume operations. As a side effect, you may also notice a "Non-yielding Scheduler" message after the "Non-yielding Resource Monitor" message.

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:


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

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!