PMDG 777X  5Hours flight ended with CTD.

 

Here is the error log:

 

Description

 

 

 

A problem caused this program to stop interacting with Windows.

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

 

 

 

 

Problem signature

 

 

 

Problem Event Name: AppHangB1

Application Name: fsx.exe

Application Version: 10.0.61637.0

Application Timestamp: 46fadb14

Hang Signature: f7fc

Hang Type: 256

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Hang Signature 1: f7fc88831a14516a1a53b7dc654b9c89

Additional Hang Signature 2: f3d5

Additional Hang Signature 3: f3d55c16b65012e01598a03e518668c0

Additional Hang Signature 4: f7fc

Additional Hang Signature 5: f7fc88831a14516a1a53b7dc654b9c89

Additional Hang Signature 6: f3d5

Additional Hang Signature 7: f3d55c16b65012e01598a03e518668c0

 I can not understand the log .

Can you please tell me what happened?

THX

 

 

 

 

 

 

 

PMDG 777X  5Hours flight ended with CTD.

 

Here is the error log:

 

Description

 

 

 

A problem caused this program to stop interacting with Windows.

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

 

 

 

 

Problem signature

 

 

 

Problem Event Name: AppHangB1

Application Name: fsx.exe

Application Version: 10.0.61637.0

Application Timestamp: 46fadb14

Hang Signature: f7fc

Hang Type: 256

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Hang Signature 1: f7fc88831a14516a1a53b7dc654b9c89

Additional Hang Signature 2: f3d5

Additional Hang Signature 3: f3d55c16b65012e01598a03e518668c0

Additional Hang Signature 4: f7fc

Additional Hang Signature 5: f7fc88831a14516a1a53b7dc654b9c89

Additional Hang Signature 6: f3d5

Additional Hang Signature 7: f3d55c16b65012e01598a03e518668c0

 I can not understand the log .

Can you please tell me what happened?

THX

 

The log does not show a faulting module or .dll file that is causing the issue. It'll be difficult to diagnose the issue if there was no faulting module.

Agree. Plus FSX did not CTD but you had a common AppHang. I suspect you were close to running out of Virtual Address Space (VAS). The AVSIM CTD Guide located to the right of this forum provides detailed information on how to troubleshoot and fix this problem.

 

Best regards,

Thanks  your responses, I was monitoring my VAS through FSUIPC .It was around 900Mb when it happened.

I will go through CTD Guide.

It was around 900Mb when it happened

That's not good. That's what is causing your problem(s).

 

Best regards,

Jim,

 

900MB is remaining VAS. I only start to hear beeps around 300MB.

I implimented all CTD guide and made test flight with same route KEWR-SVMC.  I started recive Scenery Failure warninigs

 

http://imageshack.com/a/img673/365/xajIhe.jpg

 

Many of them. In one point I cannot continue to fly. Stopped the FSX.

 

What is going on?  Where are they  belong? I have only default FSX and Orbix.

How shall I solve this problem?

Thx

Hi Ahmet,

 

When I get less than a GB, I start seeing slow downs and, when I get close to 500MB, it's really not pretty. I run only photoscenery so maybe that's the difference.

 

Best regards,

Jim,

 

My second question was Scenery Failure Watrning?

Do you know what are they coming from?

http://imageshack.co.../365/xajIhe.jpg

My second question was Scenery Failure Watrning?

Do you know what are they coming from?

Sounds like you add the Missing Scenery/Objects parameters as discussed on page 3 of the CTD Guide. When these are employed, your sim will stop until you hit OK. This is most common in the Pacific Northwest for Orbx/FTX. My understanding of the problem is that the missing objects are not a concern and you should disregard. Make sure you never disable any Orbx scenery in the scenery.cfg and only disable Orbx products through FTX Central. It is possible FTX Central got somehow corrupted. You should go back to the default scenery, run FSX, and then reenable the Orbx scenery. It is common to have missing scenery but, during troubleshooting, it could give you an idea what might be wrong with your installation of FSX. Some scenery objects might refer to Orbx scenery you have not yet installed (freeware or payware). The parameters in the fsx.cfg are just more tools you can use to troubleshoot your crash(es) or, in this case, freeze(s).

 

Best regards,

Jim,

At SVMC I got 17 Missing Scenery/Objects paraemeterss . I cliked all OK, but, as soon as I go bact to cockpit view they are keep coming back. I shot down the FSX,

I opened the FSX cfg file and cancel these three items

[sCENERY]
//ShowMissingTextureAlert=1
//MissingLibraryAlert=1
//ShowTriggers=1

 

Then I made a test flight with PMDG777 from KEWR to KDAY. None of them apperead again. I assumed those Missing Sceneries still must be there, because I blocked them to be appear.

This is not good fix.

How can I correct these "Missing Scenery/Objects parameters" 

 

Best regards

How can I correct these "Missing Scenery/Objects parameters"

The missing scenery/objects parameters are normal. They occur a lot in Orbx/FTX scenery but so far I have not seen them causing crashes. Using the missing scenery/objects parameters as discussing the AVSIM CTD Guide just gives you an idea as to what might be causing your crashes. Perhaps the developer of the product should be contacted and advised of all of the missing guids and maybe he/she can fix it in future updates.

 

Best regards,

Jim, Thanks for your info. I will inform Orbx