Ever had an OOM with 59% of your VAS left? I have had exactly the same crash at exactly the same point in my flight three times in a row. I never normally get OOMs. Anyone ever had the same?

 

Check your virtual memory for your computer and see what the settings are.  Maybe that's it.

 

Gregg

Ok thanks for the tip. My virtual memory was set at ~8000MB, I presume this is because I have 8GB of RAM installed (I've never touched it). The "recommended" was ~12,000MB. I set initial to 12,000MB and the maximum to 14,000MB. In any event, this did not solve the problem :(

 

Fortunately, I have an autosave from about 45 seconds before the crash so I am well placed to test the issue. I have so far ascertained that in DX9 mode FSX does not crash at this point. Therefore it would seem logical that the problem is connected to DX10 in some way. I have tried rolling back through the shader settings using the DX10fixer but this has not made any difference. 

 

I will next try flushing the shader cache and will report back. 

Shader cache flush = no fix

FTX Oceanic -> FTX Global = no fix

Uninstall Steve's DX10 fixer libraries = no fix

Revert to pre-REX4 textures = no fix

Hmm. Definitely DX10 related and I definitely have no more ideas. 

Bad texture?  Try turning off your AI.

Bad texture?  Try turning off your AI.

 

Thanks for the tip. Unfortunately on this occasion that didn't work. Although you have opened up an interesting line of inquiry (avatar ^_^ )!

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.

are you using aerosofts EGLL or EDBB? recently after i bought both of those airports my p3d 2.4 has be saying running out of memory, then has run out of memory like the error above, i was just curious to see if it was related.

are you using aerosofts EGLL or EDBB? recently after i bought both of those airports my p3d 2.4 has be saying running out of memory, then has run out of memory like the error above, i was just curious to see if it was related.

 

Afraid not, this is happening around 100km East of Adelaide in OrbX's Australian scenery. 

Check out the AVSIM CTD Guide (link to the right of this forum under Hot Spots). Download and run AppCrashView.

 

We have several suggestions in this guide to help you troubleshoot your problem. One is running Process Monitor during and flight and seeing what was loading when FSX crashed. I did not once. FSX was freezing up in exactly the same location in every flight between Chicago and St Louis. Ran Process Monitor and discovered that MyTrafficX, Version 5.4c, was loading some traffic. It was the only thing loading. I disabled MyTrafficX in the Scenery Library and the crashes/freezes stopped. The AppCrash View report showed the crash was caused by a StackHash and sometimes as the ntdll.dll as the faulting module. I later found out that there is a problem with MyTrafficX schedules and I reverted back to 5.4b and no more crashes. The developer has been informed of the problem as it has occurred to many others but he cannot duplicate. Unfortunately, it's a flight that is trying to start up and the aircraft cannot be found or something is wrong with getting the aircraft to fly the flightplan in the schedule.

 

There are many other suggestions and probable causes for this crash in the AVSIM CTD Guide. Version 2 was just released.

 

Best regards,