Incorrect memory page accounting may cause a wider variety of out-of-memory errors (701, 802, and so on) and performance issues in Microsoft SQL Server. You can investigate theis behavior in more detail by looking at the Memory Node Object and Buffer Manager performance counters by considering the following conditions:
One of the "Memory Node: Database Node Memory (KB)" counters exceeds its Target Node Memory counter on the same node.
One of the "Memory Node: Database Node Memory (KB)" counters drops below 2 percent of its "Memory Node: Target Node Memory" counter for the same node.
The value of the "Buffer Manager: Free list stalls/sec" counter spikes.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Cumulative Update Information
This problem is fixed in the following 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:
Service Pack Information for SQL Server 2016
This problem is fixed in the following service pack for SQL Server:
Service packs are cumulative. Each new service pack contains all the fixes that are in previous service packs, together with any new fixes. We recommend that you 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 to find more information about the latest service pack and latest cumulative update.
Learn about the terminology that Microsoft uses to describe software updates.