From your VASQuery output, it appears that you are running a 32 bit (not 64 bit) SQL Server and that you have enabled CLR. The CLR is known to be a huge memory hog and the Microsoft recomendation is to avoid using it on 32 bit SQL Server.

Having said that there are a couple of things you can do to have DBAmp "survive" in a low VAS memory system. I first need to know what version of DBAmp you currently have installed (run the DBAmp Configuration Program menu choice Help/About).

The bottom line is that you have a limited amount of VAS memory on a 32 bit SQL to share with 4 different providers with CLR memory being allocated at some point or by something. One alternative would be to run DBAmp "out-of-process" which is doable with certain caveats.

I adjusted the RAM Available to SQL up by 4gb (Since the VAS calculation is partially based on that value) and restarted the services after cleaning up some linked servers. We have been fine since then with the following numbers.

If by "cleaning up" the linked servers you mean that you removed them, then that will ease memory pressure. All linked servers share the same VAS memory. Fewer linked servers means more memory for the survivors.