Did not see a similar subject on an initial search, so here goes:In an attempt to make a small upgrade to my existing computer before I really dig in to replace it within the next 12 months, I swapped out my existing Intel P4 530 3.0 processor for a 'new' used Intel P4 650 3.4. There are the obvious differences/improvements, in addition to doubling of the cache to a 2 MB L2 Advanced Transfer Cache, over my previous 1 MB.I checked before I bought this, and my motherboard can handle this processor, and everything seems to be running fine.....ButWhen I used FS for the first time today, I ran out of memory right towards the end of my 4 hour flight. This has never happened before, and I'm wondering if I need to adjust my virtual memeory for any reason with this processor.Here are what my CPU-Z program indicates with the new processor installed and running. I thought a more experienced hardware guru might see something in these numbers:Core speed=3391.4 +/-Multiplier=x17.0Bus Speed=199.5 MHzRated FSB=798.0 MHzL1 Data=16 KBytesL2 Trace=12 KuopsLevel 2=2048 KBytesAnd some additional memory info (from MSINFO as it is running 'right now'):Total Physical Memory = 2,048.00 MBAvailable Physical Memory = 1.36 GBTotal Virtual Memory = 2.00 GBAvailable Virtual Memory = 1.95 GBPage File Space = 5.76 GBIn addition attached is more complete info via Sandra...Thanks in advance

mmmm.....I think I might have found the culprit,,,,I've been using 'snapper' to take screen shots during flights lately, and noticed (after shutting down FS, and during, by hitting Ctrl+Alt+Delete and going to the Task Manager) it increases it's memory usage the more often I use it. I saw it registering as much as 180,000k +. In and of itself (as I have 2 gig's of memory), that isn't much, but with everything else going on in FS while flying, I have a feeling it may have 'pushed the memory over the edge'.I had been using FSScreen, but it was not 'playing nice' with Flight Assistant, so I stopped using it. Perhaps it is time to re-look at finding a way of using FSScreen, as I don't remember that happening before.Anyone else seen this type of memory usage with this program?