Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


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 = 0x00000000968B4160
spid<ID> ***Stack Dump being sent to <File Path>\SQLDump0003.txt
spid<ID> * *******************************************************************************
spid<ID> *
spid<ID> * <Date> <Time>spid <ID>
spid<ID> *
spid<ID> * ex_terminator - Last chance exception handling
spid<ID> *
spid<ID> *
spid<ID> *
spid<ID> * sqlservr 000007F6C01A0000 000007F6C01F9FFF 0005a000
spid<ID> * ntdll 000007FFB2F30000 000007FFB30EFFFF 001c0000
spid<ID> * KERNEL32 000007FFB07B0000 000007FFB08E5FFF 00136000
spid<ID> * KERNELBASE 000007FFB0040000 000007FFB0133FFF 000f4000
spid<ID> * SYSFER 000000005A5E0000 000000005A666FFF 00087000

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:


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!