InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 18 May 2013 10:58:09 GMT20http://www.sqlservercentral.com/Forums/Topic597653-266-1.aspxAnother KB to look into would be http://support.microsoft.com/kb/2216485 Thu, 06 Dec 2012 11:03:54 GMTClayton Hoythttp://www.sqlservercentral.com/Forums/Topic597653-266-1.aspxCheck 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/970070http://support.microsoft.com/kb/918483Thu, 14 Jun 2012 00:42:41 GMTkrn045http://www.sqlservercentral.com/Forums/Topic597653-266-1.aspxHi 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%.Mon, 17 May 2010 03:50:38 GMTkennethigirihttp://www.sqlservercentral.com/Forums/Topic597653-266-1.aspxI'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.Fri, 07 May 2010 02:55:48 GMTThomasRushtonhttp://www.sqlservercentral.com/Forums/Topic597653-266-1.aspx[quote][b]Jonathan Kehayias (11/12/2008)[/b][hr]What is running when the stack dump generates?[/quote]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.Wed, 12 Nov 2008 13:51:31 GMTSQLdba-473999http://www.sqlservercentral.com/Forums/Topic597653-266-1.aspxWhat 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:[url]http://blogs.msdn.com/psssql/archive/2008/03/28/how-it-works-non-yielding-resource-monitor.aspx[/url]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.Wed, 12 Nov 2008 13:01:10 GMTJonathan Kehayiashttp://www.sqlservercentral.com/Forums/Topic597653-266-1.aspxNo, CLR is not enabled.Wed, 12 Nov 2008 12:36:48 GMTSQLdba-473999http://www.sqlservercentral.com/Forums/Topic597653-266-1.aspxDo you have CLR integration enabled and CLR objects being used in the database engine?Wed, 12 Nov 2008 11:48:17 GMTJonathan Kehayiashttp://www.sqlservercentral.com/Forums/Topic597653-266-1.aspxHas anyone ever experienced the following?in sql server log:2008-11-04 22:25:39.06 Server **Dump thread - spid = 0, PSS = 0x0000000000000000, EC = 0x00000000000000002008-11-04 22:25:39.15 Server ***Stack Dump being sent to X:\Microsoft SQL Server\MSSQL.2\MSSQL\LOG\SQLDump0002.txt2008-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 02008-11-04 22:25:39.17 Server *2008-11-04 22:25:39.17 Server * Non-yielding Resource Monitor2008-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 Dump2008-11-04 22:25:40.39 Server Stack Signature for the dump is 0x000000000000024EThe 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!Wed, 05 Nov 2008 13:13:33 GMTSQLdba-473999