777 crashes FSX ?

[Manny 1,293]

Windows log system.

 

 

 

I use an app called AppCrashView

 

And its crashing in the same spot

 

The Even Viewr gives me this

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: g3d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58

Exception code: 0xc0000005

Fault offset: 0x00059a3f

Faulting process id: 0x1574

Faulting application start time: 0x01ceab4401ec9731

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

Faulting module path: F:\FSX\g3d.dll

Report Id: 34371591-173c-11e3-88f5-c86000be5f20

 

The previous crash

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: g3d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58

Exception code: 0xc0000005

Fault offset: 0x00059a3f

Faulting process id: 0x33f8

Faulting application start time: 0x01ceab42d035e7ae

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

Faulting module path: F:\FSX\g3d.dll

Report Id: 33c18ea7-1737-11e3-88f5-c86000be5f20

 

and the one before that

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: g3d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58

Exception code: 0xc0000005

Fault offset: 0x00059a3f

Faulting process id: 0x31e4

Faulting application start time: 0x01ceab3e65f496eb

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

Faulting module path: F:\FSX\g3d.dll

Report Id: fdf76a7c-1735-11e3-88f5-c86000be5f20

 

[3-2-1-Now 126]

 

 

Faulting module path: F:\FSX\g3d.dll

A scenery is causing this.

 

Look at the scenery you have in the area.

 

Best regards,

Robin.

[falcon999 24]

Do you follow suggestions in the introduction?

[Manny 1,293]

A scenery is causing this.

 

Look at the scenery you have in the area.

 

Best regards,

Robin.

 

 

Hi Robin,

 

You might be right.. I just moved the 777 to some other area..the p Princess Julaiana and I am yet to see this issue.

 

Hmm.. Interesting..if its a scenery Issue..I can debug it myself to eliminate the problem.

 

Edited to add: SPOKE TOO SOON.  Just got the same crash  

 

 

Do you follow suggestions in the introduction?

 

Which part? HE He!

[FlyCathay 18]

just got this myself:

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3
Faulting module name: PMDG_777X.DLL, version: 1.0.0.0, time stamp: 0x52256029
Exception code: 0xc0000005
Fault offset: 0x00247710
Faulting process id: 0xe90
Faulting application start time: 0x01ceacbc178b0d0f
Faulting application path: E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_777X.DLL
Report Id: 448f2719-18cf-11e3-b7be-10bf487f3cfc

 

 

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="Application Error" />

  <EventID Qualifiers="0">1000</EventID>

  <Level>2</Level>

  <Task>100</Task>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2013-09-08T21:40:24.000000000Z" />

  <EventRecordID>68789</EventRecordID>

  <Channel>Application</Channel>

  <Computer>DannyFong-PC</Computer>

  <Security />

  </System>

- <EventData>

  <Data>fsx.exe</Data>

  <Data>10.0.61472.0</Data>

  <Data>475e17d3</Data>

  <Data>PMDG_777X.DLL</Data>

  <Data>1.0.0.0</Data>

  <Data>52256029</Data>

  <Data>c0000005</Data>

  <Data>00247710</Data>

  <Data>e90</Data>

  <Data>01ceacbc178b0d0f</Data>

  <Data>E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data>

  <Data>E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_777X.DLL</Data>

  <Data>448f2719-18cf-11e3-b7be-10bf487f3cfc</Data>

  </EventData>

  </Event>

[300leex 0]

I also experienced CTD a few times with the 777x which I never ever had once with NGX and 747x with the same setup and addons. werid!

[VH_JLC 1]

I also experienced CTD a few times with the 777x which I never ever had once with NGX and 747x with the same setup and addons. werid!

 

I even got my 1st OOM last night at 500ft :(

I used to read about them now im a sufferer lol hopefully a service pack will follow soon

[troyk 27]

I don't know if you are having the same issue but my FSX crashes if I have the 777 as the default aircraft on startup. Through experimentation I changed the default plane and flight and the problem went away.

[roshanf 1]

PMDG_777x.dll seems to be faulting for me as well. Here is the error I get.

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: PMDG_777X.DLL, version: 1.0.0.0, time stamp: 0x52256029
Exception code: 0xc0000417
Fault offset: 0x0022035a
Faulting process id: 0xd10
Faulting application start time: 0x01cea96b49574811
Faulting application path: D:\Program Files (x86)\Microsoft Flight Simulator X\fsx.exe
Faulting module path: D:\Program Files (x86)\Microsoft Flight Simulator X\GAUGES\PMDG_777X.DLL
Report Id: f8aba82f-155f-11e3-bf16-00241d721728
Faulting package full name:
Faulting package-relative application ID:

 

 

It seems to work fine if I load only, and only, the 777. The trouble starts the moment I try to switch between aircrafts or ending a flight with the 777. The only solution for me as of now is to restart FSX every time I finish a flight or would like to change to another aircraft /reset the flight.

 

I have written to PMDG support for the issues reported above and here is what their kind technical support had to say.

 

Quote:

"The aircraft cannot be loaded over itself, period. There are long-standing bugs in FSX that prevent us from re-initializing some critical internal variables when the gauge loads over itself like that. Every airplane we've ever made for FSX has this limitation, as do many other complex addons that have FMCs and finite-state systems modelling like this. Something weird or an outright crash happens to all of them."

 

A dead giveaway for the problem is when you look at the 777 moving animation on the Free Flight page after ending a 777 flight. I have attached a before and after image of the 777 and on the 2nd one you can clearly see that the engines have lost their blades. Kinda looks like those impulse engines on star trek.

 

I can suggest trying to plan ahead and use only the 777 before restarting FSX. See if that works for you'll.

 

Edit

 

Forgot to mention that I tried formatting and reinstalling Windows and FSX. That really does not help. For those who have a problem loading a 777 dll file at FSX start up or starting a flight with the 777, try creating a backup of your fsx.cfg and dll.xml and deleting them from its default location. If it works you know where the problem is and will have to figure out which lines in the original files are creating a problem. If it doesn't you can safely restore them from the back up.

Edited September 9, 2013 by roshanf

[VH_JLC 1]

just doesn't seem right :(

[DAL1850 51]

I'll guess I'll append myself to this long list of sorrow:

 

http://forum.avsim.net/topic/420079-access-violation-after-installing-ops-center-update-livery-install/

[ceze 1]

sure doesn't Josh. Still waiting for an answer for my ticket. Having the CTD on aircraft load and error log from appcrash report is pointing to PMDG_777X.dll        http://forum.avsim.net/topic/418501-fsx-crashes/#entry2787570

I'll guess I'll append myself to this long list of sorrow:

 

http://forum.avsim.net/topic/420079-access-violation-after-installing-ops-center-update-livery-install/

I do not recommend u reinstall. Done it a couple of times, once with updating OP Center, the second without, same result, CTD on craft load.

[chumley 0]

I even got my 1st OOM last night at 500ft :(

I used to read about them now im a sufferer lol hopefully a service pack will follow soon

Have you checked out the Process Explorer recommended in the docos on the 777 to see what is happening VAS wise?

 

I had a look last night and noticed I was running at about 3.7gb which surprised me. I then made sure that the 'default' flight was the one recommended by MS (Kite at Friday Harbour I think) and then loaded the 777, changed the time, changed the location and hit the 'Fly Now' button and Process Explorer http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx  showed it stabilised at 2.9gb and that was at ORBX YBBN, 50% AI, 50% GA and other settings as recommended.

 

Initially I had FSX crashes every time I breathed. I stopped breathing during the load but it didn't help. Then suddenly, everything started to go Ok and I got a 3hr YBBN to NZAA flight completed (horrible landing but that is another story). I then followed the advice from PMDG and FSX bombed and continued to do so even after I reloaded the deleted files.

 

Once again I uninstalled and reinstalled the 777 and once more (touch wood) everything is back operational. I once again managed a 3.75 hr flight back from NZAA to YBBN with no issues (better landing this time).

 

Just thought it worth recounting my experiences since I was in the same boat as you.

[ceze 1]

I feel a lil bit ashamed for overlooking the  "PMDG 777 issue tracking thread". I think it resolved my CTD on load issue. Maybe it would be helpful for u.   http://forum.avsim.net/topic/418750-pmdg-777-issue-tracking-thread/

 

 

In my case i had to delete runways.csv in FSX root folder and ARPT_RWY.dat in FSX\PMDG\NAVDATA folder.

[DAL1850 51]

I feel a lil bit ashamed for overlooking the  "PMDG 777 issue tracking thread".

 

False. The only party who should have egg on their face is the developer and/or their testers for allowing an 18-wheeler this large to pass through a hole this big - not the customer who just paid them $90.00.

 

"Everything seems to work except for Fly Now. Ship it!"

 

I award four ponies.

 

In any event: thank you, Ceze. The navdata appears to be the problem, which explains why the condition persists across reinstallations. I recreated runways.csv, nuked the T7-supplied navdata, and installed my prior PMDG AIRAC database (don't even want to mess with the new one). We seem to be back to square 0 now. Fantabulous. I may now resume beta testing.