On Windows 7 64 bit I have FSX Deluxe with SP2 applied, I have no addons or scenery packs installed, its all clean except for the UIAutomationcore.dll fix. I've been running FSX without issues for a year or so and decided to finally pick up the 737 NGX from PMDG's website. It installed fine, looks awesome, and I have no issues with performance or anything (I went through the docs and used all their recommended settings). My system is a 2.2Ghz i7 2670QM, 8gigs of ram, video is an NVIDIA GTX 580M with 2gigs of VRAM. NVIDIA driver version is 296.1 (The latest beta drivers do not help the issue).

 

The problem: Whenever I crash the plane, FSX will display the normal green bar with red text saying "crash" as normal, but when it tries to reload the environment it will crash to the desktop! This happens 100% of the time. I can load FSX, choose the 737NGX, put in in the air, lose control (easy for me LOL), soon it slams into the ground the the crash happens. In the windows event viewer, I see the following:

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: PMDG_737NGX.DLL, version: 1.0.0.0, time stamp: 0x4f5162a3

Exception code: 0xc0000005

Fault offset: 0x0023abe6

Faulting process id: 0x1c84

Faulting application start time: 0x01cd7b157487a069

Faulting application path: C:\FSX\fsx.exe

Faulting module path: C:\FSX\GAUGES\PMDG_737NGX.DLL

Report Id: 821ad32a-e717-11e1-b385-9cb70d011a12

 

Note: I just purchased this plane two days ago, so the version I am using is the one I downloaded 2 days ago from the link PMDG sends you.

 

Any solutions or ideas?

 

Thanks!

 

PS: I seen another post where people get this error when exiting FSX. I just ran FSX, loaded the 737NGX, and exited with no crash. I have not tried flying without crashing the plane, I will try that, but that isn't a resolution for a beginner pilot :)

I had this problem. I was trying to find my old support ticket about this. But from memory it is t do with your saved default flight. I found that loading a different aircraft up, then reloading the PMDG helped fix this problem.

 

I will try an find that support ticket. Better still open a PMDG ticket up because I think they know what this problem is.

I had this problem. I was trying to find my old support ticket about this. But from memory it is t do with your saved default flight. I found that loading a different aircraft up, then reloading the PMDG helped fix this problem.

 

I will try an find that support ticket. Better still open a PMDG ticket up because I think they know what this problem is.

 

I just submitted a ticket now. If you find your ticket, please let me know what the resolution was so I can try it without waiting a day or two :)

On Windows 7 64 bit I have FSX Deluxe with SP2 applied, I have no addons or scenery packs installed, its all clean except for the UIAutomationcore.dll fix. I've been running FSX without issues for a year or so and decided to finally pick up the 737 NGX from PMDG's website. It installed fine, looks awesome, and I have no issues with performance or anything (I went through the docs and used all their recommended settings). My system is a 2.2Ghz i7 2670QM, 8gigs of ram, video is an NVIDIA GTX 580M with 2gigs of VRAM. NVIDIA driver version is 296.1 (The latest beta drivers do not help the issue).

 

The problem: Whenever I crash the plane, FSX will display the normal green bar with red text saying "crash" as normal, but when it tries to reload the environment it will crash to the desktop! This happens 100% of the time. I can load FSX, choose the 737NGX, put in in the air, lose control (easy for me LOL), soon it slams into the ground the the crash happens. In the windows event viewer, I see the following:

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: PMDG_737NGX.DLL, version: 1.0.0.0, time stamp: 0x4f5162a3

Exception code: 0xc0000005

Fault offset: 0x0023abe6

Faulting process id: 0x1c84

Faulting application start time: 0x01cd7b157487a069

Faulting application path: C:\FSX\fsx.exe

Faulting module path: C:\FSX\GAUGES\PMDG_737NGX.DLL

Report Id: 821ad32a-e717-11e1-b385-9cb70d011a12

 

Note: I just purchased this plane two days ago, so the version I am using is the one I downloaded 2 days ago from the link PMDG sends you.

 

Any solutions or ideas?

 

Thanks!

 

PS: I seen another post where people get this error when exiting FSX. I just ran FSX, loaded the 737NGX, and exited with no crash. I have not tried flying without crashing the plane, I will try that, but that isn't a resolution for a beginner pilot :)

Would be interested in a solution as well. Could you please post the solution to this issue when you get a response from PMDG.

Regards

Andrew

Sure, I will do that for you

Sure, I will do that for you

Thanks mate!

I just did another test. I took the NGX up for about an hour long flight, then I landed at an airport without crashing. Pretty much ran the plane through all its motions, used the AP, used ground services, cold start, complete shutdown, etc. I also went to the menu A LOT of times, pulled up the map, etc. When I exit it does NOT crash.

 

So basically this crash only happens when the plane itself crashes as stated above.

 

I'll wait for a reply from my ticket

I found ENBSERIES hack would cause my PMDG to crash a lot. As soon as I uninstalled ENBSERIES it was much better and haven't had a crash in months.

I don't even know what ENBSERIES hack is, so that isn't my cause :)

I will try and find the ticket, it is worth waiting for pmdg reply, because the problem can come back.

But it's is worth knowing that it can be fixed.

I tend to disable the crash option in fsx as it is not only unrealistic but a pain in the arse. I was sick of airport vehicles driving into me and causing a crash. And my wing would trigger a crash even though I had carefully taxied around and object and given it enough room. Completly hopeless all round I think.

 

Do yourself a favour and knock it off.

I tend to disable the crash option in fsx as it is not only unrealistic but a pain in the arse. I was sick of airport vehicles driving into me and causing a crash. And my wing would trigger a crash even though I had carefully taxied around and object and given it enough room. Completly hopeless all round I think.

 

Do yourself a favour and knock it off.

 

Yep same for me, I had a long flight ruined years ago after some stupidly/incorrectly placed airport object FSX detected I touched, since then I have it off.

autosave and passenger x always came up on my crash report. No problems after uninstalling. able/disable add ons one at a time could help

I tend to disable the crash option in fsx as it is not only unrealistic but a pain in the arse. I was sick of airport vehicles driving into me and causing a crash. And my wing would trigger a crash even though I had carefully taxied around and object and given it enough room. Completly hopeless all round I think.

 

Do yourself a favour and knock it off.

 

I do not have aircraft to aircraft collisions on and vehicles hitting the plane does not cause the problem for me. I'd like the solution without disabling anything since that is the way it ran without the NGX in the first place. It may be annoying and unrealistic, but it forces me to be on my toes LOL.

 

autosave and passenger x always came up on my crash report. No problems after uninstalling. able/disable add ons one at a time could help

 

As I stated, I do not have ANY addons.

I can't check the following assumption in the NGX docs, since I'm in the process of installing a new OS so haven't even got my flightsim PC going again yet, let alone the NGX :Cry:. But I seem to recall that in the NGX introduction document, PMDG warn against loading another variant of the NGX when one is already currently loaded - or words to that effect. Wouldn't FSX, when recovering from the aircraft crash, be doing just that ? If that is the cause of your problem, the suggestion already made of turning crash detection off may well prevent a re-occurrence. It may also explain why the problem doesn't occur when you complete a flight without crashing the aircraft at the end ...