Foggy

I hope someone else out there has encountered this problem and was able to fix it. This is the log file

Faulting application name: Flight Simulator2024.exe, version: 1.6.34.0, time stamp: 0x00000000

Faulting module name: libcef.dll, version: 109.1.16.0, time stamp: 0x6368965c

Exception code: 0x80000003

Fault offset: 0x000000000170ce01

Faulting process id: 0x3AB4

Faulting application start time: 0x1DCB19F023E5FAB

Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.6.34.0_x64_8wekyb3d8bbwe\FlightSimulator2024.exe

Faulting module path: C:\FlightSimLabs2024\fsl-common\fslabs\cef_binary/release\libcef.dll

Report Id: 75839012-0860-42e4-bedc-22432683bf89

Faulting package full name: Microsoft.Limitless_1.6.34.0 x64_8wekyb3d8bbwe

Faulting package-relative application ID: App

I had a really good copy of FSX running on my previous machine. I was able to run on medium/high settings with addons airports that I was flying to activated no problem. However, the hardware reached the end of its life and I now have new hardware.

I have followed the avsim Install bible and have copied across the root folder from my old hardware to my new hardware and I also copied across the scenery.cfg. 

I tested the sim by loading in Edinburgh and it worked no problem. However when I try to load the sim in Miami or Tampa, I run into a OOM error at about 80% 

The new hardware is more capable then the previous hardware and the sim files are the same on both hardware. I'm stumped as to what could be causing this. Does anyone have any idea what could be causing this issues specifically in florida or the new hardware even though it works fine on the old hardware? 

Ive done half a dozen flights on the same routes, same scenery and same aircraft with LOD on 8.5 without any problems at all for many years.

Now, on my new W11 computer Im getting ooms when I never did before. Im using DX10 fixer the same way Ive always used it and im still getting omms now. HIGH MEM FIX is on.... Ive tried FSX and FSXsteam...I even tried a different card and drivers. What has changed?

I have just done a fresh reinstall of Prepar3D v3.2 (lastest version, Academic) on Windows 10. After installing the FSDreamteam KJFK, I got this error on startup related to the dll they use for couatl/addon manager : http://prntscr.com/apvs3t

It has been coming up ever since. I uninstalled the FSDT product and everything worked fine afterwards. How can I fix this error? I cannot even get in to the simulator with this. It seems to me that many of my problems are caused by this bglmanx/addon manager stuff...

I have the latest version of FSUIPC installed.

Thank you!

I'm suffering from a reproducable CTD that's always occuring south of EDDV airport. It happens at all times of the day, with every aircraft and even with AI traffic and AI ships set to 0. Event viewer says KERNELBASE.dll is the culprit.

What could cause that?

Kind regards
Michael

Ever since the most recent SU16 update, I am experiencing random CTD's when flying in certain regions. For example, I can fly all along the eastern and central US and Caribbean with no CTD issues. However, when flying in some parts of the western US, especially in mountainous areas, there are random CTD issues. Sometimes I can do a similar flight in the same area, and the sim is fine; other times, random CTD with no rhyme or reason. Also experiencing random CTDs when flying in the vicinity of the northern part of South America. For example, I was doing a flight earlier between MKJS (Sangster airport, Jamaica) and TNCA (Aruba), and about 90nm out of Aruba, CTD. I've done the same flight, with no issues, so it seems it's just an unexplained random CTD event. The most common faulting module (per the event viewer) is the CoherentGTCore.dll for all the recent CTD events (post SU16 update). I've read that others are also experiencing CTD issues (post SU16 update). Does anyone know if Asobo is planning on releasing a patch at some point to potentially mitigate these CTD events? Or is there some other workaround that I can possibly try in the meantime? Any input will be appreciated.

Jermaine

But this is not the issue i am trying to get solved, its just the reason why I want to actually switch back to DX11 but I cant. MSFS in DX11 mode crashes after the initial loading when usually the main menu should be shown but instead i am getting a CTD. I dont know if this issue is related to DLSS4 or not. For safety I aleady switched back to default in the DLSS swapper utility with no change.
Here is the corresponding error log from windows:

 

Fehlerhafter Anwendungsname: FlightSimulator.exe, Version: 1.39.9.0, Zeitstempel: 0x00000000
Fehlerhafter Modulname: nvngx_dlssg.dll_unloaded, Version: 310.2.1.0, Zeitstempel: 0x67d089b2
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000008976a0
Fehlerhafte Prozess-ID: 0x184C
Fehlerhafte Anwendungsstartzeit: 0x1DC25BFC6761C99
Fehlerhafter Anwendungspfad: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Fehlerhafter Modulpfad: nvngx_dlssg.dll
Berichts-ID: 1b6bf1d2-831c-4d6e-adee-5d331708647d
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe
Fehlerhafte paketbezogene Anwendungs-ID: App

It seems to be an nvidia driver issue. I found some reports of similar issues with latest nvidia drivers and nvidia releasing a hotfix, but on my system the problem still persists with the latest nvidia drivers 581.29.
I already dumped the nvidia app from my system as some say this could cause issues and there is no benefit of having it if you use nvidia inspector. 
GPU is a 4060ti with 16GB VRAM on windows 11.

Has anyone dug into that issue with more success than I did?

UPDATE: it seems that the crash doesnt happen when Hardware Accelerated GPU Scheduling is turned off in windows settings. However, DLSS4 definitely doesnt work in DX11, since it crashes as soon as you try to load a flight. DX11 with TAA works, however.
 

I have this problem with most of the call out files placed in the main sound folder. I must be placing the sound files incorrectly. Any help would be appreciated.  Thanks in advance.

I'll check this forum for any similar post while waiting for any member responses.

I can find a lot of those issues for MSFS 2020, but I've got one for MSFS 2024:

After it has worked with hardly any flaws for half a year, MSFS 2024 suddenly started to get CTDs when I was at bigger airports. After some of them, a DXGI ERROR_DEVICE_HUNG (0x887a0006) error message came up. Some people said the NVIDIA app caused this problem. So I uninstalled it. Furthermore, I did what was shown in the video below. At first, it seemed solved. Then the inibuilds A330 ran completely crazy. So, I tried to download it (instead of streaming). After that, it worked normally for a single time. And then the whole sim ALWAYS crashes as soon as the splash screen appears for a few seconds. No chance to even get to any menu or settings page within the sim.

I deleted the whole Community folder. Again, the first time it worked. And since the second time, again the same CTDs. Driver of the graphic card (RTX 4070 ti super) is current. I did exactly nothing exept loading the latest mandatory update of the sim. But the described problems started before that. Very frustrating. I can's touch the rolling cache, nor any graphic settings in the sim. And I have no idea, where the problems are coming from. First I thought, it had to do with Beyond ATC, the FSLTL AI traffic models, TrackIR or APL. But it also happens with ALL of them deactivated.

The only suspicious thing so far was, that the WASM folders are not where they should be and are very incomplete.

I feared it would be a hardware issue. But MSFS 2020 runs smooth and stable with quite some complex addons installed. And anyways, everything else on my system is running stable, too. Have you got any idea, where to start troubleshooting?

My system: Intel Core i7 9700K @4.4 GHz, ASUS Prime Z390-P, 32 GB DDR4 RAM, Nvidia RTX 4070 ti Super, BeQuiet 850W PSU.

Thanks in advance.

Best regards,

Dominik

Ive tried to narrow down what’s causing this CTD but I still can’t figure it out. I ran ProcMon and it was coming up with multiple Texture.CAB files missing from folders that don’t even have a Texture folder, most notably Scenery/SAME/Scenery. Does anyone have any suggestions?

I'm having a problem with the Aerosoft CRJ v2 Pro, with my P3Dv5.1. I've posted a ticket to Aerosoft support and several requests, but I haven't received a response. (P3D customers are probably no longer interested in them.) When I select the CRJ, P3Dv5.1 has been crashing for some time. Before, there was no problem. And no problem with other aircraft. I've uninstalled and reinstalled, but nothing works. Since I don't have any help from Aerosoft,

I'm trying to understand. One thing that puzzles me is that in the Aerosoft CRJ Pro Base Panel, there is no config panel, only a DLL called ASCRJ Pro.5.dll.

Can't find the ASCRJ Pro 5!PFDC gauge?

 In all versions of CRJ, for the "panel config" There is: gauge00=../../Aerosoft CRJ Pro Base\panel\ASCRJ Pro 5!PFDC, 0, 0, 286, 338,????? But as mentioned above, in Aerosoft CRJ Pro Base\panel\ there is no ASCRJ Pro 5!PFDC, just a DLL.

 It's a bit confusing, but if anyone has any ideas, I'm all ears. Thanks in advance.

Vidéo: https://youtu.be/4HtACIEDfGM

Thanks. I'm in a bind. 

I've had several ctd's lately using FSX SE. One advice I got is to minimize switching to spot views. That worked for a while, but the ctd's still hapened.

I have no idea how to open the error file myself or how to attach it to this post.  It's an MDMP type file. Opening it with notepad just shows gibberish.

Please assist me.

Eytan Ornstein

Rodger

Any tips? I dont want to start over because its very slow

(Reposted in CTD cause i accidently posted it in MSFS)

I have installed the swim brief option into MSFS 2020 and changed it from French to English (otherwise, the swim brief does not work).

Now, when I launch MSFS 2020, the game always crashes, and I get the message, "Your graphics device has encountered a problem, and the application will exit."

Any idea?

Ty, for your help.

J

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3
Faulting module name: g3d.dll, version: 10.0.61472.0, time stamp: 0x475e180c
Exception code: 0x80000001
Fault offset: 0x000b50df
Faulting process id: 0x69c
Faulting application start time: 0x01da69e787740f9f
Faulting application path: D:\Program Files (x86)\fsx.exe
Faulting module path: D:\Program Files (x86)\g3d.dll
Report Id: 59d802a9-2da5-40f5-8db1-170782208ea5
Faulting package full name: 
Faulting package-relative application ID: 

First thing I tried was changing "scenery.cfg" to "scenery.off" to let it rebuild. That worked for one cycle, but the next time I went to start up, back to crashes again. So I looked at the log again, and the error above was followed imediately by this:

Faulting application name: couatl.exe, version: 3.2.0.5318, time stamp: 0x6553c66e
Faulting module name: couatl.exe, version: 3.2.0.5318, time stamp: 0x6553c66e
Exception code: 0xc0000005
Fault offset: 0x0005aa89
Faulting process id: 0x2ec4
Faulting application start time: 0x01da69e794417b61
Faulting application path: D:\Program Files (x86)\Addon Manager\couatl\couatl.exe
Faulting module path: D:\Program Files (x86)\Addon Manager\couatl\couatl.exe
Report Id: b6ffcd1d-d39b-4f88-a663-889bc480b771
Faulting package full name: 
Faulting package-relative application ID:

So next I went to my FSDT updater and ran it. This would fix the problem again for only one cycle, and the next startup crashes again. So I repeated this step with the same result two or three more times. I figure something with GSX is corrupted so I uninstalled it with the intent to re-install. Again, this fixed the problem for one cycle, and now I'm back to the crashes again with these same two messages even though I haven't re-installed GSX. I'm not sure where to go from here.

-Brad... 

I have issue of CTD without any error in the windows event viewer.  So far I have asked in the P3D forum too, but to my regret I could not have solution yet.

My sim is V6.1.11 on win11 23H2 build 22631.4249. i7-12700k 4.9GHz, 16GB RAM, RTX3080 10GB.

Recently I have upgraded CPU and mother board with uninstalling P3D, deletegeneratedfile.exe, delete all folders and install it by activating again.

I am not sure the CTD started at that time, but am aware of it after the upgrade.  Because, since add-ons for V6 are very rare I usually have made flights with VFR that means low altitude flight.

Anyway, my CTD happens at indicated altitude of climbing 2700ft under fair weather condition every time without any error in the windows event viewer. Aircraft is default commander 114.

CTD happens in the different area but same altitude of 2700ft, I have checked at RJTF(Japan) and KLGA(USA).

CTD does not happen with clear weather(no cloud) even above 2700ft.

That is to say whenever the clouds are in the sky, CTD happens at 2700ft.

I have V5.4 too with my favorite add-ons, so that I have installed all of them into V6 like Activesky, ASCA, Spad.next, FSUIPC, Chaseplane, SODE, Ultimate traffic live and Reality GTN750.

To eliminate the doubt about such add-ons, I have tested uninstall and install V6 again without any add-ons except Spad.next and Chaseplane, otherwise I could not control the plane.

The result is same as before, CTD happens at 2700ft.   (V5.4 is very stable with the same configuration)

Having had my CTD with cloud layer, I have look around the something related figures in the setting, then I found the altitude of 5741ft that is lower layer of cumulus starting in fair weather condition.  The altitude of 2700ft is 3000ft below.  In my V6, lower layer of cumulus is from 5741ft to 12455ft, 2nd layer is of cirrus starting from 39370ft to 40190ft.

For my confirmation I have changed the lower altitude from 5741ft to 6741ft then CTD happens at 3700ft instead.  Set altitude more high CTD altitude increase more high.  And more, set cloud type to cirrus, CTD happens.

Having had suggestion at P3D forum, I have checked at hight altitude airport KDEN displayed altitude is 5430ft 34R. CTD happened at sim start up.  On the other I could make complete flight with clear weather setting. Aircraft is default commander 114.
For my interest, after landing on the same runway 34R, change the weather to fair on world tab, CTD happened immediately.

When Activesky has been installed, CTD happens at the startup of sim if it is cloudy day, but I could make flight and climb up until 3000ft below of cloud layer under fine day and lower cloud altitude is higher condition. 

Thinking my phenomena above, I think something like layer or boarder, or just something must be that altitude that is invisible when the clouds in the sky.
Does anybody advise me how do I go for researching my issue.

Thank you in advance.

Shibekora

I recently had to reinstall FSX on my laptop due to getting a BSOD error and having to reinstall windows. I am now getting A CTD when right clicking and I received the below on my event viewer:

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: API.DLL, version: 10.0.62615.0, time stamp: 0x559f9ab5
Exception code: 0xc0000005
Fault offset: 0x00100043
Faulting process ID: 0x33e8
Faulting application start time: 0x01da1024bf82ebb2
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\FSX\API.DLL
Report ID: a397b0d3-77a5-43eb-b3a1-8a5732aea875
Faulting package full name: 
Faulting package-relative application ID: 

Any help would be greatly appreciated 🙂