First of all thank you for your document on how to solve CTDs!

 

I have been having some very strange performance issues ever since installing global vector, and I don't know if me uninstalling my UTX sceneries have any connection.

 

I got a lot of sudden BEX resulted crashes, but also my VAS run out very very fast, today I got an OOM before even getting into the main FSX menu?!

 

I have never experience FSX so unstable before!

 

Do you have any theories?

I got a lot of sudden BEX resulted crashes, but also my VAS run out very very fast, today I got an OOM before even getting into the main FSX menu?!

That would be possible only if you have a lot of photo scenery as ALL of your photo scenery must load at startup and it uses a ton of resources. There is a lot of freeware photo scenery that may not have been compiled properly.

 

If you do not have a lot of photo scenery, then I have no idea but your can move or rename your scenery.cfg, restart fsx and your default scenery.cfg will be loaded. If that does not solve the problem then move or rename your old scenery.cfg.

 

If that does not resolve the problem, then you may have an issue with one of the modules you might have in the dll.xml that is loaded at startup. You can check to see if this is a problem by moving your dll.xml to a temporary folder, restarting fsx, and see if this fixes the problem. If not, move the dll.xml back to the proper folder.

 

Lastly, you could have a bad tweak set up in your fsx.cfg. I don't believe in tweaks as most do not work, but if you have a bad parameter or it is configured improperly, then that could bring down your fsx at startup (I've never seen it happen but I think the possibilities are there). Just move your fsx.cfg to a temporary directory, restart fsx and see if this fixes the problem. If not, move the old one back to the proper folder.

 

Those are the only possibilities for an OOM at startup. Aircraft would load after you select it in the setup so those could not be the problem.

 

Best regards,

I have to thank you so much for your time an advice!

 

I noticed some textures were missing, but I don't think its anything new, but nice to get it fixed a bit!

 

I tried to fly again yesterday, but around 7 hours into the flight over the pacific I had an OOM, could it be that my PMDG freeware textures are causing this?

 

I noticed after taking off from taxi2gates Hong Kong, I had only around 23% VAS left! This is with AI, but with out any other addon airports besides my destination, FSDreamteam JFK.

 

I have flown before to Heathrow with no problem, and frankly flying over the ocean always brought me to my destination with plenty of VAS left.

 

When I load HKG in the default helicopter with full AI I have 49% VAS steady, I am using the FSX VAS monitor

I noticed that because my FSX was installed on a different HDD than my OS, it didn't have the HDD set to system managed memory like you write about in your guide, can this have an effect?

it didn't have the HDD set to system managed memory like you write about in your guide, can this have an effect?

I recommend a "system managed size" for all HDD's/SSD's. Setting your own page file size takes some expertise and a wrong setup will cause crashes. I remember once flying out of FlightBeam's Dulles International (KIAD) over MSE V2 photoscenery. I had the photoscenery on another HDD and I only had the drive with FSX installed enabled for a page file. The others were set to none. I got major, major stutters/pauses and FSX was not useable. I enabled a page file for all HDD's and the stuttering/long pauses went away.

 

Best regards,

I have had a lot of that lately, thank you so much for your help and your good advices! Its really really appreciated.

I am a bit weary about attempting to fly again, its a bit traumatic to go through so many crashes, I start to loose my confidence in the simulator at one point

I know what you mean. It is no fun taking a long flight and having it crash near the end. Yesterday I had an OOM with a flight from Chicago to KIAD and I had sufficient VAS all the way down to the Approach. Turning on approach, and VAS dramatically got eaten up as I had 600MB's just before turning into the approach and only 100 MB's when FSX froze with an OOM message. The day earlier, same flight, same scenerio and I had 800 MB's at Approach and it went down to 200 MB's on landing but I got no OOM (just a lot of warnings from FSUIPC that I was nearing running out of memory). There was only one small difference between the flights - the flight I did yesterday had two more MSE V2 Photo Scenery States enabled than from the earlier flight. I am going to try to the flight again but this time only enable the Photo Scenery States at departure and at arrival.

 

Best regards,

My flight lasted 8 hours with good smooth running but then suddenly it made an APP crash...

 

This seems to just be random crashes its so strange

 

Problem signature:

  Problem Event Name: APPCRASH

  Application Name: fsx.exe

  Application Version: 10.0.61472.0

  Application Timestamp: 475e17d3

  Fault Module Name: d3d11.dll

  Fault Module Version: 6.2.9200.16570

  Fault Module Timestamp: 5153774d

  Exception Code: c0000005

  Exception Offset: 000a7da4

  OS Version: 6.1.7601.2.1.0.768.3

  Locale ID: 2057

 

Additional information about the problem:

  LCID: 2057

 

Read our privacy statement online:

  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

 

If the online privacy statement is not available, please read our privacy statement offline:

  C:\Windows\system32\en-US\erofflps.txt

Somehow my 777 immersion said that my FSX wasn't installed so I added it again to the registry... could this have an effect? 

Somehow my 777 immersion said that my FSX wasn't installed so I added it again to the registry... could this have an effect?

According to page 11 of the AVSIM CTD Guide the d3d11.dll crash can be fixed as follows:

 

D3D11.dll – Remove Windows Update KB2670838. CTD also occurs with SweetFX installed. Be wary removing the KB if you are using IE10 or IE11 as it will uninstall those programs and go back to IE8. If you reinstall IE10 or IE11, the KB will also be reinstalled.

 

Best regards,

It was installed in May 2013 could that really be a problem?

It has fixed the problem for everyone else.  If you have SweetFX installed, I would remove that first and see if it fixes the problem.

 

Best regards,