Even though you might get the above error message for different occasions, one thing is for sure, it has to do with memory management. :)
SQL Server allows you to limit the maximum memory that can be utilized by its Database Engine. You can use this feature in order to allow the OS to have access to memory that cannot be used by SQL Server and thus ensure stability.
As described on an
MSDN Library article, the above command will cause
Resource Governor to resets statistics on all workload groups and resource pools including the "internal" resource pool.
Action 2:
If the above action does not solve the issue you can try to free-up more memory and eventually upgrade the memory capacity of the machine.