Looking at the symptom dump file, I could clearly see it was an AV (Access Violation) SqlDumpExceptionHandler: Process 3162 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. Fortunate enough, I found a symptom dump (SQLDump0001.txt) and a minidump file (SQLDump0001.mdmp) in \LOG folder generated that day. However, the issue originally started a week back and relevant ERRORLOG was been overwritten. I’d typically start troubleshooting such issues by looking at the ERRORLOG. The spid was now stuck in a “killed/rollback” state since last one week. User found the spid in a ‘hung’ state hence killed the spid. It was SQL Server 2008 (SP2) – where a user had initiated transaction log backup for a database. The troubleshooting and resolution was quite interesting making me to write this blog. I recently worked on an interesting case where reportedly the log backup for a database was ‘hung’.
