Sign in to follow this  
sidhantsv

MSCVR80.dll crash

Recommended Posts

Hi guys!

I'm back this time with the error MSCVR80.dll . I have read the CTD guide and it suggests to uninstall SP2. but I own steam so I need some help here. I didnt fidget with the Visual thingies but yesterday I installed ASN and A2A C182 . I did a trial flight yesterday and everything went smooth. Just today has this error started to appear. (  I HAVE ALSO INSTALLED AN ENB so I'm thinking that may be a suspect too ) Error usually appears at around 2000ft to 4000ft over the runway after takeoff. Any help would be appreciated thanks!

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

The AVSIM CTD Guide was published for FSX and P3D and did not take FSX-SE into consideration when he was released. The MSCVR80.dll belongs to Microsoft Visual C++ 2005 and it indicates that an addon you installed in FSX-SE, without an official installer from the addon developer. So, the Microsoft Visual C++ 2005 installer that was used by the developer to install that product into FSX-SE could not find the proper entries in system registry to show the product was installed. You have to somehow tell that program, "hey! I'm not using FSX (which was installed using Microsoft Visual C++2005)." "I'm using another FSX program that is installed in completely and totally different folders". That's why it is always good to wait until the addon developer comes up with a fix or someone tells you what line in the system registry needs to be changed.

 

Best regards,

Share this post


Link to post
Share on other sites

The AVSIM CTD Guide was published for FSX and P3D and did not take FSX-SE into consideration when he was released. The MSCVR80.dll belongs to Microsoft Visual C++ 2005 and it indicates that an addon you installed in FSX-SE, without an official installer from the addon developer. So, the Microsoft Visual C++ 2005 installer that was used by the developer to install that product into FSX-SE could not find the proper entries in system registry to show the product was installed. You have to somehow tell that program, "hey! I'm not using FSX (which was installed using Microsoft Visual C++2005)." "I'm using another FSX program that is installed in completely and totally different folders". That's why it is always good to wait until the addon developer comes up with a fix or someone tells you what line in the system registry needs to be changed.

 

Best regards,

 

Got the problem fixed :) Was a bad ENB Thanks for your input!

Share this post


Link to post
Share on other sites

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