FIX: EXCEPTION_ACCESS_VIOLATION for query using sys.dm_os_memory_objects statement in SQL Server

Attiecas uz: SQL Server 2016 Enterprise CoreSQL Server 2016 EnterpriseSQL Server 2016 Developer Vēl

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/Time SPID * *******************************************************************************
Date/Time SPID *
Date/Time SPID * BEGIN STACK DUMP:
Date/Time SPID * Date/Time SPID
Date/Time SPID *
Date/Time SPID * Exception Address = 00007FFB8EE5015D Module(sqlmin+00000000004F015D)
Date/Time SPID * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
Date/Time SPID * Access Violation occurred reading address 0000000000000020
Date/Time SPID * Input Buffer 136 bytes -
Date/Time SPID * 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 

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 Microsoft uses to describe software updates.