April 17, 2012 at 9:59 pm
Hi. Our production server which has been up since Sept 8 2011 suddenly just keeled over with the following dump. I was wondering if people do a regular reboot of SQL as a general maintenace task.
Anyway her is the dump. If anyone has some ideas of the cause I would be grateful. thanks.
Current time is 09:59:36 04/18/12.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 10.50.2500.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 Six-Core AMD Opteron(tm) Processor 8431.
Bios Version is INTEL - 6040000
PhoenixBIOS 4.0 Release 6.0
2 X64 level 8664, 3 Mhz processor (s).
Windows NT 6.1 Build 7600 CSD .
Memory
MemoryLoad = 94%
Total Physical = 8191 MB
Available Physical = 448 MB
Total Page File = 20475 MB
Available Page File = 10854 MB
Total Virtual = 8388607 MB
Available Virtual = 8376171 MB
***Stack Dump being sent to E:\MSSQL\LOG\SQLDump0001.txt
SqlDumpExceptionHandler: Process 162 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 04/18/12 09:59:36 spid 162
*
*
* Exception Address = 0000000077161C30 Module(ntdll+0000000000051C30)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 00000994DB95BF58
* Input Buffer 178 bytes -
* EXEC [dbo].[spDesktopLabels] @Mode = 'Patient', @URN = '85904
* 6', @VisitNo = ''
*
*
* MODULE BASE END SIZE
* sqlservr 0000000000570000 000000000414CFFF 03bdd000
* ntdll 0000000077110000 00000000772BAFFF 001ab000
* kernel32 0000000076EF0000 000000007700EFFF 0011f000
* KERNELBASE 000007FEFD3D0000 000007FEFD43AFFF 0006b000
* ADVAPI32 000007FEFD440000 000007FEFD51AFFF 000db000
* msvcrt 000007FEFE9A0000 000007FEFEA3EFFF 0009f000
* sechost 000007FEFEEE0000 000007FEFEEFEFFF 0001f000
* RPCRT4 000007FEFF2C0000 000007FEFF3EDFFF 0012e000
*
* P1Home: 00000000374ACD10: 00000000C0000005 0000000000000000 0000000077161C30 FFFFF6FB00000002 00000000
00000000 00000994DB95BF58
* P2Home: 00000000374AC820: 00000000374ACD10 00000000374AC820 0000000000000000 0000000000000000 00000000
00000079 0000000000000000
* P3Home: 0000000000000000:
* P4Home: 0000000000000000:
* P5Home: 0000000000000079:
* P6Home: 0000000000000000:
* ContextFlags: 000000000010001F:
* MxCsr: 0000000000001F80:
* SegCs: 0000000000000033:
* SegDs: 000000000000002B:
* SegEs: 000000000000002B:
* SegFs: 0000000000000053:
* SegGs: 000000000000002B:
* SegSs: 000000000000002B:
* EFlags: 0000000000010216: 0000000000000000 0000000000000000 000000000FA00000 0000000000000000 00010000
00800000 0001000000010000
* Rax: 0000002E00220031:
* Rcx: 000000FFFFFFFFFF:
* Rdx: 000000001D0C22A0: 003000300031006C 9022002E00220031 0000000000000000 0000000300010000 00000001
00000000 0000000000000000
* Rbx: 00000994DB95BF50:
* Rsp: 00000000374ACDE0: 000000000036C718 0000000000000000 0000000000000000 0000000000000000 00000000
00000001 0000000000000000
* Rbp: 0000000000000000:
* Rsi: 0000000000440000: 0000000000000000 01002349D1106F65 00000000FFEEFFEE 000000000C680018 00000000
00440128 0000000000440000
* Rdi: 000000001D0C22B0: 0000000000000000 0000000300010000 0000000100000000 0000000000000000 00000000
00000000 0000000000000000
* R8: 000000001D0C22B0: 0000000000000000 0000000300010000 0000000100000000 0000000000000000 00000000
00000000 0000000000000000
* R9: 010485B801F60011:
* R10: 000000001D218D10: 00220055004D0078 0000000000000000 0000000000000000 900000B74CC9762E 0031006C
006F0043 0000003400340030
* R11: 000000001D218910: 0054004100500022 00450044004F0043 0000000000220053 960000B74CC9766E 00220055
004D0022 0046004400550000
* R12: 0000000000000000:
* R13: 0000000000000000:
* R14: 0000000000000000:
* R15: 000000000036C718: 000000000DA24CA8 000000000DA24C78 0000000010ECFFE8 000000001D148E00 00000001
FFFFFFFE 00000000000005EC
* Rip: 0000000077161C30: 0001BD4908638B4C BE49000000010000 FFFFFFFF00007FFF 000E42C6800F42C6 8B4CFFFF
0000BF41 234D280C8D4F1043
* *******************************************************************************
* -------------------------------------------------------------------------------
* Short Stack Dump
0000000077161C30 Module(ntdll+0000000000051C30)
000007FEFEB59F76 Module(ole32+0000000000039F76)
0000000044701A5F Module(OraOLEDButl11+0000000000001A5F)
0000000044423371 Module(OraOLEDBrst11+0000000000023371)
000000004442446D Module(OraOLEDBrst11+000000000002446D)
000000000D9C1DB1 Module(OraOLEDB11+0000000000001DB1)
00000000010B1AB7 Module(sqlservr+0000000000B41AB7)
00000000010590B7 Module(sqlservr+0000000000AE90B7)
0000000001048752 Module(sqlservr+0000000000AD8752)
0000000000FC2D8F Module(sqlservr+0000000000A52D8F)
0000000001E5F000 Module(sqlservr+00000000018EF000)
0000000001E5F6F6 Module(sqlservr+00000000018EF6F6)
000000000062FBF2 Module(sqlservr+00000000000BFBF2)
00000000005C5435 Module(sqlservr+0000000000055435)
00000000005C500B Module(sqlservr+000000000005500B)
00000000005C5FAC Module(sqlservr+0000000000055FAC)
00000000005D9A86 Module(sqlservr+0000000000069A86)
00000000005DB4AF Module(sqlservr+000000000006B4AF)
00000000005DAD6C Module(sqlservr+000000000006AD6C)
0000000001A6DA1C Module(sqlservr+00000000014FDA1C)
0000000001A6D37A Module(sqlservr+00000000014FD37A)
0000000001A6B36D Module(sqlservr+00000000014FB36D)
00000000005D9A86 Module(sqlservr+0000000000069A86)
00000000005DB4AF Module(sqlservr+000000000006B4AF)
00000000005DAD6C Module(sqlservr+000000000006AD6C)
00000000005FCFA6 Module(sqlservr+000000000008CFA6)
00000000006265E2 Module(sqlservr+00000000000B65E2)
000000000057B450 Module(sqlservr+000000000000B450)
000000000057B116 Module(sqlservr+000000000000B116)
000000000057AF5B Module(sqlservr+000000000000AF5B)
00000000006B44FA Module(sqlservr+00000000001444FA)
00000000006B47DD Module(sqlservr+00000000001447DD)
0000000000AFC0CD Module(sqlservr+000000000058C0CD)
00000000006B53D2 Module(sqlservr+00000000001453D2)
0000000074D337D7 Module(MSVCR80+00000000000037D7)
0000000074D33894 Module(MSVCR80+0000000000003894)
0000000076F0F56D Module(kernel32+000000000001F56D)
0000000077143021 Module(ntdll+0000000000033021)
CSession @0x00000001EB5383B0
----------------------------
m_spid = 162 m_cRef = 12 m_rgcRefType[0] = 1
m_rgcRefType[1] = 1 m_rgcRefType[2] = 9 m_rgcRefType[3] = 1
m_rgcRefType[4] = 0 m_rgcRefType[5] = 0 m_pmo = 0x00000001EB538080
m_pstackBhfPool = 0x0000000154ABCF50 m_dwLoginFlags = 0x03e0 m_fBackground = 0
m_eConnResetOption = 0 m_fUserProc = -1 m_fConnReset = 0
m_fIsConnReset = 0 m_fInLogin = 0 m_fAuditLoginSent = 1
m_fAuditLoginFailedSent = 0 m_fReplRelease = 0 m_fKill = 0
m_ulLoginStamp = 90063206 m_eclClient = 6 m_protType = 5
m_hHttpToken = FFFFFFFFFFFFFFFF
m_pV7LoginRec
---------------------
0000000000000000: 1a010000 03000a73 401f0000 00000006 38260000 †.......s@.......8&..
0000000000000014: 00000000 e0030000 00000000 00000000 5e000700 †....à...........^...
0000000000000028: 6c000600 78000000 88001c00 c0000700 ce000000 †l...x.......À...Î...
000000000000003C: ce001c00 06010000 06010a00 0dbf1745 58e71a01 †Î............¿.EXç..
0000000000000050: 00001a01 00001a01 00000000 0000†††††††††††††††..............
CPhysicalConnection @0x00000001EB538270
---------------------------------------
m_pPhyConn->m_pmo = 0x00000001EB538080
m_pPhyConn->m_pNetConn = 0x00000001EB538AD0
m_pPhyConn->m_pConnList = 0x00000001EB538380
m_pPhyConn->m_pSess = 0x00000001EB5383B0 m_pPhyConn->m_fTracked = -1
m_pPhyConn->m_cbPacketsize = 8000 m_pPhyConn->m_fMars = 0 m_pPhyConn->m_fKill = 0
CBatch @0x00000001EB538FA0
--------------------------
m_pSess = 0x00000001EB5383B0 m_pConn = 0x00000001EB538EA0 m_cRef = 3
m_rgcRefType[0] = 1 m_rgcRefType[1] = 1 m_rgcRefType[2] = 1
m_rgcRefType[3] = 0 m_rgcRefType[4] = 0 m_pTask = 0x00000001386834C8
EXCEPT (null) @0x00000000374AA308
---------------------------------
exc_number = 0 exc_severity = 0 exc_func = 0x0000000002A7F2A4
Task @0x00000001386834C8
------------------------
CPU Ticks used (ms) = 1383 Task State = 2
WAITINFO_INTERNAL: WaitResource = 0x0000000000000000 WAITINFO_INTERNAL: WaitType = 0x0
WAITINFO_INTERNAL: WaitSpinlock = 0x0000000000000000
WAITINFO_EXTERNAL: WaitResource = 0x0000000000000000 WAITINFO_EXTERNAL: WaitType = 0x40006D
WAITINFO_EXTERNAL: WaitSpinlock = 0x0000000000000000
WAITINFO_EXTERNAL: WaitResource = 0x0000000000000000
WAITINFO_EXTERNAL: WaitType = 0x20000193
WAITINFO_EXTERNAL: WaitSpinlock = 0x0000000000000000 SchedulerId = 0x0
ThreadId = 0x5ec m_state = 0 m_eAbortSev = 0
EC @0x0000000154ABC450
----------------------
spid = 0 ecid = 0 ec_stat = 0x0
ec_stat2 = 0x0 ec_atomic = 0x0 __fSubProc = 1
__pSETLS = 0x00000001EB538F10 __pSEParams = 0x00000001EB539350
SEInternalTLS @0x00000001EB538F10
---------------------------------
m_flags = 0 m_TLSstatus = 3 m_owningTask = 0x00000001386834C8
m_activeHeapDatasetList = 0x00000001EB538F10
m_activeIndexDatasetList = 0x00000001EB538F20 m_pDbccContext = 0x0000000000000000
SEParams @0x00000001EB539350
----------------------------
m_lockTimeout = -1 m_isoLevel = 4096 m_logDontReplicate = 0
m_neverReplicate = 0 m_XactWorkspace = 0x0000000190E12080
m_pSessionLocks = 0x0000000154ABCD90 m_pDbLocks = 0x00000001EB539870
m_execStats = 0x000000008C986F60 m_pAllocFileLimit = 0x0000000000000000
April 18, 2012 at 1:35 am
Hard to tell without the tools that CSS has. If it's important, open a case with them. They have tools to read these and access to the private symbols.
It looks like some non-SQL code was running at the time, specifically something in the OS kernel.
0000000077161C30 Module(ntdll+0000000000051C30)
000007FEFEB59F76 Module(ole32+0000000000039F76)
0000000044701A5F Module(OraOLEDButl11+0000000000001A5F)
0000000044423371 Module(OraOLEDBrst11+0000000000023371)
000000004442446D Module(OraOLEDBrst11+000000000002446D)
000000000D9C1DB1 Module(OraOLEDB11+0000000000001DB1)
It also looks like the dump just terminated a process, not the entire SQL Server.
SqlDumpExceptionHandler: Process 162 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
If the dump directly caused SQL to terminate completely, that would read SQL Server is terminating. I've seen that before.
Nothing else in the error logs to suggest why SQL terminated?
Access violations are memory errors and unfortunately often the process that trips over the access violation is not the one that caused the problem in the first place. It can be a faulty memory chip or a memory scribbler somewhere else on the server.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 18, 2012 at 3:13 am
C3PO's twin (4/17/2012)
... I was wondering if people do a regular reboot of SQL as a general maintenace task.
No. It is concerned a bad practice because after startup of the SQLInstance, it needs ( a relative amount of ) time to load data into ram, generate sqlplans, claim more ram until regular operational size, ...
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
April 18, 2012 at 5:56 am
have you checked the Windows application and system logs?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 18, 2012 at 7:05 pm
April 18, 2012 at 7:57 pm
C3PO's twin (4/18/2012)
Yeah I know that. But has SQL Server matured enough to be an Enterprise DBMS that can up for more than 6 months?
I am going to say yes, that SQL Server is mature enough to be an Enterprise DBMS>
As for rebooting SQL Server, I usually did when we applied OS or SQL patches or service packs or when we needed to do hardware maintenance that required a server shutdown.
April 18, 2012 at 8:24 pm
Lynn Pettis (4/18/2012)
C3PO's twin (4/18/2012)
Yeah I know that. But has SQL Server matured enough to be an Enterprise DBMS that can up for more than 6 months?I am going to say yes, that SQL Server is mature enough to be an Enterprise DBMS>
As for rebooting SQL Server, I usually did when we applied OS or SQL patches or service packs or when we needed to do hardware maintenance that required a server shutdown.
we only reboot our production server when applying software updates which we only do when there is a critical hole that got patched by MS or when we install CM's. 6 months is nothing for our production servers to go with out a reboot.
For performance Issues see how we like them posted here: How to Post Performance Problems - Gail Shaw[/url]
Need to Split some strings? Jeff Moden's DelimitedSplit8K[/url]
Jeff Moden's Cross tab and Pivots Part 1[/url]
Jeff Moden's Cross tab and Pivots Part 2[/url]
April 18, 2012 at 9:59 pm
C3PO's twin (4/18/2012)
Yeah I know that. But has SQL Server matured enough to be an Enterprise DBMS that can up for more than 6 months?
I would have to qualify the answer into two categories, 64-bit and 32-bit:
For 64-bit instances, no problem.
For 32-bit instances it is usually no problem, but will largely depend on what you're doing on the instance as to whether you need to reboot periodically. With VAS being such a limiting factor on 32-bit instances large contiguous blocks can become hard to come by after being up for a while and the only way to defragment the VAS is to reboot.
Caveat to both: no faulty third-party code exists in the environment. By third-party code I am thinking about Linked Servers with bad drivers or Extended Stored Procs that reference misbehaving code...which is by no means the fault of SQL Server.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
April 18, 2012 at 11:56 pm
opc.three (4/18/2012)
With VAS being such a limiting factor on 32-bit instances large contiguous blocks can become hard to come by after being up for a while and the only way to defragment the VAS is to reboot.
Set the -g startup parameter to 384 or higher providing you have enough physical RAM 😉
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 19, 2012 at 3:14 am
C3PO's twin (4/18/2012)
Yeah I know that. But has SQL Server matured enough to be an Enterprise DBMS that can up for more than 6 months?
Absolutely. I know of many companies that only reboot servers when absolutely necessary (windows patches).
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 19, 2012 at 9:18 am
Perry Whittle (4/18/2012)
opc.three (4/18/2012)
With VAS being such a limiting factor on 32-bit instances large contiguous blocks can become hard to come by after being up for a while and the only way to defragment the VAS is to reboot.Set the -g startup parameter to 384 or higher providing you have enough physical RAM 😉
Increasing MemToLeave using the -g startup parameter can help, but in some cases it only defers the inevitable, a reboot. It depends on the usage pattern.
For me, this is the go-to article for VAS info in case anyone's interested: Understanding the VAS Reservation (aka MemToLeave) in SQL Server by Jonathan Kehayias
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
January 2, 2015 at 9:51 am
Current time is 03:29:37 04/16/14.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 11.0.3000.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 X5650 @ 2.67GHz.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply