FSX PMDG 737 Crashing to desktop

[dk140]

Hello,  i am new to this and have had pmdg 737 for a few months now but i am getting increasing crashes to desktop and i cannot figure out why.  It has happened both before take off and also during the flight which is obviously frustrating and spoiling game experience.

The error i keep getting from the event viewer is:

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: PMDG_737NGX.dll, version: 1.0.0.0, time stamp: 0x59b7107d
Exception code: 0xc0000409
Fault offset: 0x001e4ad8
Faulting process ID: 0x500
Faulting application start time: 0x01d437c8c1ed74d4
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\FSX\gauges\PMDG_737NGX.dll
Report ID: 99cbb73b-eb8c-4051-9e84-d25b6e45d82d
Faulting package full name: 
Faulting package-relative application ID: 

 

If anyone could help i would be very grateful.

 

Many thanks

[downscc]

Hi, welcome to the PMDG forum, please note their rules require us to include our full names on all posts.

Be assured that the NGX is a mature product, been out for years and has lots of users so it is unlikely that there is a bug in the dll module cause the crash.  More likely, the problem is occurring and the dll module is caught at the time of the stack buffer overflow (you exception code points to this).

It is frustrating, but you will have to start troubleshooting in a methodical manner.   Eliminate possibilities.  The AVSIM CTD guide is a good place to start:

 

[dk140]

many thanks i will try this now.

Daniel Kerry

[dk140]

OK so i have been trying to work out why i keep getting ctd everytime i use fsx pmdg 737.  As suggested i started to go through the ctd guide and i renamed my fsx.cfg and initially this seemed to work for about 4 flights and now im getting same problem.  I have been using the appcrashview program and keep getting two specific errors. 1. Access violation under exception code description and 2. The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

Does anyone know what these mean or what to try next?

For your information most ctd occur only when i am entering data ie. legs into the pmdg 737 fmc i getting the circle and then totally crashes and doesnt come back at all.  The other times it can crash is when im configuring my joystick for some reason.

 

If anyone can help me further with this i would be very gratefully as i feel i cannot even use the pmdg 737 on fsx at all at the moment and i am spending lots of time and don't really seem to be getting anywhere with this frustrating issue.

Thanks

 

Dan Kerry

 

[Jim Young]

Means bad system driver - run a driver update program like Driver Booster to see if this fixes the problem

Means system has a bad overclock - lower the overclocking or, if you have the option, go to the Optimal Defaults.

Means FSX settings are set too high (reason why you were able to do four flights without a crash).  Did you reenter a "tweak"?  Tweaks are not good.  Need to lower settings in FSX and in your display driver settings.

FSX is an old program and very sensitive to high settings as it was never updated to handle the future tech.  The recommendations above to fix this problem are probably not your favorite recommendations but you are simply testing to see if this fixes the problem.  If it does, then you know what it was and work around it accordingly (i.e., bad overclock, high settings). 

When you are configuring your joystick within FSX, you are using more resources while do the calibrations.  If your settings are too high, you are simply placing too many resources on your system and you need to let your computer "breathe again".  FSX was developed for systems built in 2007.  Back then, we barely could get 15 fps and were happy if we got over 25.  Now, computers and graphic cards are better and everyone thinks they can go to the max when the application is not capable of going to the max settings.  Of course you can use max settings but you will begin seeing anomalies and crashes. 

[dk140]

ok will try these things many thanks Jim

Dan Kerry

[dk140]

ok so tried the above suggestions and again worked fine for a handful of flights but when entering data into fmc i just got same crash again.  Really not sure what else to try but this is so annoying.

If anyone has any other suggestions its still the same error as above.

Many thanks

Daniel Kerry