jorgen.s.andersen

I'll allow myself to modify Loki's above statement and say that I have not encountered any add-on of any kind that worked in FSX Gold and not in the Steam version. The only difference I had to get used to was the different and long path to the Steam version. Jorgen

Instead of dealing with all those activation issues, get the Steam version. It comes with Acceleration and a couple of bug fixes, and you can install it without activation on as many computers as you want. Jorgen

I just now realized that I forgot something very important in mentioning the scenery add-ons: you have to wring the AFCAD through AIG's AFCAD-converter... Jorgen

I know that FSX, ADE and AIFP will work in Windows 10, and they should work fine also in Windows 11. I have not tried MSFS 2024, but based on my (albeit short - 30 minutes before I removed it) experience with MSFS 2020, I would recommend P3D instead. Please note that this is a personal opinion, but you, as a FSX user, will be instantly familiar with the file structure etc etc etc in P3D, plus the fact that a lot of FSX scenery add-ons will work in P3D. ADE and AIFP also work in P3D. Jorgen

I have had similar issues in both FSX and P3D, and here's what seems to have solved this for me: 1. Since this throttle probably is attached through USB, then if there are any hubs in the path, make sure they all are powered. 2. Go to Device Manager, and under "Universal Serial Bus Controllers" right-click on each hub in turn and select Properties, then go to the Power Management tab and uncheck any boxes in there. Jorgen

What was the exception code at this new crash? Jorgen

There's no limit to the usage of the DVDs, but there is a limit on the number of activations, if my memory is not too goofy. I remember a cure for this issue from a while ago: copy the DVDs to a hard drive, if you have room enough, then install from there. Another cure would be to get FSX:SE. Jorgen

Just be aware that in FSX there is a limit to how many add-ons there can be in the scenery configuration library. To avoid that, I take the scenery and texture folders from the add-on library and stick them in Scenery\Global\Scenery instead. That works as well. Jorgen

Don, Try going here: https://www.freewarescenery.com/fsx.HTML Tons of stuff to choose from, also from Dan-the-Man French, alias dlfrenchmd - sorry Dan, couldn't help that one Jorgen

The memory exception occurs when a piece of running software - be it Windows or an application - tries to write to an area of RAM where it has no access rights. I would think that rules out hardware errors, and I think we can rule out Windows also as the culprit. So then that leaves applications - of any kind, FSX and others. Under "others" falls whatever is running in the background. To see what there is, hit Ctrl-Alt-Del and select Task Manager, then the Startup tab, where you will see what starts at system boot time. Use your own judgment to see what should be disabled there, only meaning it does not start when the computer boots. Some applications leave stuff running after you close them, but if you do a boot-up before running FSX, then you know there will be a minimal number of things running in the background. In FSX I also think we can rule out the default aircraft - I don't think I've ever seen error reports about them. Of the add-on aircraft that Edward mentions above, I have, or have had, all of them, both in FSX and P3D with no problems. I don't think a damaged model or livery could cause the exception error (usually the aircraft doesn't show at all or is black all over), but I cannot rule that out either. So that leaves "other" kinds of add-on that you either have now or had at one time - because some that you used to have might have left "stuff" behind when they were uninstalled. What do you have, or used to have, that could fall in this category? Sorry for the long rant - but don't worry, it gets longer! System care: is Windows updated fully? Run Windows Update, but do this: under Update, in Advanced options, is the little switch "Receive updates for other Microsoft products" set to On? If it is not, switch it to On and run Update. Leave the switch in the On position. This will ensure that your C++ and .NET Framework is up to date, which is very important. Do not worry about DirectX, that is updated when Windows updates, and FSX does not care about DX 12 either, it wants DX 9c or 10. BTW, if you have DX 10 Preview turned on, try to turn it off and see if that helps. As for other system troubles, I don't think you have them, or you would see other exception codes galore. So, in the above, you see a lot of assumptions, "I believe" and "I think or don't" - because there are so many possibilities for this error. A list of your "other" add-ons, past and/or present, may certainly help us narrow this down. Let us know how this goes - Jorgen

I must say that I have not seen the AIM ERJs or their liveries cause errors like this (I have all 3 of them), but I cannot rule out that they could be the cause.. I believe (but my opinion only) that the error more likely comes from a flyable aircraft or a scenery add-on. Edward, could you post just general list of what add-ons you have? Jorgen

Our good old friend: Exception code: 0xc0000005 is there again. The offending add-on is still present. Jorgen

From within your error reports, especially the Windows Event Viewer, comes this: Exception code: 0xc0000005 This is a memory exception error, meaning that "something" attempted to write to an area of RAM where it had no access rights. Note: this has nothing to do with the 4 GB VAS that FSX operates in, this is a direct RAM write attempt gone wrong. There is nothing to show directly what this "something" is, but since ai_player.dll is mentioned as the faulting module name, it could be something related to AI or an AI add-on. In all the cases of this exception code I have seen, both here and on prepar3d.com, this has proven to be caused by an add-on of some sorts. Jorgen

Before you begin installing, let's make sure that all remnants of FSX are really removed. First, in Windows Control Panel, make sure FSX is uninstalled from there (I have no idea of what the PMDG uninstall instructions say). Then, in Windows File Explorer, go to the drive where FSX was installed, and in the search box type: fsx and let the search run. Delete what was found. If this drive was different from the C drive, repeat this on the C drive. On C there will be items that cannot be removed, just skip those. Reboot. Now, create a folder on C and call it for example C:\FSX (if you haven't done so already). This is to keep FSX out of the reach of UAC. Install the first 2 disks to there, and at the end of the installation (important) fly around for a minute or so. Shut FSX down. Activate. Reboot. Now install the Acceleration disk, at the end again fly around for a minute. Shut FSX down. Activate Acceleration. Reboot. Now you should be ready to go. If you have a second drive, consider installing FSX on that instead of on C, just follow the above procedure. Happy flying - Jorgen

Loki is correct, it's usually the VAS space that one runs out of, and that is unfortunately a hard limit, due to FSX being a 32-bit application. But there is something a user CAN do within that limitation - try to go here: This is a page that I used to tweak my own system way back when I had FSX, and some of it is actually applicable to P3D today. Jorgen

After you installed and activated the base FSX, did you then: Fly around for a few minutes, then shut down FSX and reboot? And then only after the reboot install Acceleration? Jorgen

Kalorien, when you have the crash at LGAV, what is then in Windows Event Viewer? Jorgen

A good thing to do is to turn off User Account Control, which will stop Windows from interfering when you try to do something with your files. Here's how: https://articulate.com/support/article/how-to-turn-user-account-control-on-or-off-in-windows-10 This works in Windows 10 and 11. Another thing is that your Windows, as well as some other libraries, need to be up to date. Run Windows Update, and in Update, under Advanced options, make sure the switch "Receive updates for other Microsoft products" is set to On. Leave this switch in the On position. Jorgen

If the error occurs on a default install of FSX, guaranteed without any add-ons, then to which folder did you install FSX? The default location under C:\Program Files(x86) is, hmmm a less than ideal location. Create a folder called for example C:\FSX and install to that. Even better if you can do it to a different drive than C:. You also need to give yourself Administrator rights. Google on how to do this. And finally, when you get to installing: turn anti-virus off completely, and run the FSX installer as Administrator. Jorgen

Matthew, I have already diagnosed the exception code, as described above. I also, in my first post in this thread, out lined a course of action, which you need to follow: "Find a flight and a point in the flight where the CTD is guaranteed to occur. Then uninstall your add-ons one at a time and retry the flight until the CTD no longer occurs. Or, if you prefer, do a clean install of FSX only, redo the flight to make sure that it does not occur in a default install, and then install your add-ons, again one at a time." I repeat: until you find the offending add-on, this problem is going to continue to frustrate you. You could maybe provide us with a list of your add-ons? Jorgen

Sorry, I should have gone back there. But you need to go back up there also and read my post about the exception code Exception code: 0xc0000005 Because until you fix whatever is trying to write where it has no access rights, this problem is not going to go away. And it is not an OOM issue. Jorgen

What is in Windows Event Viewer at the time of the crash? Jorgen

"Interpreting the Event Viewer" isn't exactly rocket science, since I am able to figure it out. First of all, you note down the time of a crash. If you don't have the time, provoke a crash. Then right-click on your Windows Start button, and select "Event Viewer" from the menu. Click on the little arrow next to "Windows Logs", then on the arrow next to "Application". Now, in the top center pane scroll down to the time of the crash, and there should be one or two entries at that time labelled "Error". Highlight each of those, and the error information will show in the bottom center panel. This information you can then copy into a post here. All I am doing then is take the "Exception code" from the report, and search the web for it.... easy peasy, no magic involved. The most common exception I encounter is C0000005, which is a "Memory Exception" - "something" attempting to write to an area of RAM where it has no access rights. In all the cases I have seen of this one, the culprit has turned out to be a badly programmed or incompatible add-on. Jorgen PS: our beloved friend Mr. Zippy has a nice graphic of where to go in Event Viewer.

The FAIB models are exclusively AI models, with an AI FDE. Modify and fly such at your own risk. Jorgen

What, if anything, is in Windows Event Viewer at the time of the error? Jorgen