Fatal Stack Dump - Desperate For Help Please

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

New to SQL Server Administration

Fatal Stack Dump - Desperate For Help Please

Author

Topic

bobbles22
Starting Member

18 Posts

Posted - 2010-08-26 : 05:03:51

Dear all,

Yesterday, my SQL 2005 server (on Windows 2003 R2) twice restarted the SQL services of its own accord after a crash.

The following was written to the log at about 16:10 yesterday afternoon with everyone in the system (although I had the same thing at 18:08 the previous day with only a couple of the managers left in the building):

08/25/2010 16:11:52,Server,Unknown,Resource Monitor (0xe5c) Worker 0x0412C0E8 appears to be non-yielding on Node 0. Memory freed: 6192 KB. Approx CPU Used: kernel 0 ms<c/> user 0 ms<c/> Interval: 64172.

08/25/2010 16:11:52,Server,Unknown,Timeout waiting for external dump process 9324.

08/25/2010 16:10:16,Server,Unknown,Stack Signature for the dump is 0x00000030

08/25/2010 16:10:16,Server,Unknown,* Short Stack Dump

08/25/2010 16:10:16,Server,Unknown,* -------------------------------------------------------------------------------

08/25/2010 16:10:16,Server,Unknown,* *******************************************************************************

08/25/2010 16:10:16,Server,Unknown,*

08/25/2010 16:10:16,Server,Unknown,* Non-yielding Resource Monitor

08/25/2010 16:10:16,Server,Unknown,*

08/25/2010 16:10:16,Server,Unknown,* 08/25/10 16:10:16 spid 0

08/25/2010 16:10:16,Server,Unknown,* BEGIN STACK DUMP:

08/25/2010 16:10:16,Server,Unknown,*

08/25/2010 16:10:16,Server,Unknown,* *******************************************************************************

08/25/2010 16:10:16,Server,Unknown,***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0002.txt

08/25/2010 16:10:16,Server,Unknown,**Dump thread - spid = 0<c/> PSS = 0x00000000<c/> EC = 0x00000000

08/25/2010 16:10:15,Server,Unknown,Using 'dbghelp.dll' version '4.0.5'

Also, in the event log, I get Event ID 5000, source SQLDUMPER, with description:

EventType sql90exception, P1 sqlservr.exe, P2 2005.90.3073.0, P3 4898d0c7, P4 sqlservr.exe, P5 2005.90.3073.0, P6 4898d0c7, P7 0, P8 011a76bc, P9 00000030, P10 NIL.

Does anyone know what causes this? I'm very concerned that my SQL server is randomly restarting the SQL services whilst people are using the system. Does anyone know how to take the worker hex code and figure out who caused this (I'm guessing the worker hex code references a SQL/windows users who was performing a function that caused it to crash).

Can anyone help me on this?

Many thanks

Bob

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-08-26 : 05:47:14

Contact Microsoft Customer Support and log a call with them. They're about the only people who can diagnose and assist with stack dumps. Make sure you're on the latest patch level for SQL 2005 (SP3) first.

--
Gail Shaw
SQL Server MVP

Lumbago
Norsk Yak Master

3271 Posts

Posted - 2010-08-26 : 09:38:29

...and do make sure you have your backups in order! My default first place to look if something like this was ever to happen to me would be the hardware. I have the impression that all errors where sql server does weird stuff that causes uncontrolled behavior is caused by physical problems.

- Lumbago

My blog (yes, I have a blog now! just not that much content yet)
-> www.thefirstsql.com

Kristen
Test

22859 Posts

Posted - 2010-08-27 : 01:52:56

We have had poor quality code cause stack dumps - stuff that calls COM objects that were unstable - but in all instances the culprit was clear from the "readable" data in the Stack Dump.

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources