January 9, 2014 at 9:43 am
I have a 508MB exception.log. Too big to load into notepad. recently updated. Running SQL Server 2012. Been getting scads of dumps in my error log (brought it to 80GIG!) I had to remove it and start over -- too big to handle. I have scores of crash dumps as well... 10,000 of 'em. They seem to have stopped on 12/11/2013. Here's an example of SQLDump9999.txt:
Current time is 10:00:53 12/11/13.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 11.0.3128.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) Core(TM) i3 CPU 530 @ 2.93GHz.
Bios Version is HP - 6040000
Ver 1.00PARTTBL
4 Intel x86 level 6, 14 Mhz processor (s).
Windows NT 6.0 Build 6002 CSD Service Pack 2.
Memory
MemoryLoad = 97%
Total Physical = 4022 MB
Available Physical = 90 MB
Total Page File = 8295 MB
Available Page File = 4168 MB
Total Virtual = 4095 MB
Available Virtual = 1447 MB
***Stack Dump being sent to D:\Data\MSSQL.1\MSSQL\LOG\SQLDump9999.txt
SqlDumpExceptionHandler: Process 12 generated fatal exception c000000d EXCEPTION_INVALID_CRT_PARAMETER. SQL Serve
r is terminating this process.
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 12/11/13 10:00:53 spid 12
*
*
* Exception Address = 7598D8CB Module(kernel32+0001D8CB)
* Exception Code = c000000d EXCEPTION_INVALID_CRT_PARAMETER
*
*
* MODULE BASE END SIZE
* sqlservr 00F30000 00F64FFF 00035000
* ntdll 77150000 772AFFFF 00160000
* kernel32 75970000 75A7FFFF 00110000
* ADVAPI32 76800000 768C5FFF 000c6000
* RPCRT4 76390000 7647FFFF 000f0000
* Secur32 74C70000 74CCFFFF 00060000
* MSVCR100 73380000 7343EFFF 000bf000
* MSVCP100 73310000 73378FFF 00069000
* sqlos 73270000 73275FFF 00006000
* NETAPI32 74270000 742E5FFF 00076000
* msvcrt 74CD0000 74D79FFF 000aa000
* PSAPI 77120000 77126FFF 00007000
* pdh 731E0000 7321DFFF 0003e000
* opends60 73250000 73256FFF 00007000
* sqlmin 6B9D0000 6D398FFF 019c9000
* USER32 75D30000 75DFFFFF 000d0000
* GDI32 75FA0000 7602FFFF 00090000
* ole32 76490000 765D4FFF 00145000
* OLEAUT32 765E0000 7666CFFF 0008d000
* WS2_32 76040000 7606CFFF 0002d000
* NSI 76030000 76035FFF 00006000
* sqlTsEs 6E5A0000 6ED6AFFF 007cb000
* sqldk 6E1C0000 6E597FFF 003d8000
* WINMM 73060000 73091FFF 00032000
* OLEACC 73020000 7305DFFF 0003e000
* sqllang 58D70000 5A6B7FFF 01948000
* USERENV 74970000 7498DFFF 0001e000
* AUTHZ 730C0000 730D5FFF 00016000
* WINTRUST 749E0000 74A0CFFF 0002d000
* CRYPT32 74470000 74564FFF 000f5000
* MSASN1 74990000 749A1FFF 00012000
* imagehlp 76140000 76169FFF 0002a000
* IMM32 75CD0000 75D2FFFF 00060000
* MSCTF 758A0000 75967FFF 000c8000
* LPK 76480000 76488FFF 00009000
* USP10 760C0000 7613CFFF 0007d000
* instapi110 74690000 7469AFFF 0000b000
* cscapi 731D0000 731DAFFF 0000b000
* sqlevn70 6DF40000 6E1B9FFF 0027a000
* rsaenh 74A10000 74A4AFFF 0003b000
* ncrypt 746D0000 74704FFF 00035000
* BCRYPT 74390000 743D5FFF 00046000
* NTMARTA 746A0000 746C0FFF 00021000
* WLDAP32 76070000 760B8FFF 00049000
* SAMLIB 74370000 74380FFF 00011000
* GPAPI 74350000 74364FFF 00015000
* slc 74310000 74349FFF 0003a000
* cryptnet 742F0000 7430AFFF 0001b000
* SensApi 74BE0000 74BE5FFF 00006000
* SHLWAPI 76170000 761C8FFF 00059000
* comctl32 74710000 748ADFFF 0019e000
* SHELL32 74D80000 75890FFF 00b11000
* VERSION 74C40000 74C47FFF 00008000
* credssp 72400000 72406FFF 00007000
* schannel 71E80000 71EC6FFF 00047000
* msv1_0 72430000 72467FFF 00038000
* cryptdll 72280000 72290FFF 00011000
* Kerberos 71670000 716EDFFF 0007e000
* MSCOREE 748C0000 74909FFF 0004a000
* mscoreei 74610000 7468AFFF 0007b000
* CLUSAPI 71E20000 71E4DFFF 0002e000
* NTDSAPI 71E60000 71E77FFF 00018000
* DNSAPI 71320000 7134BFFF 0002c000
* ACTIVEDS 712E0000 71314FFF 00035000
* adsldpc 71210000 71242FFF 00033000
* credui 71060000 7108DFFF 0002e000
* ATL 711F0000 71203FFF 00014000
* RESUTILS 73000000 73012FFF 00013000
* security 730A0000 730A2FFF 00003000
* CLBCatQ 75C40000 75CC3FFF 00084000
* sqlncli11 6DC60000 6DF3DFFF 002de000
* COMCTL32 743E0000 74464FFF 00085000
* COMDLG32 75E00000 75E72FFF 00073000
* SQLNCLIR11 71730000 71767FFF 00038000
* clr 71770000 71E0AFFF 0069b000
* MSVCR110_CLR0400 734C0000 73592FFF 000d3000
* mscorlib.ni 6F710000 7073DFFF 0102e000
* culture 741F0000 741FCFFF 0000d000
* nlssorting 74060000 74071FFF 00012000
* clrjit 6ACC0000 6AD3CFFF 0007d000
* BatchParser 72480000 724A1FFF 00022000
* ftimport 60000000 6001CFFF 0001d000
* MSFTE 49910000 49B68FFF 00259000
* dbghelp 71440000 71580FFF 00141000
* dssenh 722A0000 722C5FFF 00026000
* mswsock 72FC0000 72FFAFFF 0003b000
* wship6 71E50000 71E54FFF 00005000
* wshtcpip 71E10000 71E14FFF 00005000
* NLAapi 712D0000 712DEFFF 0000f000
* IPHLPAPI 71040000 71058FFF 00019000
* dhcpcsvc 70750000 70784FFF 00035000
* WINNSI 72FB0000 72FB6FFF 00007000
* dhcpcsvc6 6AD90000 6ADB1FFF 00022000
* napinsp 70870000 7087EFFF 0000f000
* winrnr 70740000 70747FFF 00008000
* rasadhlp 71010000 71015FFF 00006000
* System.ni 6ED70000 6F709FFF 0099a000
* System.Data 6B390000 6B6A2FFF 00313000
* System.Transactions 6DB20000 6DB66FFF 00047000
* System.Security.ni 6D7A0000 6D855FFF 000b6000
* System.Xml.ni 708B0000 71000FFF 00751000
* xpsqlbot 740A0000 740A6FFF 00007000
* xpstar 6D450000 6D49DFFF 0004e000
* ATL100 73490000 734B5FFF 00026000
* SQLSCM 72470000 7247AFFF 0000b000
* ODBC32 71600000 71665FFF 00066000
* odbcint 71400000 71437FFF 00038000
* xpstar 70880000 708A4FFF 00025000
* xplog70 740B0000 740BDFFF 0000e000
* xplog70 71250000 71252FFF 00003000
* apphelp 74A50000 74A7BFFF 0002c000
* dbghelp 71ED0000 72010FFF 00141000
*
* Edi: 0D62D84C: 00310000 00640065 00380033 00390039 00660066 00660066
* Esi: 00000022:
* Eax: 0D62D6C4: C000000D 00000000 00000000 7598D8CB 00000000 58EB17FC
* Ebx: 0D62D898: 84281FA0 8427E548 0501133C 0D62D8D8 84281FA0 6D1AE200
* Ecx: 84C2000B: 5C000100 01B6F500 1C000100 00010900 72075600 01B6F418
* Edx: 00000000:
* Eip: 7598D8CB: 0010C2C9 06FA8366 F493840F 83660001 0C7509FA D81846C7
* Ebp: 0D62D714: 0D62D750 6E272E6D C000000D 00000000 00000000 00000000
* SegCs: 00000023:
* EFlags: 00000246:
* Esp: 0D62D6C4: C000000D 00000000 00000000 7598D8CB 00000000 58EB17FC
* SegSs: 0000002B:
* *******************************************************************************
* -------------------------------------------------------------------------------
* Short Stack Dump
7598D8CB Module(kernel32+0001D8CB)
6E272E6D Module(sqldk+000B2E6D)
733DD3B2 Module(MSVCR100+0005D3B2)
58EB1645 Module(sqllang+00141645)
58EB351E Module(sqllang+0014351E)
58EAF94A Module(sqllang+0013F94A)
58EAFBB0 Module(sqllang+0013FBB0)
59B7C745 Module(sqllang+00E0C745)
59B7CAC4 Module(sqllang+00E0CAC4)
6E1F0941 Module(sqldk+00030941)
6E1F0D6D Module(sqldk+00030D6D)
6E1F0B9E Module(sqldk+00030B9E)
6E1C83E6 Module(sqldk+000083E6)
6E1C8514 Module(sqldk+00008514)
6E1C7F3A Module(sqldk+00007F3A)
6E1C8268 Module(sqldk+00008268)
733DC556 Module(MSVCR100+0005C556)
733DC600 Module(MSVCR100+0005C600)
759FF299 Module(kernel32+0008F299)
771CD819 Module(ntdll+0007D819)
771CDA2B Module(ntdll+0007DA2B)
CSession @0x84280110
--------------------
m_sessionId = 12 m_cRef = 8 m_rgcRefType[0] = 1
m_rgcRefType[1] = 0 m_rgcRefType[2] = 5 m_rgcRefType[3] = 1
m_rgcRefType[4] = 0 m_rgcRefType[5] = 1 m_pmo = 0x84280028
m_pstackBhfPool = 0x00000000 m_dwLoginFlags = 0x0000 m_fBackground = 1
m_eConnResetOption = 0 m_fUserProc = 0 m_fConnReset = 0
m_fIsConnReset = 0 m_fInLogin = 0 m_fAuditLoginSent = 0
m_fAuditLoginFailedSent = 0 m_fReplRelease = 0 m_fKill = 0
m_ulLoginStamp = 318947 m_eclClient = 7 m_protType = 0
m_hHttpToken = FFFFFFFF
m_pV7LoginRec
---------------------
00000000: 00000000 00000000 00000000 00000000 00000000 ....................
00000014: 00000000 00000000 00000000 00000000 00000000 ....................
00000028: 00000000 00000000 00000000 00000000 00000000 ....................
0000003C: 00000000 00000000 00000000 00000000 00000000 ....................
00000050: 00000000 00000000 00000000 0000 ..............
CBatch @0x84280FD0
------------------
m_pSess = 0x84280110 m_pConn = 0x84280780 m_cRef = 2
m_rgcRefType[0] = 1 m_rgcRefType[1] = 1 m_rgcRefType[2] = 0
m_rgcRefType[3] = 0 m_rgcRefType[4] = 0 m_pTask = 0x9983D468
EXCEPT (null) @0x0D62B50C
-------------------------
exc_number = 0 exc_severity = 0 exc_func = 0x6E273DA6
Task @0x9983D468
----------------
CPU Ticks used (ms) = 0 Task State = 2
WAITINFO_INTERNAL: WaitResource = 0x00000000 WAITINFO_INTERNAL: WaitType = 0x0
WAITINFO_INTERNAL: WaitSpinlock = 0x00000000
WAITINFO_EXTERNAL: WaitResource = 0x00000000
WAITINFO_EXTERNAL: WaitType = 0x200002DF
WAITINFO_EXTERNAL: WaitSpinlock = 0x00000000 SchedulerId = 0x2
ThreadId = 0x11b0 m_state = 0 m_eAbortSev = 0
EC @0x84280820
--------------
spid = 0 ecid = 0 ec_stat = 0x0
ec_stat2 = 0x0 ec_atomic = 0x0 ecType = 0
__pSETLS = 0x842807C0 __pSEParams = 0x84281240
SEInternalTLS @0x842807C0
-------------------------
m_flags = 0 m_TLSstatus = 3 m_owningTask = 0x9983D468
m_activeHeapDatasetList = 0x842807C0 m_activeIndexDatasetList = 0x842807C8
m_pDbccContext = 0x00000000 m_pAllocFileLimit = 0x00000000 m_dekInstanceIndex = 0x-1
m_pImbiContext = 0x00000000
SEParams @0x84281240
--------------------
m_lockTimeout = -1 m_isoLevel = 4096 m_logDontReplicate = 0
m_neverReplicate = 0 m_XactWorkspace = 0x8307ADA8 m_execStats = 0x02BE0E30
What should I do? The db seems to be operating perfectly except for these. And how do I rid myself of the huge exception.log? How do I monitor for future issues?
Jim
January 9, 2014 at 11:40 am
Read up on sp_cycle_errorlog in BOL and see if it will help you here.
There are unix-type tools out there you can run on windows that will allow you to take a look at parts of files without having to open the entire file. There are file splitters too that could be used to bring it down to manageable-sized chunks that can be opened.
I would also take a look at TextPad - amazing functionality! I have been using it for over a decade now and have had files well over 1GB open in it.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
January 9, 2014 at 11:49 am
Also...may be...you can consider to limit the size of your error log besides recycling on regular basis, since you are running on SQL Server 2012.
http://www.sqlskills.com/blogs/paul/limiting-error-log-file-size-in-sql-server-2012/
But, First of all...I would worry why SQL is generating those dumps.
January 9, 2014 at 12:35 pm
I am worried....
That's why I included a sample log so someone could point me to what's wrong.
Jim
January 9, 2014 at 1:00 pm
What's the current Build # your SQL Server is running at?
Looks like you are running on 32 bit architecture from the message posted.
Computer type is Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz.
4 Intel x86 level 6, 14 Mhz processor (s).
"EXCEPTION_INVALID_CRT_PARAMETER" on System Health Monitor Thread in SQL Server 2012" is a Known bug in SQL Server 2012(SP1) running on 32 bit Servers which got fixed in SP1+CU4. Am not 100% sure you got hit by this bug, but please go through this KB article which might help you.
January 9, 2014 at 1:43 pm
Running SQL Server 11.0.3128
Jim
January 9, 2014 at 1:54 pm
Looks like "11.00.3128" is SP1+ 2793634 Hotfix.
2012 SP1 has some nasty bugs w.r.t Memory(See this blog post if you are curious...An interesting read http://lokna.no/?p=1251) .
Personally, I would recommend to update to SP1+CU5 at least. SQL Server 2012 SP1 without any CU being applied has a very bad reputation AFAIK especially in terms of memory related bugs.
FYI, SP1+CU7 is the latest which got released on Nov 16th 2013.
January 9, 2014 at 1:57 pm
I'm downloading CU7, I think. The download asked me to choose a download. It didn't give me any information to differentiate how to choose one of the choices...what's up with that? Anyway, I assume it'll refuse to work if it's the wrong choice, and I assume I was just choosing a download site...who knows. Do you?
Jim
January 9, 2014 at 2:24 pm
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2894115&kbln=en-us
Highlighted in the attachment is what you need if you are planning to Install CU7, as you've got 32 Bit server.
January 9, 2014 at 3:16 pm
Thank you so much, I am way out of my depth here. My client wants the server, but doesn't want to manage it or pay anyone else to manage it, so I muddle through. I only just realized what was eating up my disk space. I hope this resolves it. Downloading now.
BTW, what a crazy selection on that ms web site...why would I choose one or the other (I understand about x86 versus x64...)?
Thanks again!
Update: The CU7 install worked, and I'm back in business. We'll see about all the stack dumps....Thanks again!
Jim
January 10, 2014 at 12:54 pm
FWIW, I got CU7 installed and rebooted. Deleted over 10,000 stack dump sets from the log file. Overall, reduced used space by 10 GB. All said and done went from a disk that was full to a disk with 133GB available. No stack dumps since CU7 was installed.
I do have several .trc files (log_68.trc, etc.) I don't know where they came from, but several are dated yesterday. I tried double clicking them, but profiler said "file not found" not specifying the file it couldn't find.
I can now successfully open the Profiler and start a new trace. I couldn't connect yesterday....
What do I do to get rid of the half-dozen trc files left in the log folder? Can I just delete them?
Jim
January 10, 2014 at 1:23 pm
That's good to hear 🙂
It is safe to delete old .trc files(It doesn't impact your SQL server Services). In general these files are created by SQL Server to save events to a physical file.
If you are sure, they aren't left behind by some one on purpose and no one needs them you can delete those old files.
SQL Server will create a default trace file anyways in your Log folder each time it gets restarted.(log.trc, log_1.trc,log_2.trc and so on).
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply