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

I'm running 52 processes with quite a lot of side-loaded things - Citrix online client (2 processes), Apple-Stuff (6 processes), Teamviewer (2 processes), Office (1 process), Nvidia (3 processes), Setpoint (1 process), Daemon Tools (1 process)Deduct these processes, and this is what you should basically have on a clean system. All the above are NON-ESSENTIAL for fsx. And this is how FSX should be run, I prefer without these, but I know they cause no problems, for the fact, because I can offload them easily and did enough tests.Do you know your processes this well, and where each one belongs?On the other note: I noticed your VAS is kicking in the 3.77GB area. WAY TOO MUCH. You need to lower whatever you're running. No way you have 3.77 with default settings.

normal 51 proccesses and with my game booster prcesses are 45 all other proccesses were just my firewall etc.Yeah most of them are sound drivers system proccesses and usb stuff and graphics drivers i turn off all the non essential proccesses with my gaming booster.Hope i can get to the bottom of this without a reinstall :(ThanksHayden

Word Not Allowed what you mean with default settings? As i have little to no addons in this area and my frames are rock solid up until i get the VM error at KJFK i dont have this problem at heathrow where i have literally every addon in the book and no problems there what so ever.

Just to do a comparison with EGLL mega airport gen X 1-4 rex 2.0 enb series concorde Xprocess explorer approach 15nm to runway not even going above 2.5gb yet. no where near the 3.77gb at KJFK with only manhattan x installed ?over EGLL 2.92gb process explorer.

Manhattan X is incredibly resource hungry in my opinion. Try taking a small GA out for a spin from say kphl or something and fly towards new york city. Observe the memory footprint after departing, then when you got manhattan in view, and then again when youre in the vicinity of KJFK

Word Not Allowed what you mean with default settings? As i have little to no addons in this area and my frames are rock solid up until i get the VM error at KJFK i dont have this problem at heathrow where i have literally every addon in the book and no problems there what so ever.

Well, apparently you are wanting to much (though very unusual). I don't have ConcordeX, but I can test NGX over at KJFK and ManhattanX.

i will try using my pmdg 747 when time permits then from pittsburgh to kjfk to see if its the concorde or not as this flight will only take about 45-1hr as its only 318nmalso done a flight from klax to pittsburgh last nite no faults what so ever ran like a dream.maybe the install of manhattan x is buggy or the demo of fsdreamteam i had is causing a conflict somewherealso checked my addons it looks like i have utx usa aswell.