That is good news . :rolleyes: 

What is the correct application version number?

 

Thanks.

10.0.62610.0

Daniel , thanks for the number. How shall I find it in Steam ? I checked Beta section it is not listed there.

It was downloadable through March 9 - March 16 as an open beta. You had to enter an access code in the beta. The open beta is over now and it reverted me back to 10.0.62608.0.

 

We'll have to wait for the patch to come out.

Thanks.

I had another CTD,but this time MSFSX with  "Application Version: 10.0.61637.0" Is this version belong to FSX-SE? If so why caused crashes when  was flying with MSFSX?

or

Application Version: 10.0.61637.0  Can it be belong to FSUIPC?

Thanks

 

Description

 

 

 

A problem caused this program to stop interacting with Windows.

Faulting Application Path: F:\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: 0

OS Version: 6.1.7601.2.1.0.256.48

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

 

 

 

 

Extra information about the problem

 

 

 

Bucket ID: 582041026

I had another CTD,but this time MSFSX with "Application Version: 10.0.61637.0"

This version is FSX w/Acceleration. You had this exact same crash a little while back - http://forum.avsim.net/topic/448369-what-is-this-error/

 

Best regards,

Jim, thanks.

Is there  any clue why 777 crashed with available 808MB ram?

Is there any clue why 777 crashed with available 808MB ram?

I suspect you mean 808MB of VAS. You should have tons of RAM left. The PMDG 777 does not normally crash with 808MB of VAS remaining. But I have seen VAS being used up at a tremendous rate especially at landing. One second you will have 900MB's left and the next second you are down to 350MB's and the FSUIPC utility is sending out warnings that an out-of-memory crash is imminent. This happens if you have high settings, especially LOD Radius above 4.5 (in FSX/FSX-SE and 5.5 in P3D) and Texture_Max_Load above 2048. It's not the PMDG 777 that is causing the crash, it is just a contributing factor. The scenery you have loaded in the radius of the landing plays a huge part. If you have ASN or another commercial weather program installed, that's another major contributing factor especially if you have moved the radius slider for weather from 90 miles to something higher. REX textures are another major contributing factor. I once had REX4 textures for low and high level clouds set to 32 bit and my fps went from the 40's and 50's to single digits.

 

So, FSX, FSX-SE, and P3D are not those sims that you can set your settings high and get away with it for very long. X-Plane you can because it is a 64 bit application. If you want to enjoy these sims as much as I do, then you need to set your configuration settings to modest levels. Many have configurations for different flight plans and that's a suggestion. For instance, flying the PMDG777 over the default textures (or a texture replacement program like GEX) and out of and into default airports will give you great fps. Lots of VAS too. When you switch to commercial textures, like Orbx/FTX or photoscenery and add commercial airports, then fps and VAS are going to suffer considerably. If you do not want to lower your settings and be careful with modifications of the default scenery, then flight simulation is not for you as it will not be very enjoyable at all.

 

Best regards,

I really appreciated  your detail explanation,, It looks like only solution is keep waiting  for 64 bit application. May be FSX-SE will take the lead and find a way  to re-code the 64 bit, I am just waiting  FSX-SE Beta application, if they developed a patch, may be FSX-SE will solve our problem.    :smile:           

May be FSX-SE will take the lead and find a way to re-code the 64 bit, I am just waiting FSX-SE Beta application,

From all of the information that I have obtained about FSX-SE, there is no way Dovetail can change the code to FSX. They may be able to change/add parameters in the FSX-SE.cfg to make the application run better, but no code changes. FSX and FSX-SE will run more efficiently and faster if settings are lowered in the fsx.cfg. Perhaps the Dovetail techs are able to change the sliders so that, when you max it out if will actually be lower slider settings. Perhaps they are using an updated Microsoft Visual or Microsoft.net application to install and run FSX-SE. It would be great if they had access to the code but Microsoft has not released it. I think the best bet for a 64 bit FSX application is P3D and that may be some years from now.

 

More information on what is contained in FSX-SE is at the following link - https://fsxinsider.com/faqs/. FSX-SE is the Gold Edition of FSX converted to work with Steam. I realize there was an FSX-SE beta recently released and there are no indications in the beta that changes to the FSX code were made. They did fix the infamous G3D.dll crash by doing what the fsuipc.dll accomplished and that was trapping the error. As I have stated earlier in this topic and in other topics, the terrain.dll crash can be fixed by lowering settings. Giving your sim the opportunity to 'breath' works best for everyone and explains why just a few are getting the g3d.dll and terrain.dll errors..

 

Best regards,