This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 91%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDP%3C/text%3E%3C/svg%3E)
Failed allocate pages: FAIL_PAGE_ALLOCATION
This happens now and then on one of our SQL Server and it becomes unresponsive.
The only solution is to restart the server, we already capped max memory with13 GB and box is running with 16GB RAM.
We don't want to increase the resources, is there any bug on SP1 which is causing the memory pool issue.
First of all, install the most recent service pack for SQL 2016, which is SP3.
Next, yes, you should try add more memory. 16 GB is not a lot for SQL Server these days.
Most likely this is an issue with your workload. Since we don't know anything about it, we cannot say much. But usually, there is a dump of used memory in the SQL Server errorlog when this happens. You can use this to see where the memory is being spent.
Hi Erland,
tThanks for the reply, in the log there are multiple entries, which tag will give me details of memory being spent. like MEMORYBROKER_ <> or MEMORYCLERK_SQLS
Yes, there is usually a long output in these situations. It is not that easily decipherable. Could you extract that part and upload it here? Please work from the ERRORLOG file, not from the grid in SSMS.
Hi @Anonymous ,
> is there any bug on SP1 which is causing the memory pool issue.
Firstly I would suggest you apply the latest SP3 to SQL 2016 as Erland mentioned. You can get it from this link.
Then please follow below MS document to troubleshot your issue.
If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar thread.
Sure, we will definitely apply SP3 but before that we need to fix this. if the issue is with SP1 then we can inform customer to go for SP3.
No, apply SP3 before anything else. SP1 is completely unsupported. SP3 is at least in extended support. And would the issue actually be due to a bug in SQL 2016 SP1 which has been fixed, that's all you need to do. (I would not hold my breath, though.)