December 29, 2016 at 11:31 am
One of the PRD server got hung due to SQLDump(Crash Dump Files) were generating every seconds and put it into SQL System drive.
I tried to delete some of the files but it was filling up again within in minutes. So, I had to reboot SQL service and it got stopped.
Any idea what cause these dump files to be generated ? I looked at the error log and didn't make much sense to me...
Let me know if anyone encounter similar situation.
Here is some sample errors from the log.
External dump process returned no errors.
2016-12-28 14:00:52.66 spid35s Error: 17312, Severity: 16, State: 1.
2016-12-28 14:00:52.66 spid35s SQL Server is terminating a system or background task SSB Task due to errors in starting up the task (setup state 8).
2016-12-28 14:00:52.66 spid35s Error: 18054, Severity: 16, State: 1.
2016-12-28 14:00:52.66 spid35s Error 28709, severity 16, state 19 was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage.
2016-12-28 14:00:52.66 spid35s Error: 9602, Severity: 16, State: 1.
2016-12-28 14:00:52.66 spid35s Failed to start a system task with error code 28709, state 19.
2016-12-28 14:00:53.18 spid43s Using 'dbghelp.dll' version '4.0.5'
2016-12-28 14:00:53.18 spid43s ***Stack Dump being sent to F:\MSSQL2012\install\MSSQL\LOG\SQLDump2468.txt
2016-12-28 14:00:53.18 spid43s SqlDumpExceptionHandler: Process 43 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2016-12-28 14:00:53.18 spid43s * *******************************************************************************
2016-12-28 14:00:53.18 spid43s *
2016-12-28 14:00:53.18 spid43s * BEGIN STACK DUMP:
2016-12-28 14:00:53.18 spid43s * 12/28/16 14:00:53 spid 43
2016-12-28 14:00:53.18 spid43s *
2016-12-28 14:00:53.18 spid43s *
2016-12-28 14:00:53.18 spid43s * Exception Address = 000007FFBB247174 Module(UNKNOWN+0000000000000000)
2016-12-28 14:00:53.18 spid43s * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
2016-12-28 14:00:53.18 spid43s * Access Violation occurred reading address 0000000000000008
2016-12-28 14:00:53.18 spid43s *
2016-12-28 14:00:53.18 spid43s *
2016-12-28 14:00:53.18 spid43s * MODULE BASE END SIZE
2016-12-28 14:00:53.18 spid43s * sqlservr 000007F740D70000
2016-12-28 14:00:53.18 spid43s * ntdll 000007FFCBF10000
2016-12-28 14:00:53.18 spid43s * KERNEL32 000007FFCBC60000
2016-12-28 14:00:53.18 spid43s * KERNELBASE 000007FFC9180000
2016-12-28 14:00:53.18 spid43s * ADVAPI32 000007FFC9750000
2016-12-28 14:00:53.18 spid43s * MSVCR100
Regards,
SQLisAwe5oMe.
December 29, 2016 at 11:38 am
One possibility is that you are running into a bug that was addressed in one of the CUs for 2012. You may want to check this KB article from MS:
https://support.microsoft.com/en-us/kb/972936
Sue
December 29, 2016 at 11:49 am
Thanks Sue for the quick response.
I will look into this. Thanks again.
Regards,
SQLisAwe5oMe.
January 3, 2017 at 10:07 pm
This was removed by the editor as SPAM
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply