SQL Server goes into suspect mode

I have a situation where one of our customer's database goes into suspect mode, and I am looking to understand what we can do to help their situation. Here is some background on the issue.

Our application is a web app hosted on the JBoss. The application is configured for about 500 XA DB connections. This is needed for the high load. From time to time they notice the following error in the logs

Logon Error: 17189, Severity: 16, State: 1.
2017-07-14 09:11:41.32 Logon SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems. [CLIENT: 10.11.210.38] 
...
spid805 Error: 8510, Severity: 20, State: 3.
2017-07-14 09:15:00.89 spid805 Enlist operation failed: 0x8007000e(Not enough storage is available to complete this operation.). SQL Server could not register with Microsoft Distributed Transaction Coordinator (MS DTC) as a resource manager for this transaction. The transaction may have been stopped by the client or the resource manager.
...
2017-07-14 09:15:17.10 Server Error: 701, Severity: 17, State: 226.
2017-07-14 09:15:17.10 Server There is insufficient system memory in resource pool 'internal' to run this query. 

And the database restarts, and goes into Suspect mode. After some digging, it appears that this could be related to the following bug,

https://support.microsoft.com/en-us/help/890425/you-receive-a-not-enough-storage-is-available-to-complete-this-operati

Also, we recommended the following configuration in the database. https://msdn.microsoft.com/en-us/library/ms179586%28v%3Dsql.110%29.aspx

The idea here was that even though the database goes down, it would come up automatically without any intervention. But this does not seem to work either.

I am not a database expert, nor do I have access Microsoft support to get more help on this, so I hope somebody can point me in the right direction for this issue.

Thanks,