Originally Posted by
NitroPye
Incorrect.
(Disclaimer: This is an over simplification of a complex topic) Machines crash when a program tries to write to RAM that isn't there typically. If you've maxed out the available RAM on your machine any modern o/s will properly handle swap (as in use your disk as RAM for non active applications). The only times when running your machine with the RAM full (which my machine is typically at 90% used when working) are when the O/S incorrectly handles the swapping and tries to write to non existent RAM which usually just will result in the program crashing. Now if it accidentally writes over RAM in use, more specifically where the kernel resides you will get a full system crash. This has little to do with running with minimal free RAM and almost all to do with the operating system making a mistake.
I am talking about timings and clock speeds. Like DDR400 running at 250 (500 effective) can become very unstable. You can
try to recover some stability by slacking your timings (instead if 2-2-2-5 you could use 3-4-4-12). Also up the voltage. My ram is rated 2-2-2-6 at 200mhz (ddr400) but at 2.8v, I run it at 2.9 just in case.
So what I mean is when you are trying to get more performance from your ram you will encounter crashes due to corrupt data reading/writing.