Runtime Error

[Harper]

I'm getting random Runtime Errors in Free flight by myself, and in multiplayer.

The message is: Runtime Error! Program: SteamLibrary\steamapps\common\FSX\fsx.exe

R6025

-pure virtual function call

This also was included at the bottom in details:

Problem signature:
Problem Event Name: APPCRASH
Application Name: fsx.exe
Application Version: 10.0.62607.0
Application Timestamp: 548b7186
Fault Module Name: terrain.dll
Fault Module Version: 10.0.62607.0
Fault Module Timestamp: 548b71c0
Exception Code: 40000015
Exception Offset: 0008d7a1
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: d62b
Additional Information 2: d62b620d62ce338176d7ab7f6a2db046
Additional Information 3: dffa
Additional Information 4: dffa8eb625f1c95bd6a0fd31a2cb3b2a


The game closes out after I click ok. My friend is getting similar runtime errors.

I have Windows 7 - 64 bit. Anyone else getting these errors?

Thanks

[fly_AirCal]

Statistically shaky, but: Applied some of Bojote's tweaks to my fsx.cfg and didn't get any crashes on a flight that crashed on me the last time.

[Guardian Hope]

I hate to be the person to point out the obvious but do those of you that are having issues have the latest MSVC Runtimes? I noticed that while the problem signatures seem to be eminating from DLLs lime terrain.dll the faulting module is in fact MSVCR.

You need the Visual C++ 13 runtimes in addition to 2005, 2008, and 2010. This game was recompiled with the Visual C 13 compiler.

Its good though that Bojote's tweaks are fixing some of your all's crashing issues though.

[fly_AirCal]

The problem is that they should actually *not* fix anything. They're just config entries.
But then again, HighMemFix in the fsx.cfg did fix FSX for a lot of people before DTG made it standard...

Just noticed that I don't seem to have the 2013 runtimes installed (2005,2008,2010,2012)...and yet FSXSE mysteriously works.
Good call though, will update ASAP.

[Guardian Hope]

引用自 fly_AirCal：

The problem is that they should actually *not* fix anything. They're just config entries.
But then again, HighMemFix in the fsx.cfg did fix FSX for a lot of people before DTG made it standard...

Just noticed that I don't seem to have the 2013 runtimes installed (2005,2008,2010,2012)...and yet FSXSE mysteriously works.
Good call though, will update ASAP.

Yeah for some reason, FSX:SE doesn't install the runtimes but will still launch anyways.

Very few people seem to know Visual C++ 13 exists as it is not often used.

[Vaughn]

引用自 Guardian Hope：

I hate to be the person to point out the obvious but do those of you that are having issues have the latest MSVC Runtimes? I noticed that while the problem signatures seem to be eminating from DLLs lime terrain.dll the faulting module is in fact MSVCR.

You need the Visual C++ 13 runtimes in addition to 2005, 2008, and 2010. This game was recompiled with the Visual C 13 compiler.

Its good though that Bojote's tweaks are fixing some of your all's crashing issues though.

I did all of this, uninstalled and reinstalled FSX-SE several times, reinstalled C++ 05, 08, 10, 13 and still all I get is the same runtime error after about 30 min to an hour. Send DG an email, no response. I give up, ill stick with boxed version and FSHost instead. DG should have worked out all of the bugs before release. Zero support for a game that I had to buy??? Sloppy job for DG in my opinion. Very disappointed.......

[Harper]

Hi Capt Vaughn, You tried the bojote config file fix and it still crashes?

[JK47]

Hey everyone. So I have been troubleshooting this with a friend and we believe we found the solution. To start, this is typically a problem when settings are turned up too high and we have never had to deal with this on old FSX because it would OOM before it even got this far. The .dll's that need to load are being bottlenecked by your pc likely not having its other cores utilized. I had this problem non-stop and fixed it by doing the following.

Start by deleting your fsx.cfg and then start the game. When it starts, exit, go back to your .cfg and enter this line at the top.

[JOBSCHEDULER]
AffinityMask=14

Save and try again. It will allow the bottleneck to be removed and your system should run just fine.

[fly_AirCal]

I had the AffinityMask tweak in my fsx.cfg all along and it still crashed.

[fly_AirCal]

I think I fixed my g3d crash.

I've (re)installed all C++ libraries I could find (2005 SP1, 2008 SP1, 2010 SP1, 2012 Update 4, 2013), as well as .Net (4.5.2) and DirectX from the Steam folder. Let them update through Windows Update.
Ultimately, this didn't fix it, but it retrospect, better to be safe than sorry.

What ultimately helped me most was running Sysinternal's ProcessMonitor (Google!) alongside FSX*. Whenever FSX crashed with a g3d.dll error, ProcessMonitor would show the last file that could not be processed. But not the file was of interest, but the last folder FSX was digging in.
In my case, this was a folder belonging to an AI aircraft.
I dug around the folder and stumbled upon a corrupted model file. After I fixed the model, FSX didn't crash anymore.

So give ProcessMonitor a try to find the source of your crashes.


*Filter rules that need to be added:
1. "Process" "Is" "fsx.exe" then "Include"
2. "Result" "Is" "Success" then "Exclude"

[aracines]

I just got this error too - totally vanilla instalation and totally default settings. There is nothing wrong with my system because I never get or ever got this error with FSX DVD or P3D. It appears that DTG's are getting off to a very shaky start and before DTG starts work on a new flight sim, they better prove that they can correct these flaws in what they have done in FSX-SE. If they do not fix these issues quick - I promise that they will end up just like the MS Flight team....dont worry simmers, we will always have the last say as to what succeeds and what fails.

[FAWSeen]

im haveing problems with trying to save game or switch flight destination in game crashes with no errors just ends games completly any ideas on this?

[FAWSeen]

and there are other functions that will just end game randomly with no error messages as well

[arcandbob]

Older Intel 6 core I7 extreme on an Asus PX58D-E MB 1366 socket and GTX 670 Vid also checking in with random, but persistant R6025 crashes. So it's not just an AMD problem.

[L0lindir Fox]

引用自 Jordan_King_：

Hey everyone. So I have been troubleshooting this with a friend and we believe we found the solution. To start, this is typically a problem when settings are turned up too high and we have never had to deal with this on old FSX because it would OOM before it even got this far. The .dll's that need to load are being bottlenecked by your pc likely not having its other cores utilized. I had this problem non-stop and fixed it by doing the following.

Start by deleting your fsx.cfg and then start the game. When it starts, exit, go back to your .cfg and enter this line at the top.

[JOBSCHEDULER]
AffinityMask=14

Save and try again. It will allow the bottleneck to be removed and your system should run just fine.

This Solution so far seems to have worked for me, it's a stock install, I had the boxed version before but had been deleted before installing steam edition, did this fix before downloading the tweeks, so far so good

[Vaughn]

引用自 Jordan_King_：

Hey everyone. So I have been troubleshooting this with a friend and we believe we found the solution. To start, this is typically a problem when settings are turned up too high and we have never had to deal with this on old FSX because it would OOM before it even got this far. The .dll's that need to load are being bottlenecked by your pc likely not having its other cores utilized. I had this problem non-stop and fixed it by doing the following.

Start by deleting your fsx.cfg and then start the game. When it starts, exit, go back to your .cfg and enter this line at the top.

[JOBSCHEDULER]
AffinityMask=14

Save and try again. It will allow the bottleneck to be removed and your system should run just fine.

I did this and so far FSXSE has been running for a couple hours with no crash and no problems. It looks like this might have fixed my problems!