Sign in to follow this  
RVxSpeed

MSVCR120.dll CTD with P3D V3

Recommended Posts

hello,can u guys please take a lot into this matter?
many of the users are having this exact same error & we tried with almost no other addon installed.but,we have one thing in common.it's the pmdg 777.yes i can assure u we all have the latest p3d v3 installer for the pmdg 777.this is more likely to be an issue with the pmdg.

http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=113995&start=75

Untitled_3.jpg

Untitled_2.jpg

Untitled_1.jpg

& to make a summary.we all are having this CTD randomly.some are having on cruise after 3-4hrs with enlarging some panels like ND or PFD.& some of us having it on approach. the last group of us having this just randomly on cruise without touching anything at all.



 

  • Upvote 1

Share this post


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

hello,can u guys please take a lot into this matter?

many of the users are having this exact same error & we tried with almost no other addon installed.but,we have one thing in common.it's the pmdg 777.yes i can assure u we all have the latest p3d v3 installer for the pmdg 777.this is more likely to be an issue with the pmdg.

 

http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=113995&start=75

 

Untitled_3.jpg

 

Untitled_2.jpg

 

Untitled_1.jpg

 

& to make a summary.we all are having this CTD randomly.some are having on cruise after 3-4hrs with enlarging some panels like ND or PFD.& some of us having it on approach. the last group of us having this just randomly on cruise without touching anything at all.

 

 

 

 

 

A few things to check:

 

1. Have you installed P3D into a separate folder from program files (x86).

2. Are you running P3D as administrator.

3. What other addons are you loading at the same time as P3D (FSUIPC, GEX, etc)

 

Also:

 

4. Are you running an overclocked system

5. Have you tried running a repair reinstall of the Microsoft Visual C++ Runtime Libraries under programs and features?

Share this post


Link to post
Share on other sites

A few things to check:

 

1. Have you installed P3D into a separate folder from program files (x86).

2. Are you running P3D as administrator.

3. What other addons are you loading at the same time as P3D (FSUIPC, GEX, etc)

 

Also:

 

4. Are you running an overclocked system

5. Have you tried running a repair reinstall of the Microsoft Visual C++ Runtime Libraries under programs and features?

hello sir.

1.yes i always install p3d outside of program files & also into a separate drive

2.yes

3.no other addons.just 777+777immersion

4.No

5.yes.

Share this post


Link to post
Share on other sites

just did a flight , running only 777 in p3d ...after flying for 3 hours , pushed the ctr buton and p3d crashed, it doesn't matter wich button i press or wicht screen i enlarge , pfd or nd or fmc , when i click on something it crashes...

 

it is getting so frustrating...

Share this post


Link to post
Share on other sites

Already did , this was the respons

 

MSVCRT120.dll is the main runtime dll for programs made with Microsoft's Visual C++ 2013 package. PMDG does not use this version, all of our products are compiled against the 2010 version (MSVCRT100.dll) - thus it's not actually possible for our product to be the direct cause of a crash in the 120.dll because it never uses it. I would look at anything else you have running or potentially P3D itself as the source of the error.

 

Visual C ++ 2010 2012 2013 reinstalled already , P3d says it isn't caused bu theirs program, but in the meantime it crashes very often ..

 

A few days ago i had p3d with the 777 running for more than 23 hours without problems , 2 flights later it crashed after 3 hours when pushing a button or enlarging the pfd or nd.

 

P3d says it isn't caused by their program , so does HIFI and PMDG ,

Share this post


Link to post
Share on other sites

Already did , this was the respons

 

MSVCRT120.dll is the main runtime dll for programs made with Microsoft's Visual C++ 2013 package. PMDG does not use this version, all of our products are compiled against the 2010 version (MSVCRT100.dll) - thus it's not actually possible for our product to be the direct cause of a crash in the 120.dll because it never uses it. I would look at anything else you have running or potentially P3D itself as the source of the error.

 

Visual C ++ 2010 2012 2013 reinstalled already , P3d says it isn't caused bu theirs program, but in the meantime it crashes very often ..

 

A few days ago i had p3d with the 777 running for more than 23 hours without problems , 2 flights later it crashed after 3 hours when pushing a button or enlarging the pfd or nd.

 

P3d says it isn't caused by their program , so does HIFI and PMDG ,

 

Uninstall any 2013 runtimes, and see what happens. Either, something wont work, or you wont have any more crashes. If something doesn't work, you have successfully narrowed down your search for what is crashing the sim. (you may want to run c-cleaner for both files and registry entries after uninstalling, and then reboot before testing)

 

By the way, running the sim for 23 hours non stop is possibly pushing your luck, even the real airplane might only fly one sector of up to 16 hours per day... at the maximum.

Share this post


Link to post
Share on other sites

Uninstall any 2013 runtimes, and see what happens. Either, something wont work, or you wont have any more crashes. If something doesn't work, you have successfully narrowed down your search for what is crashing the sim. (you may want to run c-cleaner for both files and registry entries after uninstalling, and then reboot before testing)

 

By the way, running the sim for 23 hours non stop is possibly pushing your luck, even the real airplane might only fly one sector of up to 16 hours per day... at the maximum.

yes but,u need to understand that we the USERS are trying desperately to sort out this issue which is a direct cause in either hifi,lm,pmdg. & all they do is deny.so,u just can't say 23hrs non stop is possibly pushing our luck.

Share this post


Link to post
Share on other sites

yes but,u need to understand that we the USERS are trying desperately to sort out this issue which is a direct cause in either hifi,lm,pmdg. & all they do is deny.

 

As are we, honestly. You cannot see what we're doing here behind the scenes, so please do not assume. What you've written here is unfair. Not only is it unfair, actually, it's flat out wrong.

Share this post


Link to post
Share on other sites

As are we, honestly. You cannot see what we're doing here behind the scenes, so please do not assume. What you've written here is unfair. Not only is it unfair, actually, it's flat out wrong.

sir i am so sorry,i didn't meant to hurt anyone.but,lots of us(users) are having this issue & when we see no support for that & no response from the developers it's really frustrating for us.i am a developer myself also.we do not release anything until & unless it's a finished product & it has been tested by ourselves & also the users.i don't know at this point which developer to blame.pmdg or LM.but,it's really sad instead of a solution developers keep blaming each other rather than helping the users or try to test again to be sure that they are not experiencing the same issue as we are having.

again sorry if i am being rude.for me OOM is acceptable as many users don't understand the true limit of the simulator itself.But,CTD & at this stage is purely one of the developers fault,it's not the other way around.

Share this post


Link to post
Share on other sites

By the way, running the sim for 23 hours non stop is possibly pushing your luck, even the real airplane might only fly one sector of up to 16 hours per day... at the maximum.

Hi Wes,

 

When the sim was running i was testing the behaviour in flight and on the ground .i was letting the plane in full take off config , with engines running , flaps extended sitting on the runway for 8 hours , after eight hours departed KIAH to Eham and right before the approach i put a hold in the fmc over LAMSO.. used only P3D with default airports , no Nvidia inspector ,no weather , no fsuipc ,no other programs running ( this is my gaming pc with nothing installed other than FSX and P3D.)

 

As soon i pushed a button , P3d crashed,

 

Sometimes i can end a flight but 8 out of 10 it crashes , i even had the same crash when i didn't touched a think and all the crashes were after 3-3-30 hours of flying , and only in air...

 

Gérard

Share this post


Link to post
Share on other sites

Gerard and I have a many page-long thread running in the L-M forum and I am keeping PMDG informed of my findings through the beta channel.

 

The runtimes are absolutely required.. L-M uses Visual Studio 2013 I believe.

 

Of course all the obvious items were checked llike updating the runtimes to latest from MS, and I chased my tail for awhile until I re-read AVSIMs CTD guide and found my bearings.

 

Test trials have been run with a default platform (default config, scenery and no dll/exe addons) with the NGX. I have then added one thing at a time and at this point, after many trials, I have established that it's not a problem with ASN or FSUIPC. I will get a CTD with my prepar3d.cfg and not with a default config file so my focus right now is that file.

 

Last night I ran a trial with the first four sections in the default config changed to look like my config file (GRAPHICS, DISPLAY, SCENERY, MAIN). No CTD. This morning I am running a trail with the the next set of sections changed to look like mine. Eventually I'll find something that is involved with a CTD when it is there and no CTD when it's not. Basic troubleshooting but it takes time. Each trial is 4 hrs.

Share this post


Link to post
Share on other sites

Hi Dan

 

you are correct C++ 2013 is required for P3D , just uninstalled them and tried to run P3D but it wouldn't even start ,

Share this post


Link to post
Share on other sites

I am having the same problem. I am however not even lucky enough to get a event in event viewer. It happens when I try and enlarge the PFD. Has anyone found a fix? PMDG maybe?

 

Marno Koen

Share this post


Link to post
Share on other sites

I updated my testing for this error and unfortunately I'm not able to replicate ... see my response here: http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=113995&start=225#p121446

 

After 11 hours of flight and no issues, had to shutdown and head off to work/office.  My graphics settings and add-on list was pretty extensive/extreme.

 

Cheers, Rob.

Share this post


Link to post
Share on other sites

I updated my testing for this error and unfortunately I'm not able to replicate ... see my response here: http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=113995&start=225#p121446

 

After 11 hours of flight and no issues, had to shutdown and head off to work/office.  My graphics settings and add-on list was pretty extensive/extreme.

 

Cheers, Rob.

 

 

I dont actually get an 120dll. error but fidling around the FMC , undock panels , after 4-5 hours does give me a CTD.

 

Michael Moe

Share this post


Link to post
Share on other sites

This error just came up and bit me for the first time today. It happened after about 110 minute flight. Enough people have reported it both here and on the official LM message board that it is obviously a bug.

Share this post


Link to post
Share on other sites

 Enough people have reported it both here and on the official LM message board that it is obviously a bug.

 

That's conclusive proof that it's a bug?

Share this post


Link to post
Share on other sites

If you read through both this thread and the one on the official site, you will see that users that experienced this issue have only two things in common :

 

1. They are using P3d V3.

2. They are getting the error after long duration flights.

 

There does not appear to be commonality with 3rd party addons and a few people have reported the error with no addons installed. The only other possibilities are that everyone is either experiencing an overclocking side effect or there is a bug in all the recent nVidia graphics drivers that just shows up with P3d V3.

Share this post


Link to post
Share on other sites

I am totally annoyed with this .... i have just tried a trip egll to kbos and yes 3 crashes during the trip all of them mscvr120.dll error

 

I have used the aerosoft airbus 320 on a flight for 4 hrs plus and guess what no crash.

 

Clearly this is a pmdg issue not anything else.... This is a long haul airplane that cannot be used long haul and only short hops 1-3 hrs at the most. What are PMDG doing .... they have charged so much for this p3d version model no discount for fsx pmdg 777 users and simply taken more money for something that just simply does not work... very annoyed that my friend was told it was activesky and the push of the blame onto a different product

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