PDA

View Full Version : Mid-Flight CTD Help Needed!



RyanJZ
December 22nd, 2017, 07:45
Hi guys,
FSX-SE keeps crashing every single flight I do now, and I don't know how to fix it. I already tried deleting the logbook bin.
Here's my event log.


Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: MSVCR80.dll, version: 8.0.50727.9307, time stamp: 0x589acae6
Exception code: 0xc000000d
Fault offset: 0x00008aa0
Faulting process id: 0x2b4c
Faulting application start time: 0x01d37b3ec5eba636
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a 1e18e3b_8.0.50727.9307_none_d0882a20442f72e4\MSVCR 80.dll
Report Id: f2acfe85-1cf1-40bd-8c59-19db027726aa
Faulting package full name:
Faulting package-relative application ID:

MrZippy
December 22nd, 2017, 07:59
Try looking through this thread about the same CTD you are getting. http://forum.aerosoft.com/index.php?/topic/96119-fsx-crashes-telling-me-the-problem-is-msvcr80dll/

RyanJZ
December 22nd, 2017, 08:11
I will try these steps tonight after work. In the meantime, what makes you think its Msvcr80?

MrZippy
December 22nd, 2017, 09:21
I will try these steps tonight after work. In the meantime, what makes you think its Msvcr80?

Either a little birdie whispered it in my ear, or the fact your "faulting module" is MSVCR80.dll :encouragement:

Bradburger
December 22nd, 2017, 10:40
For what it's worth, I have the FSX SE crash from time to time caused by MSVCR80.dll.

Haven't been able to figure out why, but it happens regardless of what third party aircraft or addons (plus ASN16, Accufeel, FSUIPC etc) I'm using, so therefore happens with the default aircraft as well.

One would hope that MS would actually check out these crash reports and look into the issue and issue a fix, or at least liaise with Dovetail and Steam, if it is either FSX SE or the Steam software that is causing the issue.

(Maybe they have!) :banghead:

Thankfully, it doesn't seem to be as prevalent as it used to be (running a fresh install of Win10 1709), but it still crops up from time to time.

Just one of those annoying niggles I have got used to!

Cheers

Paul

RyanJZ
December 22nd, 2017, 12:35
Oh geez this is embarrassing. I didn't even look there- I just looked for the error code!

Bradburger
December 22nd, 2017, 18:04
Well, there you go, just had this CTD after exiting a flight in the RA Spitfire XIV!


Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: MSVCR80.dll, version: 8.0.50727.9348, time stamp: 0x59a71bf3
Exception code: 0xc000000d
Fault offset: 0x00008aa0
Faulting process id: 0x16f4
Faulting application start time: 0x01d37b8e906b2a77
Faulting application path: D:\Games\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a 1e18e3b_8.0.50727.9348_none_d08c1480442bf1e1\MSVCR 80.dll
Report Id: 3f32a03b-d8d9-43be-b891-45a3d052bfac
Faulting package full name:
Faulting package-relative application ID:


Cheers

Paul

RyanJZ
December 23rd, 2017, 04:29
Just a little update- I repaired the redistributables, and ran a windows update. So far so good. Thanks guys!

RyanJZ
January 11th, 2018, 17:25
Well it's back to crashing again. Same error code. It's really hard to understand because I JUST downloaded and installed the 2005 Microsoft redistributables a couple nights ago. Maybe I missed one? Can someone post some links to the necessary installers just so I can be sure I'm not missing anything?

Bjoern
January 12th, 2018, 08:07
As an insurance against missing runtime libraries, I have all C++ Redistributable packages I could find installed, both the x86 and x64 versions.

There's a tool for this, but I haven't tried it.
http://www.majorgeeks.com/files/details/visual_c_runtime_installer.html


If FSX still crashes, you should find out if there's a pattern. Only with a certain aircraft, only in a certain region, etc...anything that narrows down the probable cause.

RyanJZ
January 12th, 2018, 13:03
As an insurance against missing runtime libraries, I have all C++ Redistributable packages I could find installed, both the x86 and x64 versions.

There's a tool for this, but I haven't tried it.
http://www.majorgeeks.com/files/details/visual_c_runtime_installer.html


If FSX still crashes, you should find out if there's a pattern. Only with a certain aircraft, only in a certain region, etc...anything that narrows down the probable cause.
Thanks for the link Bjoern. I'll try it out and let you know how it works

RyanJZ
January 14th, 2018, 15:04
Well its still crashing. But it seems to only do it in the Midwest, which is really bothersome because I do a lot of coast-to-coast flying and I have no idea how I would fix that, other than a full reinstall

Bradburger
January 14th, 2018, 16:08
Well its still crashing. But it seems to only do it in the Midwest, which is really bothersome because I do a lot of coast-to-coast flying and I have no idea how I would fix that, other than a full reinstall

Ryan,

Unfortunately, (and as i mentioned above) I have had this problem with FSX SE for a long time now, and nothing seems to fix it (such as reinstalling the Visual C++ packages, disabling add ons, and even reinstalling FSX and Windows 10).

After the Windows Fall Creators update which buggered up the selecting of 2D windows in FSX, I did a fresh Windows 10 1709 install, along with everything else, and from time to time, I still get these annoying crashes!

Whilst Windows has sent god knows how many crash reports to MS, I have had nothing back or found out why they happen.

You would hope MS could give an answer!

Cheers

Paul

RyanJZ
January 14th, 2018, 16:33
Ryan,

Unfortunately, (and as i mentioned above) I have had this problem with FSX SE for a long time now, and nothing seems to fix it (such as reinstalling the Visual C++ packages, disabling add ons, and even reinstalling FSX and Windows 10).

After the Windows Fall Creators update which buggered up the selecting of 2D windows in FSX, I did a fresh Windows 10 1709 install, along with everything else, and from time to time, I still get these annoying crashes!

Whilst Windows has sent god knows how many crash reports to MS, I have had nothing back or found out why they happen.

You would hope MS could give an answer!

Cheers

Paul
I doubt MS will touch FSX anymore, since Dovetail owns the rights to it now. The unfortunate reality is that FSX is a 32bit program running in a 64bit system, and as new OS's come out (Windows 11 or Windows whatever), we'll probably see more problems like this. It has me considering moving over to P3D, but I don't believe many of of the addons I've downloaded/purchased would be directly compatible, especially Concorde X. But maybe I'm wrong...

blanston12
January 14th, 2018, 18:32
I doubt MS will touch FSX anymore, since Dovetail owns the rights to it now. The unfortunate reality is that FSX is a 32bit program running in a 64bit system, and as new OS's come out (Windows 11 or Windows whatever), we'll probably see more problems like this. It has me considering moving over to P3D, but I don't believe many of of the addons I've downloaded/purchased would be directly compatible, especially Concorde X. But maybe I'm wrong...
I agree with much of your analysis, having used P3D4 for a while and having lots of old add ons. Most of the FSX add-ons work out of the box as long as you can trick the installer into putting it where you want and they don't get too fancy with the 32 bit DLL's and GAU files, but FS9 aircraft are pretty much DOA.

Bjoern
January 15th, 2018, 04:06
Well, at this point it's be best to start from scratch. Fresh Windows, fresh FSX.

RyanJZ
January 15th, 2018, 04:30
Well, at this point it's be best to start from scratch. Fresh Windows, fresh FSX.
Dang. I was afraid of that. Before I go ahead and do that, is there anything else I could try?

Bjoern
January 15th, 2018, 05:41
Well, uninstalling, rebooting and reinstalling all C++ libraries** is an option (32 and 64 bit versions, if on a 64 bit system! In the case of the 2005 version, also the SP1 release), as is reinstalling FSX. Or deactivating each and every add-on.

If you google "fsx msvcr80.dll", you'll get a lot of results but hardly any where the poster returned to say what fixed the problem*. One of the few resolved threads solved the problem by updating FSUIPC or reinstalling FSX.

I guess at this point, it's entirely up to you to find out what causes and what fixes it.



* For an absolutely awful exaple of this, check this thread: https://www.flightsim.com/vbfs/showthread.php?291204-Fsx-se-Msvcr80-dll
Nothing but a "problem solved!" in the end. This is making me even more mad than no feedback at all.

** Here's a list:
https://blogs.technet.microsoft.com/jagbal/2017/09/04/where-can-i-download-the-old-visual-c-redistributables/

Download and install them ALL. IN THE ORDER GIVEN.

RyanJZ
January 15th, 2018, 05:50
Well, uninstalling, rebooting and reinstalling all C++ libraries is an option (32 and 64 bit versions, if on a 64 bit system! In the case of the 2005 version, also the SP1 release), as is reinstalling FSX. Or deactivating each and every add-on.

If you google "fsx msvcr80.dll", you'll get a lot of results but hardly any where the poster returned to say what fixed the problem*. One of the few resolved threads solved the problem by updating FSUIPC or reinstalling FSX.

I guess at this point, it's entirely up to you to find out what causes and what fixes it.



* For an absolutely awful exaple of this, check this thread: https://www.flightsim.com/vbfs/showthread.php?291204-Fsx-se-Msvcr80-dll
Nothing but a "problem solved!" in the end. This is making me even more mad than no feedback at all.
I know what you mean Bjoern, some people just take what they need then leave without a trace. That link you provided earlier for the runtime installer, does it handle 32bit and 64bit?

wombat666
January 15th, 2018, 05:50
Dang. I was afraid of that. Before I go ahead and do that, is there anything else I could try?

Prayer?
Kidding.......:biggrin-new:
I haven't had your problem but I'm sticking firmly to Win7 64, and I have FSX-SE, P3Dv3 (temporary insurance), P3D4.1 and my FS9 version of GW3+, all happily co-existing on separate drives.
Sadly I think Bjoern has summed your situation up, a complete clean up followed by a measured installation, testing each addition as you go.
Time consuming but IMHO the only way to sort out the cause of the issue.

RyanJZ
January 15th, 2018, 05:58
If I go the Windows reinstall and FSX reinstall route, what order should I do these in?

Bjoern
January 15th, 2018, 06:05
See my latest edit first. ALL C++ RUNTIMES IN ORDER. NO EXCEPTION. Note that some version numbers are mixed up in that list. Go from lowest to highest.

( Link, again: https://blogs.technet.microsoft.com/jagbal/2017/09/04/where-can-i-download-the-old-visual-c-redistributables/)


- E:

Here's an ordered list for reference:


8.0.50727.42 - 2005
8.0.56336 - 2005 SP1
8.0.59192 - 2005 SP1
8.0.59193 - 2005 SP1
8.0.61000 - 2005 SP1
8.0.61001 - 2005 SP1
9.0.21022 - 2008
9.0.21022.218 - 2008
9.0.30411.0 - 2008
9.0.30729.17 - 2008 SP1
9.0.30729.4148 - 2008 SP1
9.0.30729.5677 - 2008 SP1
9.0.30729.6161 - 2008 SP1
10.0.30319 - 2010
10.0.30319.415 - 2010
10.0.40219 - 2010 SP1
10.0.40219.325 - 2010 SP1
11.0.61030 - 2012 U4
12.0.30501.0 - 2013
12.0.40649.5 - 2013
12.0.40660.0 - 2013
14.0.23026.0 - 2015
14.0.23506.0 - 2015
14.0.24123.0 - 2015 U3 RC
14.0.24212.0 - 2015 U3
14.0.24215.1 - 2015
14.10.25008.0 - 2017
14.10.25017.0 - 2017
14.11.25325.0 - 2017

Most version numbers are for both the x86 and x64 redistributables, with the exception of 8.0.59192/3 and 8.0.61000/1 (one version number for the x86 and x64 release each).

54 files, 410 MB all in all.

JimH
January 15th, 2018, 08:02
I have no idea if my experience would apply, but I was having frequent stutters, and CTDs after about 20 minutes of flying. I tried dis-enabling (unclicking) every scenery in the FSX Scenery Library, except for the sceneries that I was using during a particular flight, and the stutters disappeared almost entirely and the CTDs stopped occurring.

RyanJZ
January 15th, 2018, 09:06
Thanks Bjoern. I'll try again. If that doesn't work I'll try the scenery idea next. Bjoern, after looking through the the list of runtimes, I can see that the installer you provided the link for does not install all of the runtimes

Bjoern
January 15th, 2018, 13:11
Then do it manually, one by one. And don't write my name in every sentence, I'm not that forgetful. Thank you.

RyanJZ
January 15th, 2018, 13:34
Then do it manually, one by one. And don't write my name in every sentence, I'm not that forgetful. Thank you.
Sorry. I start losing track after making several edits to update info:distracted:

RyanJZ
January 15th, 2018, 14:11
One more question: when running a runtime installer and it gives me the option to repair or uninstall, do I click repair?

Bjoern
January 15th, 2018, 17:07
Yes. Come on, straighten up! It's only a computer.

RyanJZ
January 20th, 2018, 07:58
Well after reinstalling every single runtime in order its still crashing. Even after disabling some scenery areas. I guess all I can do now is reinstall Windows and FSX. what a :banghead:

Bradburger
January 20th, 2018, 08:03
Well after its still crashing. Even after disabling some scenery areas. I guess all I can do now is reinstall Windows and FSX. what a :banghead:

And probably you'll still be having these pesky MSVCR80.dll crashes! :banghead:

But I'm keeping my fingers crossed for you.

Good luck!

Cheers

Paul

RyanJZ
January 20th, 2018, 08:13
And probably you'll still be having these pesky MSVCR80.dll crashes! :banghead:

But I'm keeping my fingers crossed for you.

Good luck!

Cheers

Paul
What's incredibly aggravating is that it didn't use to do this:dejection:

RyanJZ
February 5th, 2018, 14:29
Reinstalled FSX:SE, and that seems to have fixed the runtime issues, but now I'm getting errors from g3d.dll and kernel? I've never encountered these before. How do I fix them?

RyanJZ
February 5th, 2018, 15:42
Never mind. Just got an MSVCR80 crash trying to fly the QW787 out of PVD:banghead:
What will it take?????

Bjoern
February 6th, 2018, 06:48
Probably a reinstallation of Windows. If the horse won't walk, shoot it and get a new one. (Don't forget to turn the old one into sausage and steaks though.)