最近数据库老是自动断开，重启下又好了

[飞啊飞的菜菜鸟]

最近数据库老是莫名其妙就断了，在服务器本地和网络上其他客户端都无法访问，但网络又是通的，外网和网上邻居也都正常，重启之后又变正常。我把出问题的地方的日志贴出来，求大牛帮忙分析分析吧——（注意从下往上看。每次都是在那个named pipe之后就出现异常了）

03/25/2017 10:19:12,服务器,未知,New queries assigned to process on Node 0 have not been picked up by a worker thread in the last 180 seconds. Blocking or long-running queries can contribute to this condition<c/> and may degrade client response time. Use the "max worker threads" configuration option to increase number of allowable threads<c/> or optimize current running queries. SQL Process Utilization: 0%. System Idle: 99%.
03/25/2017 10:18:12,服务器,未知,New queries assigned to process on Node 0 have not been picked up by a worker thread in the last 120 seconds. Blocking or long-running queries can contribute to this condition<c/> and may degrade client response time. Use the "max worker threads" configuration option to increase number of allowable threads<c/> or optimize current running queries. SQL Process Utilization: 0%. System Idle: 99%.
03/25/2017 10:17:12,服务器,未知,New queries assigned to process on Node 0 have not been picked up by a worker thread in the last 60 seconds. Blocking or long-running queries can contribute to this condition<c/> and may degrade client response time. Use the "max worker threads" configuration option to increase number of allowable threads<c/> or optimize current running queries. SQL Process Utilization: 0%. System Idle: 99%.
03/25/2017 10:17:12,Server,未知,External dump process return code 0x20000001.<nl/>External dump process returned no errors.
03/25/2017 10:17:03,Server,未知,Stack Signature for the dump is 0x0000000000000140
03/25/2017 10:17:03,Server,未知,* Short Stack Dump
03/25/2017 10:17:03,Server,未知,* -------------------------------------------------------------------------------
03/25/2017 10:17:03,Server,未知,* *******************************************************************************
03/25/2017 10:17:03,Server,未知,*
03/25/2017 10:17:03,Server,未知,* Deadlocked Schedulers
03/25/2017 10:17:03,Server,未知,*
03/25/2017 10:17:03,Server,未知,*   03/25/17 10:17:03 spid 2296
03/25/2017 10:17:03,Server,未知,* BEGIN STACK DUMP:
03/25/2017 10:17:03,Server,未知,*
03/25/2017 10:17:03,Server,未知,* *******************************************************************************
03/25/2017 10:17:03,Server,未知,***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0009.txt
03/25/2017 10:17:03,Server,未知,**Dump thread - spid = 0<c/> EC = 0x0000000000000000
03/25/2017 10:17:03,Server,未知,Using 'dbghelp.dll' version '4.0.5'
03/25/2017 10:16:30,登录,未知,Login succeeded for user 'NT AUTHORITY\SYSTEM'. Connection made using Windows authentication. [客户端: <local machine>]
03/25/2017 10:15:24,登录,未知,Login succeeded for user 'sa'. Connection made using SQL Server authentication. [客户端: <local machine>]
03/25/2017 10:15:18,登录,未知,Login succeeded for user 'sa'. Connection made using SQL Server authentication. [客户端: <local machine>]
03/25/2017 10:14:43,登录,未知,Login succeeded for user 'sa'. Connection made using SQL Server authentication. [客户端: <named pipe>]
03/25/2017 10:14:10,登录,未知,Login succeeded for user 'sa'. Connection made using SQL Server authentication. [客户端: 192.168.0.51]
03/25/2017 10:14:07,登录,未知,Login succeeded for user 'sa'. Connection made using SQL Server authentication. [客户端: 192.168.0.51]
03/25/2017 10:13:58,登录,未知,Login succeeded for user 'sa'. Connection made using SQL Server authentication. [客户端: 192.168.0.217]

日志中提到的SQLDump0009.txt我也贴出来——Current time is 10:17:03 03/25/17.
=====================================================================
BugCheck Dump
=====================================================================

This file is generated by Microsoft SQL Server
version 10.50.4000.0
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 Intel(R) Xeon(R) CPU E7- 4807 @ 1.87GHz.
Bios Version is IBM - 0
24 X64 level 8664, 1 Mhz processor (s).
Windows NT 6.1 Build 7601 CSD Service Pack 1.

Memory
MemoryLoad = 57%
Total Physical = 65513 MB
Available Physical = 28136 MB
Total Page File = 75511 MB
Available Page File = 35603 MB
Total Virtual = 8388607 MB
Available Virtual = 8320129 MB
**Dump thread - spid = 0, EC = 0x0000000000000000
***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0009.tx
t
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 03/25/17 10:17:03 spid 2296
*
* Deadlocked Schedulers
*
* *******************************************************************************
* -------------------------------------------------------------------------------
* Short Stack Dump

[Tiger_Zhao]

发生了死锁，所有的工作线程都用完了/等待中，所以不能再开新的访问了。
检查下前台，哪个调用时产生了长时等待/超时。

[飞啊飞的菜菜鸟]

引用 2 楼 Tiger_Zhao 的回复:

发生了死锁，所有的工作线程都用完了/等待中，所以不能再开新的访问了。 检查下前台，哪个调用时产生了长时等待/超时。

请问下前台怎么检查啊，我太想知道到底是哪个调用引发的问题

[Tiger_Zhao]

前台（程序）捕获的超时错误，或者（人工）一个操作长时没有响应。

[0与1之间]

数据库跟踪下吧，好像是超时了

[飞啊飞的菜菜鸟]

引用 4 楼 Tiger_Zhao 的回复:

前台（程序）捕获的超时错误，或者（人工）一个操作长时没有响应。

主要是我们前台程序比较多，用户也比较分散，也搞不清是从哪里先出现提示了，一发作的时候都在反映说慢、连不上。 能有更有效的方法揪出源头吗？

[Tiger_Zhao]

开活动监视器啊。
又：调优解死锁是个大工程，没有药到病除的灵丹。

[xiaoxiangqing]

可能是服务器不稳定