FSX SteamEdition in Windows 11

[lucame]

Hi everybody,
it is possible that someone has already answered to my question bur at the moment I have a big issue.
Bought FSXSE on Steam, first install everything was fine, even with ORBX products and payware/freeware addons.
I' ve installed MAIW Conigsby package and CTDs started.
I' ve done everything I' ve found on Steam ( uninstall, reinstall, logbook, ...) without success.
Has anybody a good idea to help me to find a solution?


Thanks a lot

[Firebird]

Do you still get the CTDs if you deactivate Coningsby?

[lucame]

Hi Firebird,

Yes, CTDs are still there, even after a complete uninstall and a new install of FSXSE following JJ's guide.
Is it possible that these crashes are caused by files coming from Onedrive? I' ve found folders that I tought have been deleted in my PC ( now deleted in Onedrive, too).
Tonight I' ll try again and see what happens.

[Firebird]

I don't think so unless you activated folders that are on your one drive.

If you are going to uninstall and reinstall then I would do that and that alone and test in game. What you have to do is find stability then add something else, check stability etc.
When it becomes unstable you have found what was making it crash and can break that down.

If you just through everything back in and then try it doesn't make sense that it would suddenly work. The only way that it would work is if there was a corruption with FSX itself.

Generally speaking, CTDs with a a sim running are down to a missing texture. Either with the scenery itself, in which case it would crash as soon as you go there is those lighting conditions or that you are calling an aircraft that has a texture issue.

what I would do, if you think Coningsby is the problem, install FSX. Make sure it is stable, especially at Coningsby. Then install the scenery from our Coningsby pack - note only the scenery. Check stability.
Finally, install the aircraft and traffic files from our pack and check again.

Now if all that is stable then it says that one of your other additions is the issue, very likely near CGY.

See how you go.

[Jorgen]

Lucame,

To find out exactly what's going on, ideally we need the crash info from Windows Event Viewer.

If you need instructions on how to locate that info, drop a note here.

Jorgen

[lucame]

Hi all,
and thank you for your suggestions.
I ' ll give them a try and l let you know.

[lucame]

This is what I've got with the Event viewer

+ System

- Provider

[ Name] Application Error
[ Guid] {a0e9b465-b939-57d7-b27d-95d8e925ff57}

EventID 1000

Version 0

Level 2

Task 100

Opcode 0

Keywords 0x8000000000000000

- TimeCreated

[ SystemTime] 2024-03-25T18:44:31.4678744Z

EventRecordID 9427

Correlation

- Execution

[ ProcessID] 14280
[ ThreadID] 15368

Channel Application

Computer Casa

- Security

[ UserID] S-1-5-21-917918129-2236430114-343397943-1001


- EventData

AppName fsx.exe
AppVersion 10.0.62615.0
AppTimeStamp 559f9a9a
ModuleName ntdll.dll
ModuleVersion 10.0.22621.3235
ModuleTimeStamp b62363d8
ExceptionCode c0000005
FaultingOffset 00049a65
ProcessId 0x1e0c
ProcessCreationTime 0x1da7ee478fbeade
AppPath C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
ModulePath C:\Windows\SYSTEM32\ntdll.dll
IntegratorReportId 1c49cb9e-276a-4587-9fbb-3398dae4aafd
PackageFullName
PackageRelativeAppId


What is ntdll.dll ?

[Firebird]

It is an OS system file.

[lucame]

Do you think that any OS file is corrupted?

[Firebird]

No it is a catch all error for FS9/X. If it was corrupted I think you would see system crashes not crash to desktops.
I don't think that there is anything useful there but if somebody thinks there is then they will say so.

[Jorgen]

Here's the indication for the culprit:

ExceptionCode c0000005

This is Windows telling you that a memory access violation occurred: "something" attempted to write to an area of RAM where it had no access rights.

Unfortunately, there is nothing to show exactly what this "something" is, but in all the cases of this that I have seen, except for one very exotic one, the cause has been an incompatible or badly programmed add-on. We see this exception code pretty often on Lockheed-Martin's P3D boards, there it is often caused by people installing incompatible add-on flyable aircraft.

I have the MAIW Coningsby installed in P3D v. 5.4 myself, and no issues with that or any other MAIW packages.

So, this is FSX:SE under Windows 11, and a couple of suggestions:

1. Turn UAC off! Especially important with FSX:SE, where you cannot easily move it from its default installation location. UAC tends to be more and more aggressive as Windows progesses through its versions, and you can always turn it back on if necessary.

2. Make sure that it is the FSX Coningsby you installed. There is also a P3D version available, if you have that you will have problems.

3. The usual: make sure your Windows is completely updated... including the "additional Microsoft products" under Advanced options in Update.

Jorgen

[lucame]

Hi folks,
sometime the easiest way is really the best....
Uninstalled FSXSE, UNINSTALLED STEAM !, reinstalled Steam and FSXSE and now my PC is happy again ( and me too).
Thanks again everyone who took his time to help me to find a solution.

Best wishes Lucame

[Firebird]

So it was a Steam issue. Interesting to note. Thanks for the update.