R6025 Pure Virtual Funcion Call Runtime Error - FSX SE

[pbug]

Hello,
Sorry if it has already been answeres - couldn't find anything.
I got FSX SE from here - Installed on Clean Windows 7 Pro 64bit
No add-ons at all.
However I get Runtime Error R6025 Pure Virtual Funcion Call after some gametime.

System Specs
AMD FX8120
Clean Windows 7 64 bit Pro
Nvidia GTX660ti - Drivers 347.09
Running from SDD

I disabled other planes, airport trafic, road traffic, etc, set max frame rate to 30 - Same issue

[ollie.p0]

I have exactly the same problem, can anybody help???

[C-FPAS]

Try This !! WORK FOR ME (w 7 Pro X64 ) ... - http://www.venetubo.com/fsx.html -

All Peoples with same Folders but not a same Machine .....

[El Vert]

I had this problem too (with a new computer, not on an older one), and the only thing which fixed it for me was something I read somewhere on this board:

1. Delete fsx.cfg, which will cause FSX to create a new one when you start the game again (I actually just cut it out of where it is and saved it elsewhere, just in case).

2. Start the game again so that it creates a new fsx.cfg, then exit.

2. Edit the new fsx.cfg (I used Notepad) and add this parameter:

[JOBSCHEDULER]
AffinityMask=14

Save it, but be sure it's saved as fsx.cfg, not fsx.cfg.txt. Just rename it if that happens.

I'm not sure it's actually necessary to delete fsx.cfg first, but that's what the instructions I saw said to do so I did. You might try just adding that parameter to your existing fsx.cfg.

I have no idea what that parameter does (and it's possible that the number 14 should be something different for your computer), but whatever it is, it worked for me. Before I added this, I would get that runtime error within seconds after speeding up game time, and within 30 minutes or so running at normal time. Haven't had any such errors since.

I would also try the online tool listed above to fine-tune the file. I tried it before adding the affinity mask thing, and it made a bunch of changes but it didn't fix the runtime errors. Once I added the affinity mask parameter, I ran the tool again and it liked the addition. It's a useful tool - it provides instantaneous information, and you can either adopt its changes or not, as you wish.

[95Bravo95]

Yeah, it controls how FSX uses your cores. It is a different number depending on the specifics of your machine. It also has nothing to do with runtime errors, which is with MS visual C++. It is however a very popular "voodoo tweak" for a number of things.

In most cases the error results from FSX calling on C++ to do something it can't do without the proper version of C++ being available, or because parts of C++ are corrupt. Bad tweaks, or improper settings (I.E, maxing the sliders to the point of instability) can also result in this error being thrown, and there are a few other causes. Most likely, deleting the old config, thus restoring the sim back to defaults, is what actually had the effect of "fixing it". The error may or may not show up again in the future, depending on the actual cause.

One problem with FSX, is that a given machine can quite often "do more" than the program itself can handle. If you're like me, you can max all kinds of settings, even beyond what the sim itself allows in menus, and the sim will appear to work. However, below the surface, the sim itself will actually start to become unstable, and even though it seems to run just great at first, it can start throwing up various errors under certain circumstances. I myself see runtime errors about once every six months, when I jack everything up in the config for a good screenshot session, and mostly in aftermaket scenery, like ORBX, or photoscenery. They go away again has soon has I stop torturing the program, making it do things that it can't really handle.

[El Vert]

Thanks for that note Bravo, I'll keep that in mind in case it starts to occur again. I plead guilty to maxing out all of the sliders . . .

[95Bravo95]

No problem. I've been doing this since before MSFS became a MS product, and even I can't resist the urge to max those sliders from time to time, even knowing that it most likely won't end well, lol. ;)

[pbug]

Thanks guys, will test those fixes