BugCheck Dump: Non-yielding Resource Monitor

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Data Corruption » BugCheck Dump: Non-yielding Resource Monitor

BugCheck Dump: Non-yielding Resource Monitor

Rate Topic

Display Mode

Topic Options

Author

Message

SQLdba-473999

Posted Wednesday, November 05, 2008 1:13 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, May 13, 2013 2:46 PM
Points: 149, Visits: 676

Has anyone ever experienced the following?

in sql server log:
2008-11-04 22:25:39.06 Server **Dump thread - spid = 0, PSS = 0x0000000000000000, EC = 0x0000000000000000
2008-11-04 22:25:39.15 Server ***Stack Dump being sent to X:\Microsoft SQL Server\MSSQL.2\MSSQL\LOG\SQLDump0002.txt
2008-11-04 22:25:39.15 Server * *******************************************************************************
2008-11-04 22:25:39.17 Server *
2008-11-04 22:25:39.17 Server * BEGIN STACK DUMP:
2008-11-04 22:25:39.17 Server * 11/04/08 22:25:39 spid 0
2008-11-04 22:25:39.17 Server *
2008-11-04 22:25:39.17 Server * Non-yielding Resource Monitor
2008-11-04 22:25:39.17 Server *
2008-11-04 22:25:39.17 Server * *******************************************************************************
2008-11-04 22:25:39.17 Server * -------------------------------------------------------------------------------
2008-11-04 22:25:39.17 Server * Short Stack Dump
2008-11-04 22:25:40.39 Server Stack Signature for the dump is 0x000000000000024E

The SQLDump0002.txt shows:
=====================================================================
BugCheck Dump
=====================================================================

This file is generated by Microsoft SQL Server
version 9.00.3159.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.

Computer type is AT/AT COMPATIBLE.
Current time is 22:25:39 11/04/08.
8 Unknown CPU 9., 3167 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 2.

Memory
MemoryLoad = 18%
Total Physical = 16381 MB
Available Physical = 13398 MB
Total Page File = 19036 MB
Available Page File = 14023 MB
Total Virtual = 8388607 MB
Available Virtual = 8371762 MB
**Dump thread - spid = 0, PSS = 0x0000000000000000, EC = 0x0000000000000000
***Stack Dump being sent to X:\Microsoft SQL Server\MSSQL.2\MSSQL\LOG\SQLDump0002.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 11/04/08 22:25:39 spid 0
*
* Non-yielding Resource Monitor
*
* *******************************************************************************
* -------------------------------------------------------------------------------
* Short Stack Dump

Please help!

Post #597653

Jonathan Kehayias

Posted Wednesday, November 12, 2008 11:48 AM

SSCommitted

Group: General Forum Members
Last Login: Sunday, May 12, 2013 4:26 PM
Points: 1,696, Visits: 1,742

Post #601604

SQLdba-473999

Posted Wednesday, November 12, 2008 12:36 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, May 13, 2013 2:46 PM
Points: 149, Visits: 676

No, CLR is not enabled.

Post #601631

Jonathan Kehayias

Posted Wednesday, November 12, 2008 1:01 PM

SSCommitted

Group: General Forum Members
Last Login: Sunday, May 12, 2013 4:26 PM
Points: 1,696, Visits: 1,742

What is running when the stack dump generates? Non-yielding resources usually mean that something pre-emptive was executing which could be CLR, an XP, a OLE Automation Call, or it could be a real bug in SQL Server, that you've happened upon in your configuration. It is not impossible. You might read the PSS teams blog post on the non-yielding resource monitor:

http://blogs.msdn.com/psssql/archive/2008/03/28/how-it-works-non-yielding-resource-monitor.aspx

There is a whitepaper linked at the top of the post that has information on how to actually read the dump file with the debugger to determine what actually caused it to dump out. It gets really cryptic though, and support is likely your best avenue to a fix for this problem.

Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs

Post #601656

SQLdba-473999

Posted Wednesday, November 12, 2008 1:51 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, May 13, 2013 2:46 PM
Points: 149, Visits: 676

Jonathan Kehayias (11/12/2008)

What is running when the stack dump generates?

I could not tell what was running from any of the logs and it only happened once.

I will review the link you sent. Thanks.

Post #601695

ThomasRushton

Posted Friday, May 07, 2010 2:55 AM

SSC Eights!

Group: General Forum Members
Last Login: 2 days ago @ 6:30 AM
Points: 966, Visits: 372

I've just had the same problem on a SQL2005 Standard Edition SP2 box that's not very active.

The only other thing that has logged an issue at a similar time on that box was McAfee, giving a McLogEvent EventID 257. (I've checked - McAfee On Access Scan is set to exclude SQL Server processes and mdf/ldf/ndf/bak/trn files.)

I've had a look into this machine's history, and I see that it suffered the same issue a year or so earlier. unfortunately, there's no DBA around here now who was here then that I can ask about it - and I've only been here 6 weeks!

The server itself seems perfectly happy, so I'm going to let it run.

Post #917722

kennethigiri

Posted Monday, May 17, 2010 3:50 AM

Valued Member

Group: General Forum Members
Last Login: 2 days ago @ 10:17 AM
Points: 52, Visits: 212

Hi All,

I also had this error in my environment. I would like to know how it is related to this one (assuming anyone has a quick answer):

A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 395696, committed (KB): 11644184, memory utilization: 3%.

Post #922777

krn045

Posted Thursday, June 14, 2012 12:42 AM

Grasshopper

Group: General Forum Members
Last Login: Monday, January 21, 2013 9:35 PM
Points: 15, Visits: 68

Check the below articles to resolve the below messages in sql error log.. Basically add -T845 flag in sql server startup parameter and sql service account should have lock pages in memory permission.
-------------------------
A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 395696, committed (KB): 11644184, memory utilization: 3%.
---------------------
http://support.microsoft.com/kb/970070
http://support.microsoft.com/kb/918483

Post #1315640

Clayton Hoyt

Posted Thursday, December 06, 2012 11:03 AM

Forum Newbie

Group: General Forum Members
Last Login: 2 days ago @ 9:34 AM
Points: 5, Visits: 152

Another KB to look into would be http://support.microsoft.com/kb/2216485

Post #1393655

« Prev Topic | Next Topic »

Permissions