FIX: Memory dumps generate when access violation occurs in SQL Server 2016

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core


Assume that you create a distributed availability group by using automatic seeding in Microsoft SQL Server 2016. You will periodically receive a series of memory dumps that resemble the following when access violation occurs:
Stack Dump being sent to FilePath
SqlDumpExceptionHandler: Process ProcessId generated fatal exception ExceptionId EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
*   04/17/19 04:28:00 spid SpidId
*   Exception Address = AddressId Module(sqlmin+00000000007C73A6)
*   Exception Code    = CodeId EXCEPTION_ACCESS_VIOLATION
*   Access Violation occurred reading address AddressId


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


This issue is fixed in the following cumulative update for SQL Server:
About cumulative updates for SQL Server:
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:


Learn about the terminology that Microsoft uses to describe software updates.