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.

End flight results in CTD and PDMG737NGX.dll error

Featured Replies

Hi all

 

Apologies for posting this here if it should be in the CTD forum but it appears to be NGX specific.

I get a consistent error (as per the below) whenever I choose 'End Flight' within FSX. It works as expected with the 'vanilla' Microsoft planes, but errors when using the NGX. This wouldn't be an issue for me personally, however, I use add-ons that sometimes require a clean End Flight exit. I have also found that if you choose the NGX in Free Flight menu, and then go to settings, then try to click Free Flight again, I receive the same DLL error message.
I have tried all of the supposed fixes I can find on forums such as running as administrator, importing the UIAutomation.dll (from Vista 32) but have had no joy.
I have today, completely re-installed Windows 7 Home Premium 64-bit, and then only installed DirectX, .NET 4, FSX, FSX SP1, FSX SP2, and then the NGX. I refrained from installing any further add-ons as I suspected they may cause issues. However, prior to installing the NGX, I could 'End Flight' and return to the menu screen. If you have anything that may assist, then I'd be very grateful. Equally, if you require any further information, I'd be happy to supply it.

 

(I also have the full APPCRASH data, but don't want to post it here as it's long, and I can't find a 'spoiler' option)

Cheers

Andy

 

 

---------------

 

EventType=APPCRASH
EventTime=130112178577591967
ReportType=2
Consent=1
ReportIdentifier=86b8eadf-ac49-11e2-b360-0025116553d4
IntegratorReportIdentifier=86b8eade-ac49-11e2-b360-0025116553d4
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.61472.0
Sig[2].Name=Application Timestamp
Sig[2].Value=475e17d3
Sig[3].Name=Fault Module Name
Sig[3].Value=PMDG_737NGX.DLL
Sig[4].Name=Fault Module Version
Sig[4].Value=1.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4f5162a3
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0023abe6

  • Author

scandinavian13 Many thanks for your reply. After going through the untried ideas in the link above it appears FSUIPC sorts the problem out. I remember getting it ages ago, but obviously never updated it. (Mainly because I didn't understand the importance of it until today).

It seems to have solved my problem, and I can only hope others see this, as I've been googling etc for months, but putting up with it. There's a lot of 'flakey' fixes knocking about, and I apologise to all if this has been raised umpteen times before.

 

Thanks again scandinavian13

 

Cheers

 

Andy

 

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.