Check this KB article. This may be what is effecting your DB.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q810195

Dave

-----Original Message-----
From: Chip Smith [mailto:[Email Address Removed] Wednesday, June 18, 2003 10:51 AM
To: LazyDBA.com Discussion
Subject: SQL SERVER 2K ERROR LOG


EC 59c5f568?
This message is my err log.
2003-06-17 21:22:36.44 spid66 WARNING: EC 59c5f568, 0 waited 300 sec. on
latch 42ca5a30. Not a BUF la
2003-06-17 21:22:36.44 spid66 Waiting for type 0x4, current count 0xa,
current owning EC 0x468F5520.
2003-06-17 21:27:36.45 spid66 WARNING: EC 59c5f568, 0 waited 600 sec. on
latch 42ca5a30. Not a BUF la
2003-06-17 21:27:36.45 spid66 Waiting for type 0x4, current count 0xa,
current owning EC 0x468F5520.

SQLSERVER Service went to 100% CPU and locked up the box.
Any gurus see this before?

-- "Chip"
<<...OLE_Obj...>>
"It never Rains Under My Umbrella!"

MS Sql Server LazyDBA home page