• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Mid-Flight CTD Help Needed!

RyanJZ

RyanJZ

Members +
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_1fc8b3b9a1e18e3b_8.0.50727.9307_none_d0882a20442f72e4\MSVCR80.dll
Report Id: f2acfe85-1cf1-40bd-8c59-19db027726aa
Faulting package full name:
Faulting package-relative application ID:
 
I will try these steps tonight after work. In the meantime, what makes you think its Msvcr80?
 
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


 
Last edited:
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_1fc8b3b9a1e18e3b_8.0.50727.9348_none_d08c1480442bf1e1\MSVCR80.dll
Report Id: 3f32a03b-d8d9-43be-b891-45a3d052bfac
Faulting package full name:
Faulting package-relative application ID:
Click to expand...

Cheers

Paul
 
Just a little update- I repaired the redistributables, and ran a windows update. So far so good. Thanks guys!
 
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 said:
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.
Click to expand...
Thanks for the link Bjoern. I'll try it out and let you know how it works
 
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
 
RyanJZ said:
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
Click to expand...

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
 
Bradburger said:
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
Click to expand...
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...
 
RyanJZ said:
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...
Click to expand...
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.
 
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...i-download-the-old-visual-c-redistributables/

Download and install them ALL. IN THE ORDER GIVEN.
 
Bjoern said:
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.
Click to expand...
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?
 
RyanJZ said:
Dang. I was afraid of that. Before I go ahead and do that, is there anything else I could try?
Click to expand...

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.
 
You must log in or register to reply here.
Back
Top