Hi,

 

I'm hoping for some advise on a rather strange OOM issue I am experiencing and that really has me scratching my head.

 

On my maiden flight with the PMDG 777 I flew a leg from EDDL(Aerosoft) to OMDB(FlyTampa). On approach to OMDB I got the first OOM error in a long time, and certainly the first on my new rig (4770k, 680GTX, 8GB 2400MHz Ram, Win 7 Pro x64, build in June/July).That really surprised me as I have my system set up very carefully to avoid such issues. Reading the PMDG recommendations to avoid OOMs taught me nothing I wasn't doing already for a long while (thanks Word Not Allowed!).

 

I have since reduced settings even further and repeated the exact same flight 3 times. Same result every time! OOM on approach :-(

 

Now before you jump to the usual conclusions (i.e. your fault, you are running too much at once etc.) let me assure you that my settings are sane, balanced and well tested. I run 1024 DXT clouds, LOD radius at 4.5, medium auto gen., max texture load at 2048, water at 2-low, high mem fix, all sceneries disabled except the 2 mentioned above.

 

Now here is the really curious thing: On my last 2 flights I measured VAS with MS process explorer. In both cases the "virtual size" (see screen shots) did not go above 3.1 and 3.3 Gigs respectively! In fact at the moment the OOM occured on the 2nd to last flight I was only using 2.7 GB. Correct me if I'm wrong here but I think I should have ample head room. Why is this still occurring?

 

I have posted my experiences over in the PMDG forum but got no answers and eventually the thread was closed. I'd like to add that I have put many many hours onto the NGX, also often flying to OMDB without issue.

 

Any ideas/explanations/tips would be greatly appreciated!

 

 

I've had the same problem for ages, I get an OOM when the FSX process registers 3 GB in Task Manager (I am running Win7 x64 on 8 GB RAM btw). I can only presume the other gigabyte must be graphics memory?

How big is your video card memory?

ATI HD6870 1 GB...

 

 

let me assure you that my settings are sane, balanced and well tested. I run 1024 DXT clouds, LOD radius at 4.5, medium auto gen., max texture load at 2048, water at 2-low, high mem fix, all sceneries disabled except the 2 mentioned above

 

Do you have microsoft patch applied too? http://support.microsoft.com/kb/947246

If that happens arround 3GB, you need this to increase limit to maximum of exactly 4GB

 

Also leave paging at default settings, it's very important in windows 7 / 64bit.

 

I'm not saying that is something with your FSX settings becouse i came close to OOM on my last 3 flights with 777 on approach, and i didn't saw OOM for at least 2 years before this plane...and it happens only with this plane. The funny thing is that i have all recommendations from PMDG manuals applied allready, except water settings. I tried last night with low water settings, but there is no big difference in VAS usage unless i set water slider to minimum - which looks worse then FS9 water BTW

I like PMDG but I find it a little disapointing that they've closed down this thread. I am also having OOM on the first gen i7, 8gigs of RAM, GF470. Only in this bird - The T7 performs a lot better for me than the NGX overall and I love it, but as of yet, I wasn't able to complete a single flight in it, gate to gate.

I would be interested in knowing the faulting module if one showed up in your crash report.  I had the ntdll.dll faulting module for every crash I had.  Crashes with the ntdll.dll as the cause are usually related to memory or high settings (FSX or a bad OC).  I could duplicate the crash 100% of the time in a flight from Wash Dulles to Charlotte NC.  Like you I have my FSX settings set close to the default and still got the crashes.  My only tweaks were setting the LOD_Radius to 6.5 and Texture_Max_Load to 2048.  No other tweaks employed (like Bufferpools which causes more problems than enhancing the fsx experience).  I lowered the LOD_Radius and tried again.  Still got the crash.  Then I decided to check my dll.xml for any corruption.  I had several entries for software I had uninstalled some time ago.  I had a couple of entries leading to the FSX SDK which I had not installed yet and, there were two entries for the PMDG.  Both were exactly the same.  So, I opened up Notebook++ (Google) and edited the dll.xml and removed the old entries and one of the PMDG entries.  I ran the same flight again (with LOD_Radius, etc., back up to my tweaks) and this time I was able to takeoff and land at Charlotte.  No CTD.  Of course I will be doing some further testing to see if the problem is fixed permanently but the CTD I could replicate 100% of the time is no longer happening.

 

Best regards,

Jim

 

 

Of course I will be doing some further testing to see if the problem is fixed permanently but the CTD I could replicate 100% of the time is no longer happening.
 
Best regards,
Jim

 

Jim, does the T7 run in P3D do you know?

Jim, does the T7 run in P3D do you know?

 

 

No

I've had the same problem for ages, I get an OOM when the FSX process registers 3 GB in Task Manager (I am running Win7 x64 on 8 GB RAM btw). I can only presume the other gigabyte must be graphics memory?

 

Well, for starters, Task Manager doesn't tell you VAS.  You need a program such as Process Explorer to read VAS.

ATI HD6870 1 GB...

 

Hmmm it may be one of those rogue scenery OOM's.  GPU ram usually affects OOM's but only noticeable when the user has a monster 2GB or 4GB card.  

Hmmm it may be one of those rogue scenery OOM's.  GPU ram usually affects OOM's but only noticeable when the user has a monster 2GB or 4GB card.  

 

Can you explain this or provide a link? I'm not saying that is not true, but i never heard about and i have 2GB card. Just curious 

I'd have to dig long and hard to find it. Standby

For what its worth, you can definitely get well above 3GB VAS in FSX.  I just completed KJFK-CYVR (both with FDST sceneries) in the PMDG 777 and with process monitor running I landed with just over 3.7GB VAS used.  Not a lot of room left but no problems.

Can you explain this or provide a link? I'm not saying that is not true, but i never heard about and i have 2GB card. Just curious 

 

And the Titan has 6Gb of very very fast memory. Why would a video card use slower main memory when it has enough of its own? I always thought it was the other way round, the less on board video memory the more it needed to shadow parts of its data in main memory. And also surely that's not in the FSX process memory at all. There's no need for it to be in a specific process memory. After all, in Windowed mode (for example) lots of processes are using the video. Makes no sense.

 

Regards

Pete