Dump files in SQL 7.0 Enterprise

Hello,
I have been experiencing crash dump files on our SQL 7 Enterprise box several times per day for the last few months. I can't seem to match them up to a particular task or job.
Any ideas appreciated. Thank you.
Here is the head of one of the .dmp files:
================================================== ===================
BugCheck Dump
================================================== ===================
This file is generated by Microsoft SQL Server 1792.842
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 local time is Wed Jul 21 12:13:00 2004
2 Intel x86 level 6, 797 Mhz processor(s).
Windows NT 5.0 Build 2195 CSD Service Pack 4.
Memory
MemoryLoad = 97% TotalPhys = 2047 MB AvailPhys = 47 MB
TotalPageFile = 3941 MB
Dump thread - spid = 29, PSS = 0x35799138, EC = 0x357992e8
Symbol load failed - Proceed to dump without any symbols
Stack Dump being sent to C:\MSSQL7\log\SQL08175.dmp
************************************************** *****************************
*
* BEGIN STACK DUMP:
* 07/21/04 12:13:00 spid 29
*
* Input Buffer 42 bytes -
* s p _ r e s e t _ c o n n e c t i o n
*
************************************************** *****************************
Parsing dump files is not something everybody can do and you only provided a
fraction of it. If your crashing that often you should contact MS PSS and
let them work directly with you to fix the issue. They can certainly access
the dump files properly.
http://support.microsoft.com/default...d=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"ddrewrey" <ddrewrey@.discussions.microsoft.com> wrote in message
news:A939C3EC-D341-4835-B4EC-E9FB7AF26638@.microsoft.com...
> Hello,
> I have been experiencing crash dump files on our SQL 7 Enterprise box
several times per day for the last few months. I can't seem to match them up
to a particular task or job.
> Any ideas appreciated. Thank you.
> Here is the head of one of the .dmp files:
> ================================================== ===================
> BugCheck Dump
> ================================================== ===================
> This file is generated by Microsoft SQL Server 1792.842
> 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 local time is Wed Jul 21 12:13:00 2004
> 2 Intel x86 level 6, 797 Mhz processor(s).
> Windows NT 5.0 Build 2195 CSD Service Pack 4.
>
> Memory
> --
> MemoryLoad = 97% TotalPhys = 2047 MB AvailPhys = 47 MB
> TotalPageFile = 3941 MB
> Dump thread - spid = 29, PSS = 0x35799138, EC = 0x357992e8
> Symbol load failed - Proceed to dump without any symbols
> Stack Dump being sent to C:\MSSQL7\log\SQL08175.dmp
>
************************************************** **************************
***
> *
> * BEGIN STACK DUMP:
> * 07/21/04 12:13:00 spid 29
> *
> * Input Buffer 42 bytes -
> * s p _ r e s e t _ c o n n e c t i o n
> *
>
************************************************** **************************
***

Dump files in SQL 7.0 Enterprise

Hello,
I have been experiencing crash dump files on our SQL 7 Enterprise box several times per day for the last few months. I can't seem to match them up to a particular task or job.
Any ideas appreciated. Thank you.
Here is the head of one of the .dmp files:
===================================================================== BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server 1792.842
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 local time is Wed Jul 21 12:13:00 2004
2 Intel x86 level 6, 797 Mhz processor(s).
Windows NT 5.0 Build 2195 CSD Service Pack 4.
Memory
--
MemoryLoad = 97% TotalPhys = 2047 MB AvailPhys = 47 MB
TotalPageFile = 3941 MB
Dump thread - spid = 29, PSS = 0x35799138, EC = 0x357992e8
Symbol load failed - Proceed to dump without any symbols
Stack Dump being sent to C:\MSSQL7\log\SQL08175.dmp
*******************************************************************************
*
* BEGIN STACK DUMP:
* 07/21/04 12:13:00 spid 29
*
* Input Buffer 42 bytes -
* s p _ r e s e t _ c o n n e c t i o n
*
*******************************************************************************Parsing dump files is not something everybody can do and you only provided a
fraction of it. If your crashing that often you should contact MS PSS and
let them work directly with you to fix the issue. They can certainly access
the dump files properly.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
--
Andrew J. Kelly SQL MVP
"ddrewrey" <ddrewrey@.discussions.microsoft.com> wrote in message
news:A939C3EC-D341-4835-B4EC-E9FB7AF26638@.microsoft.com...
> Hello,
> I have been experiencing crash dump files on our SQL 7 Enterprise box
several times per day for the last few months. I can't seem to match them up
to a particular task or job.
> Any ideas appreciated. Thank you.
> Here is the head of one of the .dmp files:
> =====================================================================> BugCheck Dump
> =====================================================================> This file is generated by Microsoft SQL Server 1792.842
> 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 local time is Wed Jul 21 12:13:00 2004
> 2 Intel x86 level 6, 797 Mhz processor(s).
> Windows NT 5.0 Build 2195 CSD Service Pack 4.
>
> Memory
> --
> MemoryLoad = 97% TotalPhys = 2047 MB AvailPhys = 47 MB
> TotalPageFile = 3941 MB
> Dump thread - spid = 29, PSS = 0x35799138, EC = 0x357992e8
> Symbol load failed - Proceed to dump without any symbols
> Stack Dump being sent to C:\MSSQL7\log\SQL08175.dmp
>
****************************************************************************
***
> *
> * BEGIN STACK DUMP:
> * 07/21/04 12:13:00 spid 29
> *
> * Input Buffer 42 bytes -
> * s p _ r e s e t _ c o n n e c t i o n
> *
>
****************************************************************************
***

Dump files in SQL 7.0 Enterprise

Hello,
I have been experiencing crash dump files on our SQL 7 Enterprise box severa
l times per day for the last few months. I can't seem to match them up to a
particular task or job.
Any ideas appreciated. Thank you.
Here is the head of one of the .dmp files:
========================================
=============================
BugCheck Dump
========================================
=============================
This file is generated by Microsoft SQL Server 1792.842
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 local time is Wed Jul 21 12:13:00 2004
2 Intel x86 level 6, 797 Mhz processor(s).
Windows NT 5.0 Build 2195 CSD Service Pack 4.
Memory
--
MemoryLoad = 97% TotalPhys = 2047 MB AvailPhys = 47 MB
TotalPageFile = 3941 MB
Dump thread - spid = 29, PSS = 0x35799138, EC = 0x357992e8
Symbol load failed - Proceed to dump without any symbols
Stack Dump being sent to C:\MSSQL7\log\SQL08175.dmp
****************************************
************************************
***
*
* BEGIN STACK DUMP:
* 07/21/04 12:13:00 spid 29
*
* Input Buffer 42 bytes -
* s p _ r e s e t _ c o n n e c t i o n
*
****************************************
************************************
***Parsing dump files is not something everybody can do and you only provided a
fraction of it. If your crashing that often you should contact MS PSS and
let them work directly with you to fix the issue. They can certainly access
the dump files properly.
http://support.microsoft.com/defaul...id=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"ddrewrey" <ddrewrey@.discussions.microsoft.com> wrote in message
news:A939C3EC-D341-4835-B4EC-E9FB7AF26638@.microsoft.com...
> Hello,
> I have been experiencing crash dump files on our SQL 7 Enterprise box
several times per day for the last few months. I can't seem to match them up
to a particular task or job.
> Any ideas appreciated. Thank you.
> Here is the head of one of the .dmp files:
> ========================================
=============================
> BugCheck Dump
> ========================================
=============================
> This file is generated by Microsoft SQL Server 1792.842
> 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 local time is Wed Jul 21 12:13:00 2004
> 2 Intel x86 level 6, 797 Mhz processor(s).
> Windows NT 5.0 Build 2195 CSD Service Pack 4.
>
> Memory
> --
> MemoryLoad = 97% TotalPhys = 2047 MB AvailPhys = 47 MB
> TotalPageFile = 3941 MB
> Dump thread - spid = 29, PSS = 0x35799138, EC = 0x357992e8
> Symbol load failed - Proceed to dump without any symbols
> Stack Dump being sent to C:\MSSQL7\log\SQL08175.dmp
>
****************************************
************************************
***
> *
> * BEGIN STACK DUMP:
> * 07/21/04 12:13:00 spid 29
> *
> * Input Buffer 42 bytes -
> * s p _ r e s e t _ c o n n e c t i o n
> *
>
****************************************
************************************
***