Sometimes you will encounter the server at intervals of the crash, Ping, remote also landing, restart after resuming the situation, to find the reason can not find; in fact, in the system log file carefully looked up will find such an error:
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/6B/78/wKiom1UuMEmSX-fgAAHNE-wYCfA527.jpg "title=" 1111. PNG "alt=" wkiom1uumemsx-fgaahne-wycfa527.jpg "/>
This is caused by a memory leak.
A memory leak is due to an application or process allocation that consumes memory, but does not release memory when it is finished, causing memory to be full and leaking.
The root of the memory leak, find the error program to modify the program
Second, you can modify the registry so that memory consumption to a lower level is to clean up the memory, the system by default, memory reaches 80% when the memory, you can manually modify the registry
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
Change the value to a smaller value, such as 40 or 50.
This article is from the "Jx_ Trench linux" blog, so be sure to keep this source http://xujunxian.blog.51cto.com/8614409/1633058
Windows Server memory leak-event ID2019