If you have LESS than 2GB of physical memory, set the feature to SYSTEM MANAGED"

 

I have found that system managed size solves a lot of problems for many and it has worked for me. When I tried to set my own page file (I have 8 GB's), I started getting CTD's so moved back to system managed size and the CTD's went away. I did some research and found that Microsoft Windows 7 does a better job than in past os's in managing memory. So, if you ever get a crash with your own page file settings, goto system managed size and see if that fixes things. Thanks again Bill for your input and research. All the help we can get here to fix CTD's is most welcomed.

 

Best regards,

Jim

..and the answer to PF fragmentation is to custom set it at (e.g.) a coupla times your physical memory but stipulating the Initial size to be the same as the Maximum size; i.e. 16392 in both squares. This way it stays in the same place, and never gets fragmented - you can check this (generally) with you defrag s/w.

 

My personal preference - 100 MB on C: done the same way, with 1.5 x my 8 gig ram = 12294 on the separate E:, as that doesn't impact the OS's drive I/O and is almost impervious to fragmentation - and 1.5 x 8 gig is plenty big enough. No OOMs' or VAS ctd's.

Jim,

 

You are correct, it is probably system specific.....I will continue with a fixed until otherwise.

 

Currently, I have a version of FSUIPC4 that gives an audible warning (background chime) when you are approaching the OOM limits. I get this on every flight at the end of making a landing. So far, I haven't had a crash or lockup due to an OOM.

 

Bill Clark

System Managed is the best choice on a SSD, since there is no fragmentation. Fixed is best on a hard disk drive.

 

Dave

The experts say OOM's for 64 bit systems are extremely rare

I assume it is because I am simply trying to run multiple detailed addons at very high detail levels.

 

That is the case, Christopher, but I think you should moderate your language somewhat don't you? Some of those "experts" are ordinary guys who are long-term simmers - maybe not pro IT guys - but they are helping others diagnose and more often than not - fix those problems. And they do it day after day after day. They may not always be technically correct, but what happens is - it does bring out pro guys - who do know what they're talking about - and the correction is posted without insulting the other guys. We certainly don't need "jack ######" here, thank you.

 

Old retired IT guy.

I have a version of FSUIPC4 that gives an audible warning (background chime) when you are approaching the OOM limits.

 

I can say with almost 100% accuracy that it's not a problem with the FSUIPC.dll. Have you checked the FSUIPC4.log in the Modules folder?

System Managed is the best choice on a SSD, since there is no fragmentation. Fixed is best on a hard disk drive.

 

Thanks Dave for that info. It might be the reason 'system managed size' works best for me as I have an SSD. I still say though that people with HHD's should use 'system managed size' as FSX is an old program AND Windows 7 manages memory than any OS in the past.

 

Christopher Low: Have you ever Googled 'out of memory Windows 7 64 bit'? Here's one link - http://forum.avsim.net/topic/321527-out-of-memory-windows-7-64-bit/. It doesn't mean they don't happen in 64 bit systems, they are just very rare and I know you have had your fair share.

 

Best regards,

Jim

also here, and Mark Russinovich is an expert.

I can say with almost 100% accuracy that it's not a problem with the FSUIPC.dll. Have you checked the FSUIPC4.log in the Modules folder?

Jim, you may have mis understood Bill, he was referring to the OOM warning that Pete Dowson coded in FSUIPC recently to warn users that the VAS was about to become exhausted, so to give the user the chance to save the flight or refresh the scenery etc. Bill was not implying an error with FSUIPC.

 

regards

I'm now getting really rather odd results.... Not had any OOMs since I toned down a few settings however I for some reason seem to have a massive performance reduction that doesn't seem affected by...well...anything! Most I seem able to attain most of the time is around 16FPS - I was getting over 25 when in clear blue sky over not-too-detailed scenery with my old un-upgraded system. I now have gone from a 4 core Phenom 2 to a I7 2700K overclocked to 4.5Ghz and now I'm getting these low FPS.....

 

I've tried with scenery turned down..... no effect - Turned the traffic slider to 0% - still much of the same. I run FSX using the external batch file limiter as I was getting over 40FPS but now all of a sudden its gone all wonky!

 

For example most recent flight again in the F1 mustang - Out of Mahon airport off to Rome - Barely got over 17FPS on that flight and that was over the water!

 

More than adequate GFX card (I mean it was giving better performance before!)

 

Anyone have any troubleshooting ideas?

 

James

anyways ive since changed the fsx.cfg to the usepools=0 and things actually seem alot better - plus i reduced the cloud resolution in rex which for some reson i had set at 4096......

 

Was this (post #11) when using the 2600K or the Phenom, James? - and what is your GPU?

That is the case, Christopher, but I think you should moderate your language somewhat don't you?

 

I rarely use language of that sort on internet forums, but I apologise if it caused offence. It's just that to suggest that OOM errors are extremely rare on 64bit systems is not exactly accurate. It certainly would be if we were all flying the default 737 in and out of default airports with mid range scenery settings, but I'm betting that most of us didn't purchase powerful Core i5 2500k or i7 2600k PCs to run FSX at its most basic level. Since I have experienced numerous OOM errors during my UK Tour in the Flight1 Cessna Citation Mustang, you can probably appreciate that this is something rather close to my heart.

[/font][/color]

 

Was this (post #11) when using the 2600K or the Phenom, James? - and what is your GPU?

 

Hi Paul,

 

After I installed the 2700K - I did use BP=0 with the old processor too.

 

GFX is the ATI Radeon 6970

Christopher,

 

I deleted your post where you used bad language to express a terrible attitude. Notwithstanding your above post justifying the tone of your ugly response, you owe these people a real apology. I am very surprised to see this kind of thing coming from you.

 

Kind regards,

Hmmmm.... Ye e e e e es...... I think he should send each of us who subscribe here a PMDG Gift Voucher for about $60.....

 

:LMAO:

 

It really beginning to sound like it's not an issue with the flight sim, James.

 

How did you do the migration of the OS and the flight sim over to the new mobo and proc? Would you post your cfg here, too, please?

Hi Paul,

 

When I moved to the new Mobo and OS I did a complete re-install of everything from the ground up - re-installed FSX manually and re-installed each addon individually. Nothing was 'copied' from the old install.

 

I'll grab the CFG later on - at work at the moment so don't have access to the home PC.

 

James

 

Out of interest - With a system of my spec what kinda FPS should I generally be recieving - I see loads of people getting way over 30 most of the time

 

Win7 Pro 64Bit

16GB 1600mhz RAM

Radeon 6790 1GB GFX

750W Power supply

Intel I7 2700K Overclocked to 4.5GHZ (hyperthreading on)

Asus P8Z68 Deluze Gen3

128GB SSD as primary OS and FSX drive

1TB Second HDD files/page file/other