Jump to content
Sign in to follow this  
Jetblst

DX10, DX09, FSX Crash to Desktop

Recommended Posts

Hey Folks.

 

Crash to desktops in Windows 7?  

 

Well I cannot speak for Windows 8 or XP, but I can speak for 7.  This find, was THEE most important find for me when it comes to FSX crashing.  Whether using DX9 OR DX10.

 

Please give this a read.  Since I performed this fix I have yet to have a CTD, or OOM crash.

 

 

Here it is.

 

 

http://forum.avsim.net/topic/273341-heres-the-apparent-fix-to-fsx-crashing-win-7-x64/

 

 


Respectfully,

 

Jet

Share this post


Link to post

Sounds like a good find but it's not.  I have proof beyond all reasonable doubts that this "fix" does not work for everyone.  In fact, in some cases, it actually fixes crashes when the module is removed from the main fsx folder.  If you go to the AVSIM CTD Forum and look at the hundreds, maybe thousands, of individuals who reported crashes and look at the AppCrashView report I have asked everyone to submit with their crash, you will see that the uiautomationcore.dll loaded in the individual's main FSX folder but they still had the crash.  The uiautomationcore.dll is part of the Microsoft.net framework which is used by developers to make sure their applications run as intended, including memory management. The appropriate version is installed with FSX and every addon.  I have found that high settings, the BufferPool tweak or other Fsx.cfg tweaks are the best possibilities for the causes of the crashes and not because of some old module from an old version of Microsoft.net.  I have never kept the uiautomationcore.dll in my main FSX folder (yes, I tried it when I had a crash but it would not work).  Many think the module works but I call it a "placebo".  When you have a freeze or crash, individuals will shutdown FSX and maybe their system and thus free up memory resources.  So, after putting the uiautomationcore.dll in their main FSX folder and restarting FSX, of course FSX is not going to crash (right away).  It may never crash again but it's not because of the module.

 

There's more discussion of this in the AVSIM CTD Guide located to the right of this forum under Hot Spots.  I just wanted to set the record straight here and not get everyone's hopes up that there's a magic module out there that fixes everything. 

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post

Thanks Jim, well there you have it...  Your mileage may vary!  


Respectfully,

 

Jet

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...