|Bad analogy in #13 with trying to clean the gas tank while the engine is running, because we are talking about flow of information, not flow of fuel. A better analogy could be a person getting electric shock therapy. You could in theory induce a memory into a brain using electricity, you could also erase memory using the same thing. Clearing a persons memory may not improve the persons' performance (like clearing a cache doesn't necessarily improve a computers'), but if a rogue memory is causing an underlying problem, it may be good to remove the memory instead of repressing it.|
There is a way in Linux to simulate a reboot that would clear rogue memory leaking programs from the cache, I haven't found any particular way to do this in Windows. The people who know the problems and possible fixes for these situations aren't able to give you this support because Windows is a closed source proprietary software, end of discussion. These people can only tell you so much, and they themselves can only do so much without breaching infringement.
Memory management is not the same across operating system platforms as some here suggest, only the theory is the same (see #9). The way these systems actually allocate is completely different. Take android for instance, memory management/allocation is based primarily on the amount of times the system has called a particular program in recent time. The more times a person uses an application, this application gets allocated more memory so to start promptly and run smoothly. All programs under android are actually not turned off, they are just simply in idle. Whereas Windows and other like operating systems, all programs are not actually on until the user (or system) calls it to run. The system then allocates based on what the program needs to run, with the preferred performance wanted, and which program is being actively used.
To address the IE statements above, Internet browsers (like most programs) weren't built to idle for weeks. Browsers are simply built for trafficking through information on the internet or on your physical system for short periods like a day or two at the most with multiple restarts of the application. Windows doesn't know certain applications and their mistakes, and cannot simply choose to close off allocation to these programs based on how well they were built.
If we lived in a perfect world, all programs would know how much memory it needs, attempt to grab that memory, and hold on to that exact amount without giving up or taking away any memory to or from another. Also in this perfect world, the operating system would be smart enough to not allocate unnecessary memory to a rogue application. It could maintain its' performance by attempting to patch leaks that these rogue applications may have, be able to utilize a standby RAM or cache to perform these tasks without interrupting memory flow to all other programs, cut off flow to rogue applications, or possibly terminate/restart them. But, we don't live there.
My suggestion, develop a 'simulated' reboot type of program and that may solve these unwanted 'real' reboots, since Windows doesn't come with maintenance tools that cover 100% of the system. The type of tools given to fix and maintain Windows is kind of like only giving janitors just a broom and a screw driver.
Back to that analogy of shock therapy, a brain can confuse itself to a point of a coma, a full blown system restart might be the only way to bring it out of that coma. The brain is just a very sophisticated computer so, your computer will have those same moments of coma like states. Heed my warning and regularly restart.