Skip to content

mssqlserver-854-database-engine-error.md

Latest commit

 

History

History
46 lines (35 loc) · 2.43 KB

mssqlserver-854-database-engine-error.md

File metadata and controls

46 lines (35 loc) · 2.43 KB
title MSSQLSERVER_854
description MSSQLSERVER_854
author rwestMSFT
ms.author randolphwest
ms.reviewer jopilov, mathoma
ms.date 08/20/2020
ms.service sql
ms.subservice supportability
ms.topic reference
helpviewer_keywords
854 (Database Engine error)

MSSQLSERVER_854

[!INCLUDE SQL Server]

Details

Attribute Value
Product Name SQL Server
Event ID 854
Event Source MSSQLSERVER
Component SQLEngine
Symbolic Name HARDWARE_MEMORY_SCRUBBER
Message Text Machine supports memory error recovery. SQL memory protection is enabled to recover from memory corruption

Explanation

This message indicates the hardware in the operating system supports the ability to recover from memory errors. On computers that have newer hardware and are running Windows Server 2012 or a later version, the hardware can notify the operating system and applications that memory pages (operating system pages) are marked as bad or damaged. Applications such as [!INCLUDEssNoVersion] can register these bad memory page notifications by using the following API set:

  • GetMemoryErrorHandlingCapabilities
  • RegisterBadMemoryNotification
  • BadMemoryCallbackRoutine

[!INCLUDEssNoVersion] adds support for these notifications in Microsoft [!INCLUDEssNoVersion] 2012 and later versions. During [!INCLUDEssNoVersion] startup, [!INCLUDEssNoVersion] checks whether the hardware supports this new feature. Additionally, you receive the following message in the error log:

<Datetime> Server Machine supports memory error recovery. SQL memory protection is enabled to recover from memory corruption.

User action

Check if you are encountering other errors like 855 and 856 and take appropriate corrective action.

More information

You can use [!INCLUDEssNoVersion] trace flag 849 to keep [!INCLUDEssNoVersion] from registering with the operating system for memory error notifications. However, be aware that enabling trace flag 849 will prevent [!INCLUDEssNoVersion] from receiving bad memory notifications from operating system. Therefore, we do not recommend that you use this trace flag under typical circumstances.