Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


BugCheck Dump: Non-yielding Resource Monitor


BugCheck Dump: Non-yielding Resource Monitor

Author
Message
SQLdba-473999
SQLdba-473999
SSC-Enthusiastic
SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)

Group: General Forum Members
Points: 177 Visits: 767
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!
Jonathan Kehayias
Jonathan Kehayias
SSCommitted
SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)

Group: General Forum Members
Points: 1822 Visits: 1807
Do you have CLR integration enabled and CLR objects being used in the database engine?

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
SQLdba-473999
SQLdba-473999
SSC-Enthusiastic
SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)

Group: General Forum Members
Points: 177 Visits: 767
No, CLR is not enabled.
Jonathan Kehayias
Jonathan Kehayias
SSCommitted
SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)

Group: General Forum Members
Points: 1822 Visits: 1807
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
SQLdba-473999
SQLdba-473999
SSC-Enthusiastic
SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)SSC-Enthusiastic (177 reputation)

Group: General Forum Members
Points: 177 Visits: 767
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.
ThomasRushton
ThomasRushton
SSCommitted
SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)

Group: Moderators
Points: 1820 Visits: 2160
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.
Br. Kenneth Igiri
Br. Kenneth Igiri
SSC-Enthusiastic
SSC-Enthusiastic (160 reputation)SSC-Enthusiastic (160 reputation)SSC-Enthusiastic (160 reputation)SSC-Enthusiastic (160 reputation)SSC-Enthusiastic (160 reputation)SSC-Enthusiastic (160 reputation)SSC-Enthusiastic (160 reputation)SSC-Enthusiastic (160 reputation)

Group: General Forum Members
Points: 160 Visits: 444
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%.

Br. Kenneth Igiri
www.scribblingsage.com
www.igiribooks.com
"All nations come to my light, all kings to the brightness of my rising"Smooooth
krn045
krn045
Grasshopper
Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)

Group: General Forum Members
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
Clayton Hoyt
Clayton Hoyt
Forum Newbie
Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)

Group: General Forum Members
Points: 6 Visits: 407
Another KB to look into would be http://support.microsoft.com/kb/2216485



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search