[dnr]

I ran a baseline tracking my memory usage through Win 7 Resource Monitor hoping to find evidence of memory leakage as the cause by my thrashing problem. Taking cold start data I ran the same scenarios in sequence and recorded the memory allocation at the conclusion of each mission. Most of the time it all looked pretty normal, but after the third mission on Thursday 16 Dec 11 as I pulled up the resource monitor window the standby memory was filling up before my eyes as the free space dropped to zero. I think this might have been a memory dump from the virtual memory paging setup back to the RAM. Needless to say my rig didn't respond well to that so I shut down and followed the same sequence on Fri night (17 Dec). The system finally locked up after about three hours of run time. I then swapped out the Kingston HyperX DDR3 1600 for some sexy new G.Skill Ripjaws DDR3 PC3 12800 16GB. I can say that there is a noticible difference in CLoD performance as motion tracking is smoother, less judder on the geo layers and my rid remained stable for over four hours through three full missions and a couple of hours in mission builder setting up and testing new scenarios. At about 0017 hrs Saturday morning CLoD had finally had enough and it frooze. Difference was that my rig kept running just fine. I pulled up the resource monitor and still had bags of free memory remaining. Data that I collected is attached if its of use to anyone out there considering adding more RAM as a solution to their memory leaks and thrashing problems. I think Klem was right, this does not solve the programming problem, Win 7 might not even be using all that RAM properly, but this does delay total lockup long enought to get a more enjoyable experience out of CLoD.