Search the Community

For some reason, I suddenly started having CTDs (Crash to Desktop) during assorted FSX flight sessions. I thought I had discovered a cause - having Flight Sim Commander running weather as well as REX 2.0 OD doing real-time weather at the same time. However today, I had FSCommander off and it crashed.As a registered FSUIPC user, I naturally downloaded the latest DLL library and copied it to the FSUIPC folder. Unfortunately, that did not completely eliminate my CTD issue.Got a CTD this morning while I had FSX simulation speed running at 8x on PMDG 737ngx flight from Groton CT to JFK New York. I don't always use the speed-up function in FSX, but I was going to be unable to finish the flight if I ran it at "normal" speed. Bingo- I get the crash when I switched back down from 8x to normal sim rate.I am aware of the UIAutomationCore.DLL fix and had performed that long ago when I first installed FSX, so I knew the problem most-likely lay elsewhere, and having already updated FSUIPC - I had no clue what else to try, so I dug into the crash log to try to discover what modules were involved. Of course FSX itself was running, so it was listed int the crash log report - then another DLL was mentioned.I used the System Event Log to troubleshoot and locate the file that was involved in the crash, and the offender was shown (after googling it) to be a part of Microsoft's C++ runtime library files. So I then went to programs & features to look at the C++ runtimes that were installed, and discovered to my dismay that there several different 'versions' of C++ runtimes, and there were several different iterations (file dates) within those.Simply put, I believed there were WAY TOO MANY C++ runtime files - AFAIK you should only need 1 of each year for 2005/2008/2010. In theory, the 2010 version should be backward compatible with 2005 and 2008, possibly the system would operate with ONLY the 2010 runtime but I didn't take the chance.What I had prior to cleaning out the excess versions:C++ 2005 Runtimesx86 version << didn't think that belonged on a 64-bit version of Win 7 (removed)x64 versions (3 or 4 listed - picked the highest version number and removed all the older ones)x older version number (deleted) y older different version number (deleted)z newest version number (KEPT) x64C++ 2008 Runtimesx64 versions (3 or 4 listed - picked the highest version number and removed all the older ones) w older version (deleted) x older version (deleted) y older version (deleted)z newest version number (KEPT) x64C++ 2010 Runtimes (added by me) x64w current version (KEPT)Since I run Windows 7 --64 bit -- The proper C++ runtime libraries for me needed to be x64 NOT x86 (x86 is 32-bit) If you run 32-bit Windows or Vista, you would keep x86 versions NOT x64.So I found 1 instance of 32-bit C++ 2005 and removed it completely.I removed all but the latest (highest file number sequence) of Versions 2005 and 2008, and then I searched Microsoft and downloaded the 2010 version (x64) as well.So now I have only ONE version EACH of C++ 2005 / C++ 2008 and C++2010 on my system [All are x64]. (Looking at Programs and Features within Control Panel in Win7)I repeated the flight, and cautiously optimistic that the crash problem -- may -- possibly be gone. (It didn't crash again on the same flight plan running 8x sim speed)Elected to share this discovery with others here on Avsim.WARNING: If you're 'new' to PC's you may not have implemented a strong backup schema using a product like Acronis System Image or Windows 7 Built-in Backup. It's always wise to have a full system image (backup) of your machine BEFORE you make any changes (such as I am speaking of here).Of course once you do backups, you also need to know how to RESTORE your machine via those backups. Given the fact that hard disk drives are not bulletproof, you will greatly benefit from instituting a regular scheme designed to re-image your system to an external hard drive (e.g. USB External, eSata External or even in the cloud.Windows System Restore is not the same as restoring from backup - I'm sure there are tutorials on YouTube to cover this topic. Just want to caution everyone to backup their entire system prior to making changes. Worst case scenario: You make changes that later prove to either "not work as expected" or somehow cause problems ranging from low-grade to severe. That's when you pull your Rescue Boot CD out and plug in the external backup drive and "put everything back as it was".For those who already know this topic, I apologize. For those who didn't know about it - in the strongest possible terms it is suggested you undertake the backup advice....Hoping this works I will report back after further testing.Backup!