Hello everyone,

 

I have been thoroughly enjoying the 747 NGX for the past week or so, but just this evening on a flight between Aldergrove and Tarbes-Lourdes-Pyrénées airport I started to experience a hitherto unobserved panel freeze. I was at FL330 and noticed that my FMC was suggesting an optimal cruising altitude of FL350. I requested a 2000ft altitude increase from the FSX ATC, dialed FL350 into the MCP and hit ALT INV. FSX promptly froze. I had saved the flight shortly after the T/C, so I reloaded it and repeated this process, requesting the altitude increase, dialing it in and hitting ALT INV. Again, FSX froze. And again, a third time. I have had no other problems up until this point and I was hoping that someone might be able to suggest what the problem is.

 

I have spent a bit of time trawling Google for an answer to this, but I can't seem to hit upon a search string that works. There's a lot of background noise in the search results. With a bit of luck we can get this sorted. I've tried to provide you with as much information as possible and hopefully I haven't forgotten anything obvious. I've also attached a DxDiag dump.

 

Further information:

 

Error message produced: none.

 

FSX Version: Acceleration: 10.0.6029.1000

PMDG 737-800/900NGX Version: 1.00.3118

Additional AddOns: GEX Europe 2.0, ActiveSky with REX Essential textures, AS MyTraffic, latest version of FSUIPC, EZCA.

 

What it's definitely not: the UIAutomationCore.dll freeze, as I fix this as a matter of course for every FSX installation.

 

My PC: Intel Core i7-2700K @ 4.7GHz, 8GB RAM, 2x nVidia GTX590 3GB (with SLi disabled for reasons of stability), and FSX is installed to C:/FSX on a Corsair 256GB SSD. Windows 7 64 Home. Every piece of software on my rig is paid for and licensed.

 

Event viewer dump for last freeze:

 

The program fsx.exe version 10.0.61637.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.

Process ID: 13a0

Start Time: 01cdc28c5d17e125

Termination Time: 160

Application Path: C:\FSX\fsx.exe

Report Id:

 

Action center dump for last freeze:

 

Description

A problem caused this program to stop interacting with Windows.

Faulting Application Path: C:\FSX\fsx.exe

 

Problem signature

Problem Event Name: AppHangB1

Application Name: fsx.exe

Application Version: 10.0.61637.0

Application Timestamp: 46fadb14

Hang Signature: c350

Hang Type: 2048

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 2057

Additional Hang Signature 1: c3503c7a5592e0eaff7b54b60875d07e

Additional Hang Signature 2: c30e

Additional Hang Signature 3: c30ee3c215854006b30d54121234b9b3

Additional Hang Signature 4: c350

Additional Hang Signature 5: c3503c7a5592e0eaff7b54b60875d07e

Additional Hang Signature 6: c30e

Additional Hang Signature 7: c30ee3c215854006b30d54121234b9b3

 

Pádraig Donnelly (just in case I didn't add my signature correctly)

It's not a pmdg module for sure,

It could be the flight-plan you loaded has become corrupt.

Try creating a new flightplan from new and retry this.

Submit a ticket, http://support.precisionmanuals.com/Main/Default.aspx, i'm sure the aircraft re-installation will fix the problem.

Thank you for your responses.

 

Jude, I created a new flight plan and loaded it up (after re-loading the save), but the problem persists.

 

ctdesing, I tried a re-installation there this evening but the problem persists. I'll take your advice and submit a ticket.