Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Fatal error on Approach

Featured Replies

Ok, KATL to KTPA with AES OFF, this time I was able to land the 737-600, something that in two earlier tries could not, but as soon as I turned onto the taxiway, CTD with OOM message... both airports are PW ones...Is getting to where I cannot land this beautiful beast in PW airports, this never happened before SP1, and I mean clean no fixes install, I never had any problems before SP1...

Santos Cedeno

Dell Studio XPS 9100 Core i7 920 2.67GHZ 12GB DDR3 RAM 8GB USB RAM W7HP-x64 ATI Radeon HD 5700 1G FSX GOLD Acceleration SP2

PMDG NGX737-600, 700, 800, 900, SP1

  • Author

I've never had a problem flying from non AES to AES airports til SP1. If I had OOM the computer always said it was OOM. The FMC also dumped several of the waypoints and went into a continuos right turn!

i get this in the FTX oz scenery always happens about 25miles out on descent, fsx freezes up and wants to restart. im going to try it again with the ftx scenery turned off and see what happensi have no problems flying anywhere elseFaulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3Faulting module name: g3d.dll, version: 10.0.61472.0, time stamp: 0x475e180cException code: 0xc0000005Fault offset: 0x000b50dfFaulting process id: 0x10d0Faulting application start time: 0x01cca4d226dfd4b0Faulting application path: C:Microsoft Flight Simulator Xfsx.exeFaulting module path: C:Microsoft Flight Simulator Xg3d.dllReport Id: 57948697-10d6-11e1-92ad-001fbc0d7083

John C

I'm glad to see that I am not alone with the OOM crashes post SP1....

Santos Cedeno

Dell Studio XPS 9100 Core i7 920 2.67GHZ 12GB DDR3 RAM 8GB USB RAM W7HP-x64 ATI Radeon HD 5700 1G FSX GOLD Acceleration SP2

PMDG NGX737-600, 700, 800, 900, SP1

Can't really see why there would be though.. I don't seem to be usingany more memory than any other version, and after using the low resgauge textures, I seem to be using slightly less memory. I've tested thisby gradually increasing scenery density and noting when I crash.I seem to actually have more overhead now with SP1, than I did usingprevious versions with all high res textures..So.. If it's a fault with the NGX itself, seems I would notice it, being Iam running XP 32 bit, and should be one of the first to notice a problemif the memory load increased. Using the high res textures as before,I noticed no difference at all.So... I would have to guess either too much stuff is running in the background,or really dense scenery is cratering the box. Or a combo of both..

Mark Keith

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.