Tom Van Harpen - Monday, March 20, 2017 11:48 AM

For the 3rd time in as many weeks, we've had a SQL 2012 sp1 instance go down. 

Couple changes that were made: 
Add a linked server type:SQLSERVER and running Sp_blitz and using the linked server to send data back to our management SQL Server. (this job was not running so i guess i cant blame Brent)
Added CommVault backup agent and started running CommVault backups, however the first crash occurrence was before we implemented this. 

There is no information in the SQL Logs. The last event was a tranlog backup then the next log entry was the service starting back up.

Event viewer had a single entry for the crash (aside from the one saying it terminated unexpectedly)

Faulting application name: sqlservr.exe, version: 2011.110.3000.0, time stamp: 0x5082086a
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x1178
Faulting application start time: 0x01d29c04eedd742a
Faulting application path: C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: eb0621d9-0cce-11e7-a90d-005056a90e7f

Looking for any thoughts, suggestions, or direction on how to further troubleshoot this or capture more data if it happens again.

Thanks