We have found the problem on node. It was due to non-paged memory limit.
NP pool on Windows 2003 x86 systems has limit 256 MB, it used for kernel operations (drivers), GUI and some others. In case NP pool is overloaded, the system becomes slow and unresponsive, some software components can't work normally (for example IIS Web Server refuses connections).
NP pool memory leaks can be caused by incorrect software work or malware. So if this problem happens we have to find out the process on main node and kill it, which is utilizing extra non-paged memory pool.
Another possible reason could be that the process which consumes non-paged pool memory could be a kind of malware. So in this case it is necessary to kill one at the first and then check VE with antivirus software
|