Second flight before a while and a CTD error. The weird is that in Appcrashview nothing was recorded, only in event viewer i found the error.

  Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="Application Hang" />

  <EventID Qualifiers="0">1002</EventID>

  <Level>2</Level>

  <Task>101</Task>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2013-10-17T19:50:10.000000000Z" />

  <EventRecordID>6564</EventRecordID>

  <Channel>Application</Channel>

  <Computer>Bradner-PC</Computer>

  <Security />

  </System>

- <EventData>

  <Data>fsx.exe</Data>

  <Data>10.0.61637.0</Data>

  <Data>bd4</Data>

  <Data>01cecb64b5627385</Data>

  <Data>130</Data>

  <Data>G:\Microsoft Flight Simulator X\fsx.exe</Data>

  <Data />

  <Binary>55006E006B006E006F0077006E0000000000</Binary>

  </EventData>

  </Event>

Sorry to hear you are still having problems.  This is not good that you are still having issues.  Something is seriously wrong with your system for it to CTD or hang up all of the time.  The Event ID indicates you had an Application Hang and not a CTD.  This is probably because fsx couldn't accomplish something while running FSX.  Maybe it couldn't connect to the Internet.  Perhaps it was because it could not find a texture or gauge that was being called by FSX.  If it cannot do something, it will hang up or CTD depending on the severity.  Lots of times there are other things going on in the background with Windows.  Perhaps Indexing.  So FSX freezes or hangs up as the system is just too busy to handle all of the FSX requests.  Just like a CTD, I know of no solution.  It's in your system.

 

What I would do now is run a program to scan your system for corrupted files - http://pcsupport.about.com/od/toolsofthetrade/ht/sfc-scannow.htm.

 

If that doesn't fix the problem, then I would download and run a freeware driver scanner.  This program will scan your system for any outdated drivers for your system bus, usb ports, and other things that Windows Update does not do.  If it finds any problems, it will offer to download and update the drivers but for a small subscription fee (usually around $19 a year).  You can find one by going to Google.com and searching for driver scanners.

 

If that doesn't fix the problem, then run a program like CCleaner.  It will clean up your system and fix any problems with the system registry.

 

If that doesn't fix the problem, then make sure your anti-virus program is disabled while running FSX. 

 

Hope this helps.

 

Best regards,

Jim

I used to run a driver update programm but because of installing a faulty driver my pc starts BSOD and i unistalled it! Is there any possibility the problem is due to the copy and pasted fsx.cfg from the past?

I run a "sfc /scannow" but there is no error! 

 

 

used to run a driver update programm but because of installing a faulty driver my pc starts BSOD and i unistalled it!

 

This can happen if you are running an anti-virus program in the background.  Anti-virus programs do not like to have system files changed or the registry tampered with.  So, when you are installing a new driver, your anti-virus program will not install a file or make a required registry change and that will then cause your system to crash.  You have to trust certain downloads and attempts to update your system.  An anti-virus program is good if you get an e-mail with an attachment and you open the attachment and a program starts running.  It will stop it until you say it is okay.  This is the problem with User Access Controls (which should be disabled) and/or anti-virus programs. 

 

 

 

Is there any possibility the problem is due to the copy and pasted fsx.cfg from the past?

 

As I've stated, one should not use an old Fsx.cfg after reinstalling FSX.  Some people have had no problems.  Many others have had problems.  You can rename your current fsx.cfg to fsx.orig and then restart FSX and let the config rebuild.  If the problems go away, that was the problem.  If the problem continues, then it is something else and you can go back in and rename the fsx.orig back to fsx.cfg.

 

Best regards,

Jim

This can happen if you are running an anti-virus program in the background.  Anti-virus programs do not like to have system files changed or the registry tampered with.  So, when you are installing a new driver, your anti-virus program will not install a file or make a required registry change and that will then cause your system to crash.  You have to trust certain downloads and attempts to update your system.  An anti-virus program is good if you get an e-mail with an attachment and you open the attachment and a program starts running.  It will stop it until you say it is okay.  This is the problem with User Access Controls (which should be disabled) and/or anti-virus programs. 

 

I installed a driver update programm and again BSOD after driver installation. The anti-virus was turned off. I prefer update the drivers manually by myself from the manufacturers site. 

I ll try what you told me about fsx.cfg and i ll inform you!

I have found that if I right click on views too many times, I will get the CDT, so don't try to do that too often and have not had any trouble with CDT's.  Just a thought, and would love to know why this happens???

I have found that if I right click on views too many times, I will get the CDT, so don't try to do that too often and have not had any trouble with CDT's.  Just a thought, and would love to know why this happens???

For me this not happens due to switching views! It happens sometimes but not because of this! The reason of happening we are searching in order to fix it. I hope to find it soon!

I have found that if I right click on views too many times, I will get the CDT, so don't try to do that too often and have not had any trouble with CDT's.  Just a thought, and would love to know why this happens???

Supposedly the Vista version of the uiautomationcore.dll placed in your main fsx folder will fix this issue.  I would recommend Version 6.0.5840.16386.  This happens as it takes a lot of memory to click on View and on the FSX menu.  After awhile FSX will shut down.  It's a known bug.

 

Best regards,

Jim

Supposedly the Vista version of the uiautomationcore.dll placed in your main fsx folder will fix this issue.  I would recommend Version 6.0.5840.16386.  This happens as it takes a lot of memory to click on View and on the FSX menu.  After awhile FSX will shut down.  It's a known bug.

 

Best regards,

Jim

I already have  uiautomationcore.dll in my fsx folder. Also the CTD is not happening any time by switching cameras! The last CTD was while flying and i didnt press anything on fsx.Actually i was not at the PC, when i returned it has crashed! 

I already have uiautomationcore.dll in my fsx folder.

Perhaps that is the problem.  Make sure it is the correct 32 bit version.  Switching views with the S or Ctrl S or the A or Ctrl A key can take up huge amounts of VAS (virtual address space) too.  Download and run AppCrashView and copy and paste the results here so we can take a look at the report. 

 

Best regards,

Jim

Sorry for not responding so many days, but i was checking fsx for CTDs. So i was made 6 flights and in the 2 i had a CTD. The second happens before a while and as I tell in one of my previus posts my appcrashview is not recording, so i send the CTD record from event viewer! 

 <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="Application Hang" />

  <EventID Qualifiers="0">1002</EventID>

  <Level>2</Level>

  <Task>101</Task>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2013-10-24T22:08:57.000000000Z" />

  <EventRecordID>8486</EventRecordID>

  <Channel>Application</Channel>

  <Computer>Bradner-PC</Computer>

  <Security />

  </System>

- <EventData>

  <Data>fsx.exe</Data>

  <Data>10.0.61637.0</Data>

  <Data>111c</Data>

  <Data>01ced0e7acb7fa68</Data>

  <Data>120</Data>

  <Data>G:\Microsoft Flight Simulator X\fsx.exe</Data>

  <Data />

  <Binary>55006E006B006E006F0077006E0000000000</Binary>

  </EventData>

  </Event>

The second CTD happens after 2,5 hours of flying! 

FSX is hanging, not crashing.  So, why is it hanging?  It's because you have something else running in the background.  This happens to me if I enable all of my photoscenery, plus all of my FSDT sceneries, all of my FlightBeam sceneries, and, of course, my AI program and AS2012.  I'll then put all of my sliders near the max, my display driver settings to the max, and then I'll fly the PMDG 777 or the PMDG 737NGX and FSX hangs up, drops to the desktop and wants to restart.  Go figure!  I have a powerful system and lots of memory.  No way my system should be freezing up (hanging).   I don't use any tweaks but I have tweaked my LOD_Radius setting and my Texture_Max_Load settings to 6.5 and 2048 respectively.  I want eye-candy!  I discovered after doing all of this that my settings and the number of sceneries being loaded were way too high.  They were eating up memory and taking away a lot of my enjoyment (okay, most of my enjoyment).  I decided to download and use the SceneryConfigEditor so that I could only enable the areas my flightplan would be using.  I lowered by scenery sliders to what was recommended by developers such as those at FTX/Orbx (they have a configuration guide in every manual) and MegaScenery developers.  Success!  No more freezes/hangings.

 

So, it is really hard to say what really caused your crashes but I suspect one of the scenarios above might fit.

 

The uiautomationcore.dll in the main fsx folder is also known for causing freezes/crashes.

 

Best regards,

Jim

I ve done everything you insisted me till now, but my fps are low especially on a foggy weather. My cloud density is at medium but the same thing with fps. I want to ask me if in my fsx.cfg the FIBER_FRAME_TIME_FRACTION=0.5 makes any difference. Should i lower it? The problem with my fsx is because of a weak CPU?