Please help! SQL Server crash dump

Help,
A server became unresponsive yesterday, starting with disk write errors that
we've seen before,
but then around 9am this morning a crash dump was written.
Can anybody help me to chase this down. I think the best resolution is PSS,
but I'd like to get
as much info as I can before making a call.
2003-07-30 16:40:40.90 server Error: 17883, Severity: 1, State:
2003-07-30 16:42:19.68 spid54 Time out occurred while waiting for buffer
latch type 2,bp 0x278e640, page 1:4425087), stat 0x40d, object ID
46:517576882:0, EC 0x5973F580 : 0, waittime 300. Not continuing to wait.
2003-07-30 16:40:40.90 server Process 0:0 (b18) UMS Context 0x12863740
appears to be non-yielding on Scheduler
2003-07-31 09:00:35.96 spid54 Waiting for type 0x2, current count
0x100022, current owning EC 0x5973F580.
2003-07-31 09:00:37.64 server Sleeping until external dump process
completes.
2003-07-31 09:00:46.53 server Resuming after waiting on external debug
process for 2 seconds.
2003-07-31 09:00:46.53 server Stack Signature for the dump is 0x00000000
TIA.Have a look at
PRB: Common Causes of Error Message 844 or Error Message 845 (Buffer Latch
Time Out Errors)
http://support.microsoft.com/default.aspx?scid=kb;en-us;310834
and also
INF: New Concurrency and Scheduling Diagnostics Added to SQL Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;319892
which contains this note about 17883 errors
"Microsoft tries to keep all content up-to-date with the latest 17883
conditions. However, the 17883 error message is a health detection message
that can be triggered for many reasons. Microsoft has not only corrected
known issues with the SQL Server software product but has also encountered
the 17883 error in a variety of situations that are unrelated to the SQL
Server software. For example, the error has occurred with external
application CPU consumption and hardware failures. You must determine the
root cause of the 17883 error message if you want to avoid an unwanted
reoccurrence of the error. "
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Stressed" <k@.c.co.uk> wrote in message
news:uQ4C7a0VDHA.2156@.TK2MSFTNGP11.phx.gbl...
Help,
A server became unresponsive yesterday, starting with disk write errors that
we've seen before,
but then around 9am this morning a crash dump was written.
Can anybody help me to chase this down. I think the best resolution is PSS,
but I'd like to get
as much info as I can before making a call.
2003-07-30 16:40:40.90 server Error: 17883, Severity: 1, State:
2003-07-30 16:42:19.68 spid54 Time out occurred while waiting for buffer
latch type 2,bp 0x278e640, page 1:4425087), stat 0x40d, object ID
46:517576882:0, EC 0x5973F580 : 0, waittime 300. Not continuing to wait.
2003-07-30 16:40:40.90 server Process 0:0 (b18) UMS Context 0x12863740
appears to be non-yielding on Scheduler
2003-07-31 09:00:35.96 spid54 Waiting for type 0x2, current count
0x100022, current owning EC 0x5973F580.
2003-07-31 09:00:37.64 server Sleeping until external dump process
completes.
2003-07-31 09:00:46.53 server Resuming after waiting on external debug
process for 2 seconds.
2003-07-31 09:00:46.53 server Stack Signature for the dump is 0x00000000
TIA.