Dear all

 

So far not very many issues, suddenly I had issues where FSX would crash at around 91-94% of loading the flight.

 

Another time I changed gates at the preflight stage and then while loading the sim crashed.

 

Third scenario after roughly 35 minutes of preflight and flying for over 5 hours FSX crashed

 

Normally the event log shows only that FSX.exe is the faulting path but no reason.

 

one time I saw this:

 

Faulting application path: D:\games\fsx.exe

Faulting module path: C:\Windows\SysWOW64\ntdll.dll

 

But all the other times it just writes:

 

Faulting application path: D:\games\fsx.exe

Faulting module path: unknown

 

Do you have any idea what could be wrong? I did see windows updates were installed, I tried to uninstall but it doesn't seem to have cured it.

 

This is an automatic message.

 

This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
• The images might not have been "illustrative" or "explanatory" in nature.
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

Do you have any idea what could be wrong? I did see windows updates were installed, I tried to uninstall but it doesn't seem to have cured it.

There are several causes of crashes. My suggestion is to take a look at the AVSIM CTD Guide located at the right of this forum under Hot Spots and try some of the investigative techniques or look near the end where he provides probable causes for crashes (the ntdll.dll is there). Most likely you had an Out-of-Memory crash for the over 5 hour flight. People get high powered computers thinking they can turn their sliders up to the max and all it does is eat up the 4GB's of Virtual Address Space (VAS) that Windows provides for applications. High Autogen settings are the biggest culprit but there are many other things involved too like HD textures, including cloud textures. If you want to monitor your VAS you can try the following:

 

Monitoring VAS in FSX or P3DV2 – The freeware or registered versions of the FSUIPC utility will allow you to monitor the amount of VAS remaining during a flight session. This might be valuable in troubleshooting Out-of-Memory (OOM’s).

 

Startup FSX/P3D and then enter the Addon Menu and select FSUIPC. Once FSUIPC is open, click on the Logging Tab and enter 024C under Offset and select S32 under Type. Select where you would like to have the usage displayed. The FS Window is for Full Screen sessions. The FS Title Bar is for Windowed Mode. AVSIM recommends you also check the Normal log file as this provides you information on how much VAS you had to start out with and then it logs usage throughout your flight.

 

The VAS usage is displayed in Kilobytes (KB’s). The value represents the amount of VAS left so, the lower the value, the more VAS being depleted. The max amount of VAS allowed in computers with 64 bit Operating Systems is 4GB’s. This is shared with other applications running in the background on your computer. For 32 bit Operating Systems, the max amount of VAS allowed for FSX/P3D is 2GB’s but this can be expanded to 3GB’s with a switch like the /3GB switch.

 

To convert the KB’s to the amount of GB’s, you should use one of the Byte converters on the Internet like the following: http://www.whatsabyte.com/P1/byteconverter.htm. You will never see 4194304 KB’s displayed as this equals 4GB’s. You might see around 3GB’s (3145728) remaining when you first start up FSX/P3D but that would be unusual. Do not be too concerned with the amount of VAS remaining when you first start up.

You might be interested in a utility in our AVSIM Library called Quantum Leap which allows you to speed up your trip across the US or any ocean but it requires the payware version of the FSUIPC utility - http://library.avsim...php?DLID=179703. According to the developer, “this utility was written to allow an FSX aircraft established at cruise to "leap" to a point further along the flight plan track. It allows the user to select a nav fix or manually enter coordinates for the jump-ahead point, as well as setting a new time in the simulation to be set at the designated leap-ahead point. The primary objective was to leap forward on very long haul flights to eliminate long periods of droning or wrestling with accelerated flight. It was tested with the PMDG® 777 and 737NGX simulations, but will most likely work with most other add-ons.”

 

Hope this helps.

 

Best regards,