The article is about any 32-bit OS, and the memory limitations associated with it. The max amount of memory a 32-bit OS can recognize is 4GB. Of the 4GB, only 2GB of memory is available to any program and that includes all background services (antivirus can be a major memory hog), with the remaining 2GB of memory used exclusively for the OS. If it ever gets to a point that you hit the max of 2GB and exceed it, as mentioned in the article, whether due to newer games with much larger memory requirements or memory leaks, the game will crash with no warning. Since certain areas are added to memory linearly when a new area is added, this can lead to the 2GB being exceeded at exactly the same point in the game and thus why the crash keeps occurring. The article explains in depth what I have above, and mentions ways to increase the 2GB limit, but at the possible cost of stability in the OS.Also, this 2GB limit is independent of the amount of RAM you have. Regardless if you have 1GB or 4GB, there is always 4GB available. If you do not physically have the RAM, it uses virtual memory on your hard drive (which is where defragging regularly and faster RPM hard drives helps greatly) which is your page file. Hence why you want to have the page file set to min/max "4096" which is 4GB. This way regardless of the amount of physical RAM, you always have the entire amount of memory covered. But definitely try the article's recommendation to increase the 2GB limit, even just by a small amount, and see if the crashing continues. This would determine if it's a memory problem or a game error. I'm willing to bet the majority of crashes at a certain point, or after hours of playing, is based on memory management.
