We just got a single EXCEPTION_ACCESSS_VIOLATION error on a production box, the process was apparently killed but the server continued.
How seriously does one want to take this, and what is a good standard operating procedure for it?
I know this is pretty basic stuff, but hey it turns out nobody else is doing anything about it, so I may be volunteering - and I don't really know! All praise to modern hardware, but I haven't been around these much for a long, long time.
Thanks.
Josh
2013-04-29 16:42:12.920 ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\LOG\SQLDump0007.txt 2013-04-29 16:42:12.920 SqlDumpExceptionHandler: Process 100 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. 2013-04-29 16:42:12.920 * ******************************************************************************* 2013-04-29 16:42:12.920 * 2013-04-29 16:42:12.920 * BEGIN STACK DUMP: 2013-04-29 16:42:12.920 * 04/29/13 16:42:12 spid 100 2013-04-29 16:42:12.920 * 2013-04-29 16:42:12.920 * 2013-04-29 16:42:12.920 * Exception Address = 0000000001064010 Module(sqlservr+00000000000E4010) 2013-04-29 16:42:12.920 * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION 2013-04-29 16:42:12.920 * Access Violation occurred reading address 0000000000000188 2013-04-29 16:42:12.920 * Input Buffer 255 bytes -