Hi everyone,How many users are using a set paging file to manage there virtual memory, and are having CTD's. Following Nick's tuning guide, I set a paging file of 3172 (have 8GB DDR3 1600MHZ). When setting up windows 7 64 after building my new system a few months ago, I tuned everything including FSX following the guide, and also Ryan's as well. One thing I forgot to do, was set a user managed paging file of 3172, and noticed this yesterday, and changed it.After doing so, I did a flight in the NGX from KDFW to KTPA, and on app, when of course it gets quite busy setting up the MCP, FMC etc. When dialing in the Nav freq, I had a NGX.DLL crash, and that was the conclusion of that flight.That is my first CTD, after 100+ hours of flying this bird. Be interesting to see who else sets there own Paging file. I am going to set it back to windows managed, and do the same flight and see how it goes. Edit: Wonder how the Beta testers set up there paging file ? if they all had the same, ie windows managed or user managed ?

I was under the assumption that Windows 7 was masterful at controlling memory usage. Not sure you even need to touch the Paging File. Stick with *******' Tweaking tool and you should be just fine.

Paging file could be depleted. Defraggler will take care of it before starting windows, since this file is excluded from normal defraggingMore to read here about memory and other stuff.

I will Dylan. As a lot of people have followed Nick's guide tuning their system, and if they have followed it to the letter, then there is a lot of simmers out there with a user set paging file. for years, I always have set up windows this way, looks like the NGX changes all that, or I am still living behind the times, which is most likley.

Paging file could be depleted. Defraggler will take care of it before starting windows, since this file is excluded from normal defraggingMore to read here about memory and other stuff.

All back to windows managed now Jan, I use O&O defragger, to keep things in order. And thank you for the link.

Hi everyone,How many users are using a set paging file to manage there virtual memory, and are having CTD's. Following Nick's tuning guide, I set a paging file of 3172 (have 8GB DDR3 1600MHZ). When setting up windows 7 64 after building my new system a few months ago, I tuned everything including FSX following the guide, and also Ryan's as well. One thing I forgot to do, was set a user managed paging file of 3172, and noticed this yesterday, and changed it.After doing so, I did a flight in the NGX from KDFW to KTPA, and on app, when of course it gets quite busy setting up the MCP, FMC etc. When dialing in the Nav freq, I had a NGX.DLL crash, and that was the conclusion of that flight.That is my first CTD, after 100+ hours of flying this bird. Be interesting to see who else sets there own Paging file. I am going to set it back to windows managed, and do the same flight and see how it goes. Edit: Wonder how the Beta testers set up there paging file ? if they all had the same, ie windows managed or user managed ?

I`ve set a Custom size since the advent of FSX SP1 when I first spotted OOM errors regularly. Since setting it I haven`t had a single OOM since except when I wipe the drive and forget or don`t quite get around to that step. I use 4 gig RAM and Windows advises me in the PageFile settings window to set mine at 4605MB which strangely is above what you set, I get no problems doing this and have done it this same way a long time now. Steve

I`ve set a Custom size since the advent of FSX SP1 when I first spotted OOM errors regularly. Since setting it I haven`t had a single OOM since except when I wipe the drive and forget or don`t quite get around to that step. I use 4 gig RAM and Windows advises me in the PageFile settings window to set mine at 4605MB which strangely is above what you set, I get no problems doing this and have done it this same way a long time now. Steve

If I may quote Nick below, this is the info I used when setting up my page file, he uses 3072 as a figure, (ignore 3172 above, typo), sure does not seem enough does it ? <quote>Processor Scheduling... MOVE the bullet from PROGRAMS to BACKGROUND.. then, Move the bullet from BACKGROUND back to PROGRAMS and click OK. I know it sounds strange, like you didn't do anything, but there is a reason for thatClick Virtual Memory Set a MANUAL size page file on the Windows7 partition to 3072-3072, click SET, OK and APPLY (if applicable) do not reboot at this time, cancel any reboot requestNOTE: I DOES NOT MATTER if you have 2, 4, 6 or 8GB of memory, UNLESS your system is also a dedicated A/V, graphics production or engineering application tower, a 3072-3072 page file is MORE than enough.If your system is used for high memory demand applications like I listed above, the page file size is based on how much you overrun your physical memory. IT IS FAR better to add more memory then use a larger page file.HOME/GAME/FSX systems with 2GB or more will NEVER use a page file of 3072 or greaterIf you have LESS than 2GB of physical memory, set the feature to SYSTEM MANAGED<quote>

To be honest I think thats purely a sample figure to illustrate how to set it, as in put the same figure in both boxes. If you look carefully near the bottom of the virtual memory setting page window theirs a figure advised by the Windows OS as the maximum to use. Best bet is to use this figure, for me its 4605 and I`ve used that figure about 6 years now maybe, had no OOM and no problems on several machines. Steve

Yes ZK-SUH, a page-file of 3072 is more than enough even in a 32-bit environment. You're running Win7 64-bit; FSX is 32-bit and will run a max of 4GB in that environment. Virtual Memory doesn't equate to the size of the Page File. Making it larger is just going to waste hard drive space. Your NGX.dll crash could be due to the NGX itself or your settings within FSX. NGX is a heavy addon, particularly when used with heavy scenery addons. And yes, even on the best systems you have to make compromises to prevent .dll errors (unless it's a fundamental flaw) and certainly for OOM's. Don't waste time and effort messing with the Page File. Chris

Thanks for your help. memory management is not something I delve into much. Have learnt some of it today though. Cheers

I must agree with Cris though, the NGX.dll crash is most likely attributable to something else. The raising, on a Custom value, of the Virtual Memory will fix OOM issues but that kind of crash is not a part of it. Steve

I heard a general rule a while back saying that it should be set to 1.5x your RAM amount.

Thats right, I heard the same. But whatever you do don`t exceed the max advised by Windows in the Virtual Memory page. If you have any doubt about it go back there later and change it back to a different value or reallow Windows to manage/mismanage it. Steve

Thanks for all your help everyone. In the dialouge box where you set the amount, it say's max @ 12GB. Which is what Di said it would be :) Have taken Chris's advice and set it at 3072. Steve, In regards to the NGX.dll, I found in the dll.xml, the wilco airbus entry had incorrect format, so removed it (don't think will be flying that again ) and repeated the crashed flight without problems. It may have been the cause, time will tell :) Thanks again.