Applies ToSQL Server 2016 Enterprise Core - duplicate (do not use) SQL Server 2016 Enterprise - duplicate (do not use) SQL Server 2016 Developer - duplicate (do not use) SQL Server 2016 Standard - duplicate (do not use) SQL Server 2017 on Windows (all editions) SQL Server 2014 Service Pack 2 - duplicate (do not use) SQL Server 2014 Developer - duplicate (do not use) SQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Enterprise Core - duplicate (do not use) SQL Server 2014 Standard - duplicate (do not use)

Symptoms

When you run the "select contention_factor from sys.dm_os_memory_objects" statement in the SQL Server monitor tool to monitor the SQL Server database, an error message that resembles the following is logged in the SQL Server error log:

Date/Time SPID SqlDumpExceptionHandler: Process 56 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.Date/TimeSPID * *******************************************************************************Date/TimeSPID *Date/TimeSPID * BEGIN STACK DUMP:Date/TimeSPID * Date/TimeSPIDDate/TimeSPID *Date/TimeSPID * Exception Address = 00007FFB8EE5015D Module(sqlmin+00000000004F015D)Date/TimeSPID * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATIONDate/TimeSPID * Access Violation occurred reading address 0000000000000020Date/TimeSPID * Input Buffer 136 bytes -Date/TimeSPID * SELECT contention_factor FROM sys.dm_os_memory_objects;

Resolution

This fix is included in the following cumulative updates for SQL Server:

Cumulative Update 1 for SQL Server 2017

Cumulative Update 5 for SQL Server 2016 Service Pack 1

Cumulative Update 11 for SQL Server 2014 SP2

Service Pack information for SQL Server

This fix is included in the following service pack for SQL Server:

Service Pack 3 for SQL Server 2014 

About SQL Server builds

Each new build for SQL Server 2016 contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2017

latest build for SQL Server 2016

Latest cumulative update for SQL Server 2014

Service packs are cumulative. Each new service pack contains all the fixes that are in previous service packs, together with any new fixes. Our recommendation is to apply the latest service pack and the latest cumulative update for that service pack. You do not have to install a previous service pack before you install the latest service pack. Use Table 1 in the following article for finding more information about the latest service pack and latest cumulative update.

How to determine the version, edition and update level of SQL Server and its components

Status

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

References

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

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.