I see it from another perspective:FSX was coded for FSX. Not for FSX+ORBX+REX+GEX+UTX+NGX+FT+FSDT+XXXXXXX... And ORBX was made for FSX. And at it's default settings, it's not crashing, now is it?It is our choice to run as we like, and it should be our expectation that it crashes if we don't understand what's under the hood.In the end, lowering to default 4.5 LOD is going to relieve you of any problems. But you/we can't live with it... it's our problem. Not FSX old poorly written code. The code is alright for the time when it's been written.

Well they shouldn't have allowed custom edits if that's the case... But I do see your point.

happened again off the coast of jfk the concorde x must have a memory leak :@ :( any suggestions im going to do a reinstall when time permits and just keep my scenery on my other drive i use for all my other games and keep my hardrive dedicated to fsx with just plane addons and small airport scenery packages im so annoyed with this already had the plane 2 days and twice ive wasted 3hours then just as im about 50nm out i get the damn virtual memory has ran out.i have downloaded that process explorer but not sure what you guys wanting me to do with it so need instructions although im not going to do another flight and waste another 3 hours just to see whats happening.im so frustrated now i done about 1hr 30mins in around heathrow with everything on genx etc and not a bit of bother was around 20fps above 2000ft then bang vm error just as im about to turn into jfki will try upping the pagefile to 16gb but i dont think this is the culprit in this case i think its more a hardrive space issue or the concorde anyone wanna help me out ?cheersHayden

im so frustrated now i done about 1hr 30mins in around heathrow with everything on genx etc and not a bit of bother was around 20fps above 2000ft then bang vm error just as im about to turn into jfk

If you are not read for hour long tests, then best leave it.FSX is like that, and it will always be.Is Concorde X only addon you have installed? No other scenery, nothing?PE is going to show you if and when your VAS is growing so you can possibly detect a problem. I just spent 5 days testing a 9,5hrs flight form EGLL to KSEA, why it crashed just before the end. At first it wasn't VAS... it was a faulty installation, and then it was VAS, which I narrowed down to the forgotten skidmark effect file, which is a know problem: delete/rename to .bak the fx_skidmark.fx file from effects folder. But I don't think that's your problem.

Soooo... just to add some fuel to the "no pagefile" thought... The logic sounds good, and Win7 seems to run just fine without it, so I ran without a pagefile from the time of my last post until this morning. Late last night I thought I should do a defrag on C: drive as well.. So - closed everything, ran Ken Salter's 'Alacrity' to shut down all extraneous services, disabled the internet, etc., and then started up Ultimate Defrag. Normally the 200 GB C: drive takes three hours or so.... Well - it's now 09:15 in the morning and UD is still churning away and the drive's not anywhere near finished.That's reason enough for me. It needs a pgefile, so I've just recreated it.

update: took my cfg file out incase it was corrupt or what not and replaced it with my backup my frames have jumped back up to 25fps -30fps on my frame limiter and i have managed to bump up the settings with no effect on frames what so ever. my fsx also isnt getting as many lock ups and freezes im going to uninstall concorde x and reinstall from scratch just incase the civa ins didnt install properly etc.and yeah i will stick with it till we finda a solution/fix its just time consuming to say the least when time is of the essence :(i will need instructions how to use that process explorer as i cant find out where the settings are that you want me to change to monitor the VM.and i currently have lots of addons pmdg rex genx manhattan x concorde x and i have enb series.thanksHayden

Soooo... just to add some fuel to the "no pagefile" thought... The logic sounds good, and Win7 seems to run just fine without it, so I ran without a pagefile from the time of my last post until this morning. Late last night I thought I should do a defrag on C: drive as well.. So - closed everything, ran Ken Salter's 'Alacrity' to shut down all extraneous services, disabled the internet, etc., and then started up Ultimate Defrag. Normally the 200 GB C: drive takes three hours or so.... Well - it's now 09:15 in the morning and UD is still churning away and the drive's not anywhere near finished.That's reason enough for me. It needs a pgefile, so I've just recreated it.

My O&O is working great, I am not using Ultimade Defrag though. I usually leave it overnight, last defrag of the FSX drive, which was 55% fragmented after new installation was done 8hrs later. I didn't look how long it took.

i  will need instructions how to use that process explorer as i cant find out where the settings are that you want me to change to monitor the VM.

With all respect, what instructions do you need? Open PE, View, Select Columns, Process Memory, check Virtual Size. Uncheck everything else in Process Memory only if you want clearer view.I guess you needed it laid out for you.

ok think ive done that i take it virtual memory is the memory commit ? done a flight to edinburgh last nite from heathrow didnt have any hiccups think maybe it was my .cfg file that was causing it ?sorry for being a noob with that process explorer btwcheershayden

ok think ive done that i take it virtual memory is the memory commit ? done a flight to edinburgh last nite from heathrow didnt have any hiccups think maybe it was my .cfg file that was causing it ?sorry for being a noob with that process explorer btwcheershayden

Possibly. A column called Virtual Size, not commit or anything is what you want to know. Virtual Size.That one should not show more than 3GB, or maybe if you push things 3.5GB.

Hey all after some testing tonight it's definetley a memory leak at KJFK same symptoms on approach gauges freezing and my ground textures going all fuzzy then on touchdown i got the error system has ran out of VM .....i managed to get some pictures this time but my system seems in my opinion to have plenty of poke left considering all i have is manhattan x this is all.started to go funny 20nm out from KJFK runway 13Li will post some pics i took here see if any of you can help me.thanks for helping.

The pics you posted are way too small. You need to post bigger pictures.

68 processes is a huge number to be running.

Will enlarge them just now then

There.and 68 proccesses is not much i usually have more than that without any problems in any of my games.cheersHayden

FSX is not your normal game.

More than 10 of the processes are for fsx as soon as this is closed then im back down to 58 again.i think its more of a conflict than a hardware issue IMHO as it's only at KJFK this problem happens.i will try cut down more proccesses but i dont think it's the culprit here as i'm only using at max 5.5 to 5.6gb ram and 2.5gb of the 10gb + pagefile this is really starting to put me off this simulator again as i cant get on vatsim till this is fixed