The reason I recommend restarting SQL because that is a quick way to troubleshoot the problem. If it doesn't help, you keep looking; if it helps then you know that it is a resources issue.
We have tuned AC to run in environments of 50+ users, and that takes custom tweaking, but it can be done.
All of our larger practices are now on SQL Standard, and it regularly runs 12-16G of RAM.
