Assume that an instance of Microsoft SQL Server 2016 restarts, for example, because of a system restart. During startup, if SQL Server tries to start Query Store Manager, you may receive an access violation error intermittently. Because of the access violation, SQL Server fails to start automatically. Therefore, you may have to start SQL Server manually. Additionally, an error message that resembles the following is logged in the SQL Server error log:

Date/Time Starting up database 'master'.
Date/Time Using 'dbghelp.dll' version '4.0.5'
Date/Time ***Stack Dump being sent to FilePath\FileName
Date/Time SqlDumpExceptionHandler: Process 5 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Date/Time * *******************************************************************************
Date/Time *
Date/Time * Date/Time
Date/Time *
Date/Time *
Date/Time * Exception Address = 00007FFF2BF59AFB Module(sqlmin+00000000011D9AFB)
Date/Time * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
Date/Time * Access Violation occurred reading address 0000000000000000
Date/Time *
Date/Time *


This issue is fixed in the following cumulative updates for SQL Server:

Cumulative Update 4 for SQL Server 2016 Service Pack 2

Each new cumulative update for SQL Server contains all the hotfixes and security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2016

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!