MSVCR80.dll Causes Frequest Crashes

Any last suggestions?
Marius
Is it possible that you loko into my pc with team viewer?

All of my suggestions/recommendations are in the AVSIM CTD Guide (which I'm in the process of updating with some minor updates).  Everything you are describing as causing your crashes are related to User Access Controls.  If you do not have the proper permissions, your sim will crash.  I see your installation is outside of the default installation path and that's good.  But you still need to make sure UserAccessControls and any anti-virus program is not running in the background.  You also needed to trust modules when you first started up FSX.  If a module was not trusted, then the module will not work while using FSX.

I would recommend you return FSX to the default configuration.  In the undated version of the AVSIM CTD Guide (not released yet), here's how to return FSX back to the default configuration:

Return to the default configuration - This is done by rebuilding your configuration; disabling add-on scenery; and disabling modules in your dll.xml or exe.xml as follows –

• Rebuild Configurations – Rename your FSX/P3D/FSX-SE configuration with another extension, such as fsx.cfg to fsx.orig, or move the file to a temporary folder, restart the program and let the configuration rebuild. It has been said my many experts that rebuilding your configuration is about the same as uninstalling/reinstalling FSX, FSX-SE or P3D, as appropriate, as it removes tweaks or other parameters that you may have added and may be causing more harm than good or they were not properly set.
• Disable Add-on Scenery – To quickly determine if your scenery.cfg is the problem, move the scenery.cfg to a temporary folder, restart FSX/P3D/FSX-SE, as applicable, and the default scenery.cfg will be installed when you restart the application.  If this stops the CTD’s, then the problem is probably associated with one or more of your add-on sceneries. To find the offending scenery, return the scenery.cfg moved to a temporary folder above back to the hidden folder to replace the default.  Disable all of the add-on scenery via the Scenery Library or the Scenery Config Editor utility.  You will then have to enable your add-ons 3-4 at a time until the CTD returns. AVSIM does not recommend this action unless you know for sure the problem is one of your scenery add-ons. Since an AI program is commonly the cause of CTD’s, disabling your AI program may be all you need to check.
• Move/Disable modules in dll.xml and exe.dll– To quickly determine if your dll.xml and/or your exe.dll is the issue for your CTD’s, move the dll.xml and exe.xml to a temporary folder and restart FSX.  These modules will not be rebuilt but your sim will still load (you just will not have an Add-on Menu).  Sometimes a module you have installed is corrupted or is somehow duplicated in the dll.xml.  If you moved the dll.xml and exe.xml to a temporary folder and the crashes stopped, move the dll.xml and exe.xml files you moved to a temporary folder back to the hidden folder.  You can now check to see which module(s) caused your crashes by disabling all the modules (except the first one). Change the parameter ‘False’ in the line <Disabled>False</Disabled> to True.  Do this for each module until the problem is fixed. 

This is a good way to investigate your crashes.  If you have the default configuration and you still have crashes, then there is something external to FSX causing the crashes.  In the instructions above, I would not move or disable the dll.xml just yet.  You indicated you were trying to program an FMC.  I do not know what aircraft you installed that requires programming the FMC (could be PMDG, Captain Sim, Eaglesoft, or several other aircraft).  These aircraft need to have things loaded in the FMC to work properly.  So, just do the fsx.cfg and scenery.cfg for now.  If crashes continue, then you will have to disable the modules in the dll.xml (except the ones relating to the aircraft you want to fly).

Best regards,