Symptoms
When you retrieve an SQL statement hash for logging XEvent in Microsoft SQL Server 2012 or in Microsoft SQL Server 2014, SQL Server may crash. Additionally, you receive the following error message:
spid<ID> **Dump thread - spid = <ID>, EC = 0x00000000968B4160spid<ID> ***Stack Dump being sent to <File Path>\SQLDump0003.txtspid<ID> * *******************************************************************************spid<ID> *spid<ID> * BEGIN STACK DUMP:spid<ID> * <Date> <Time>spid <ID>spid<ID> *spid<ID> * ex_terminator - Last chance exception handlingspid<ID> *spid<ID> * spid<ID> *spid<ID> * MODULE BASE END SIZEspid<ID> * sqlservr 000007F6C01A0000 000007F6C01F9FFF 0005a000spid<ID> * ntdll 000007FFB2F30000 000007FFB30EFFFF 001c0000spid<ID> * KERNEL32 000007FFB07B0000 000007FFB08E5FFF 00136000spid<ID> * KERNELBASE 000007FFB0040000 000007FFB0133FFF 000f4000spid<ID> * SYSFER 000000005A5E0000 000000005A666FFF 00087000
Resolution
The issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 5 for SQL Server 2014 /en-us/help/3011055
Cumulative Update 3 for SQL Server 2012 SP2 /en-us/help/3002049
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
