Soulflight

Thanks everyone. But I dont use FG at all, as even with good FPS it feels wobblish. Anyways, DX12 in 2020 runs fine now for me and give me amazing image quality with DLSS4. But for this, I had to reduce texture resolution in 2020 from "ultra" to "high", as DX12 mode eats up my 4060ti's 16GB of VRAM easily on ultra. On high, its -5GB VRAM usage and butter smooth even in the middle of big cities with traffic and addon airports. Someone on youtube also mentioned that DLSS4 is not compatible with DX11.

meanwhile a channel admin on youtube confirmed to me that DLSS 4 is not compatible with DX11. But i managed to get DX12 running fine. My bad i was reluctant to lower texture resolution from "ultra" to "high" before. I see no quality difference so far but -5GB VRAM usage. Remarkable that DX12 on with ultra texture resolution brought even my 16GB VRAM to its knees and caused my system RAM to be used in complex scenery areas. It even caused OOM crashes, hello FSX days. 😁

I activated DLSS4 on my 4060ti and it was all done correctly. The DLSSinfo method shows the latest version being used in MSFS too. But i have a stupid question: does DLSS4 now require using DX12 mode? If yes, thats a shame since DX12 doesnt run as well on my system. In areas with dense scenery and high quality aircraft, it is more laggy and has more stutters. For some reason it seems to utilize more system RAM on my rig, so in the past I prefered DX11. I am not using FG, as I dont like the taering effects, but I like the better image quality that DLSS4 delivers. The problem is that DX11 doesnt seem to work with it. After the installation launching MSFS in DX11 mode crashes it after loading the main menu/map. Any ideas?

Noob question: is it normal that enabling DLSS 4 in 2020 breaks DX11 mode? I am only able to use MSFS in DX12 now. Problem is that DX11 runs much smoother as with DX12 my VRAM fills up too much resulting in stutters in dense areas. I dont want to use FG, I just want to improve image quality with DLSS4.

Btw why do they still not allow this? Afaik this is what makes apps like ASFS basically a collection of improvised workarounds. Previously I thought Asobo didnt want to allow creation of a proper 3rd party weather system for MSFS because it could defeat marketing for MSFS 2024. Whats the reason for being so protective with the weather API? I am still on 2020 myself and i am happy with it. Especially since addon compatbility doesnt seem to be as guarranteed as announced. Minor issues with visuals in 2020 could be improved by mods/3rd party apps. The only reason for me to get 2024 would have been more accurate live weather and cloud types, including realistic TS/CB depiction, similar to the way it was done by ActiveSky on FSX/P3D. I decided to wait for reviews and I am glad to see i was right.

After several hours of gradually removing stuff from the community folder and subsequent testing i found out that it seems to have been caused by a navigraph AIRAC I had installed. Weird enough this causes such a crash but its gone when removed.

Got back from work today and did some checking. Updated nvidia driver the usual clean way without any changes. But I can get into safe mode! This is strange because I deactivated my addons already using the addon manager. But there are some which are installed by their own installers and are still present in the community folder. Is there anything else MSFS safe mode changes when activated, except for not loading addons inside the community folder?

memory issues were not really my suspicion as the system itself is very stable with anything except MSFS. Its just something i read that 0xc000005 points towards memory instability. But I just ran a full memtest, which took 4,5 hours and returned 0 errors, so nope...

I just got back from 2 weeks offline and tried to start MSFS, yesterday it worked fine, i downloaded the recent WU and mandatory update. Now I cannot get to the main menu anymore. Loading finishes and then MSFS crashes without any error. Event log shows this: Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.37.19.0, Zeitstempel: 0x00000000 Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.37.19.0, Zeitstempel: 0x00000000 Ausnahmecode: 0xc0000005 Fehleroffset: 0x0000000000bee81e ID des fehlerhaften Prozesses: 0x0x3120 Startzeit der fehlerhaften Anwendung: 0x0x1DAF4A7B1461F4A Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Berichtskennung: 723bb2d6-1ccb-486d-956d-f02d071da89e Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App I used addon manager already to deactivate all addons, but even plain vanilla MSFS crashes the same way. sfc /scannow also didnt show any corrupted system files. Some threads I found about it online point towards memory timing problems but I didnt change anything recently. I use 2x16GB DDR4-3200 sticks and applied the corresponding preset in my BIOS setup. Other than that I didnt make any changes and didnt OC anything. So nice, you have one day off and you spend it downloading updates and then troubleshooting, fml. 😄

Cope and seethe. I said the symptoms seem to me like there is a memory leak, which, in my case, is most likely caused by SimFX filling up RAM. Since the solution is to not use SimFX at all, I dont see how you come to the conclusion there never was a memory leak either. Unfortunately I didnt do anything else so far anymore. I was away for 2 weeks now and since the recent updates my MSFS isnt launching at all. 😬 I read P42 released updates, so maybe ill give it another try and tell you about it.

Cope and seethe. I said the symptoms seem to me like there is a memory leak, which, in my case, is most likely caused by SimFX filling up RAM. Since the solution is to not use SimFX at all, I dont see how you come to the conclusion there never was a memory leak either. Unfortunately I didnt do anything else so far anymore. I was away for 2 weeks now and since the recent updates my MSFS isnt launching at all. 😬 I read P42 released updates, so maybe ill give it another try and tell you about it. For me it definitely was, as its gone after deactivating simfx. Every system and setup is different however.

Bump. It seems to be somehow related to Deer Lake airport on the island of newfoundland. Whenever i load that airport directly from the main menu or fly near it, MSFS crashes. Now the problem is that it is marked as an addon with the plug icon next to it on the map screen, but I didnt install any addon in this area. Can this be a problem with World Update Canada? Are there ways of tracking down the scenery files the sim loads at specific airports? Disregard, it had to do with the simaddons library. There was an incompatibility with newer FS updates i guess.

In-place upgrade with the most recent ISO solved the issue in the end. All the configuration stuff could be kept. Actually performance improved afterwards. interesting.

Thanks for the hint. Interestingly enough, the option "solve problems using windows update" isnt available on my system. "this option is currently unavailable". So, the only option seems to be a complete reset using an ISO. While it says that data is kept, I am worried in particular for MSFS, attached programs and my settings and key bindings in there, since "apps and settings are removed". So, i really want to save me the time of setting everything up again the way it was before. The last W11 build successfully installed was on april 2024 (build 22631.3447) since then, every cumulative update resulted in the mentioned install error.

Yes just now, no change..... I did some digging, here is the CBS.log section that contains the error. Looks like some file is missing the installer wants to work with: 2024-07-27 01:27:07, Error CSI 0000001e@2024/7/26:23:27:07.305 (F) onecore\base\wcp\sil\ntsystem.cpp(3095): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null) [gle=0x80004005] 2024-07-27 01:27:07, Error CSI 0000001f (F) STATUS_OBJECT_NAME_NOT_FOUND #5785147# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = 0, handle = {provider=NULL, handle=0, name= ("null")}, da = (FILE_GENERIC_READ), oa = @0x8a65cfad20->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[142]'\??\C:\WINDOWS\WinSxS\Manifests\amd64_microsoft-windows-a..p-merged-deployment_31bf3856ad364e35_10.0.22621.2506_none_203e2018ca4459f0.manifest'; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x8a65cfaf08, as = (null), fa = (FILE_ATTRIBUT[gle=0xd0000034] 2024-07-27 01:27:07, Error CSI E_NORMAL), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid) [gle=0xd0000034] 2024-07-27 01:27:07, Error CSI 00000020 (F) STATUS_OBJECT_NAME_NOT_FOUND #5785146# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::OpenFilesystemFile(flags = 0, da = (FILE_GENERIC_READ), fn = [l:139]'\SystemRoot\WinSxS\Manifests\amd64_microsoft-windows-a..p-merged-deployment_31bf3856ad364e35_10.0.22621.2506_none_203e2018ca4459f0.manifest', sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_SYNCHRONOUS_IO_NONALERT|FILE_NON_DIRECTORY_FILE|FILE_OPEN_FOR_BACKUP_INTENT), file[gle=0xd0000034] 2024-07-27 01:27:07, Error CSI = NULL, disp = Invalid) [gle=0xd0000034] 2024-07-27 01:27:07, Error SXS Could not open \SystemRoot\WinSxS\Manifests\amd64_microsoft-windows-a..p-merged-deployment_31bf3856ad364e35_10.0.22621.2506_none_203e2018ca4459f0.manifest: STATUS_OBJECT_NAME_NOT_FOUND 2024-07-27 01:27:07, Error SXS WIL Origination: onecore\base\servicing\turbostack\lib\turbostackutil.cpp(70)\TurboStack.dll!00007FF98443337B: (caller: 00007FF984433721) Exception(1) tid(368) C0000034 Der Objektname wurde nicht gefunden. 2024-07-27 01:27:07, Error CSI 00000021@2024/7/26:23:27:07.305 (F) onecore\base\servicing\turbostack\lib\turbostackutil.cpp(70): Error HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) originated in function (null) expression: (null) [gle=0x80004005] 2024-07-27 01:27:07, Error SXS WIL Origination: onecore\base\servicing\turbostack\lib\package.cpp(11067)\TurboStack.dll!00007FF98449CDF2: (caller: 00007FF984B8C2F3) ReturnNt(1) tid(368) C0000034 Der Objektname wurde nicht gefunden. Msg:[onecore\base\servicing\turbostack\lib\turbostackutil.cpp(70)\TurboStack.dll!00007FF98443337B: (caller: 00007FF984433721) Exception(1) tid(368) C0000034 Der Objektname wurde nicht gefunden. ] 2024-07-27 01:27:07, Error CSI 00000022@2024/7/26:23:27:07.325 (F) onecore\base\servicing\turbostack\lib\package.cpp(11067): Error HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) originated in function (null) expression: (null) [gle=0x80004005] 2024-07-27 01:27:07, Info CBS Exec: Failed to commit stager to stage execution chain. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2024-07-27 01:27:07, Info SXS Perf: File cache FileCount: 1, ByteCount: 0 MB, Hits: 0, Total: 1 2024-07-27 01:27:07, Info CBS CommitPackagesState: Started persisting state of packages 2024-07-27 01:27:07, Info CBS CommitPackagesState: Completed persisting state of packages 2024-07-27 01:27:07, Info CSI 00000023@2024/7/26:23:27:07.345 CSI Transaction @0x24bcdd38060 destroyed 2024-07-27 01:27:07, Info CBS Perf: Stage chain complete. 2024-07-27 01:27:07, Info SXS Removing reference on previously loaded registry hive: \Registry\Machine\COMPONENTS 2024-07-27 01:27:07, Info SXS Removing reference on previously loaded registry hive: \Registry\Machine\SCHEMA 2024-07-27 01:27:07, Info CSI 00000024 Direct SIL provider: Number of files opened: 9. 2024-07-27 01:27:07, Info CBS Failed to stage execution chain. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2024-07-27 01:27:07, Error CBS Failed to process single phase execution. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2024-07-27 01:27:07, Info CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.3958.1.18, status: 0x80070002, failure source: Stage, start state: Resolved, target state: Installed, client id: UpdateAgentLCU 2024-07-27 01:27:07, Info CBS Not able to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2024-07-27 01:27:07, Info CBS Added C:\WINDOWS\Logs\CBS\CBS.log to WER report. 2024-07-27 01:27:07, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20240726232155.cab to WER report. 2024-07-27 01:27:07, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20240726223809.cab to WER report. 2024-07-27 01:27:07, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20240726222410.cab to WER report. 2024-07-27 01:27:07, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20240726222115.cab to WER report. 2024-07-27 01:27:07, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20240726214859.cab to WER report. 2024-07-27 01:27:07, Info CBS Not able to add %windir%\winsxs\pending.xml to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2024-07-27 01:27:07, Info CBS Not able to add %windir%\winsxs\pending.xml.bad to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2024-07-27 01:27:07, Info CBS Reboot mark cleared 2024-07-27 01:27:07, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications 2024-07-27 01:27:07, Info CBS Winlogon: Deregistering for CreateSession notifications 2024-07-27 01:27:07, Info CBS FinalCommitPackagesState: Started persisting state of packages 2024-07-27 01:27:07, Info CBS Reporting package change for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.3958.1.18, current: Resolved, pending: Default, start: Resolved, applicable: Installed, target: Installed, limit: Installed, status: 0x0, failure source: Stage, reboot required: False, client id: UpdateAgentLCU, initiated offline: False, execution sequence: 1988, first merged sequence: 1988, reboot reason: REBOOT_NOT_REQUIRED, RM App session: -1, RM App name: N/A, FileName in use: N/A, release type: Update, OC operation: False, download source: 0, download time (secs): 4294967295, download status: 0x0 (S_OK), Express download: False, Download Size: 0 Used lower priority: False Priority changes: 0 2024-07-27 01:27:07, Info CBS Reporting package change completion for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.3958.1.18, current: Resolved, original: Resolved, target: Installed, status: 0x80070002, failure source: Stage, failure details: "(null)", client id: UpdateAgentLCU, initiated offline: False, execution sequence: 1988, first merged sequence: 1988, pending decision: InteractiveInstallFailed, primitive execution context: Interactive 2024-07-27 01:27:07, Info CBS Stage time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND] 2024-07-27 01:27:07, Info CBS Execute time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND] 2024-07-27 01:27:07, Info CBS FinalCommitPackagesState: Completed persisting state of packages 2024-07-27 01:27:07, Info CBS Enabling LKG boot option 2024-07-27 01:27:07, Info CBS Exec: End: nested restore point - complete. 2024-07-27 01:27:07, Info CBS Exec: Automatic corruption repair has already been attempted today, skip it. 2024-07-27 01:27:07, Info CBS Exec: Processing complete. Session: 31121331_573278810, Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.3958.1.18, Identifier: KB5040527 [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2024-07-27 01:27:08, Error CBS Failed to perform operation. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2024-07-27 01:27:08, Info CBS Session: 31121331_573278810 finalized. Reboot required: no [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2024-07-27 01:27:08, Info CBS Failed finalizing session [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2024-07-27 01:27:08, Info CBS Failed to call Process on TiWorker session [HRESULT = 0x80070002] 2024-07-27 01:27:08, Info CBS Deleting directory: \\?\C:\WINDOWS\CbsTemp\31121331_573278810\ 2024-07-27 01:27:08, Info CBS Moving directory from \\?\C:\WINDOWS\CbsTemp\31121331_573278810\ to \\?\C:\WINDOWS\CbsTemp\{35322E5E-EA44-47FD-88AD-9DE828EEB3E8} 2024-07-27 01:27:08, Info CBS Deletion of: \\?\C:\WINDOWS\CbsTemp\{35322E5E-EA44-47FD-88AD-9DE828EEB3E8} successful 2024-07-27 01:29:09, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP 2024-07-27 01:29:09, Info CBS TiWorker signaled for shutdown, going to exit. 2024-07-27 01:29:09, Info CBS Deleting the contents of directory: \\?\C:\WINDOWS\CbsTemp 2024-07-27 01:29:09, Info CBS Deletion of: \\?\C:\WINDOWS\CbsTemp successful 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: ExecutionEngineFinalize 2024-07-27 01:29:09, Info CBS Execution Engine Finalize 2024-07-27 01:29:09, Info CBS Execution Engine Finalize 2024-07-27 01:29:09, Info CBS Execution Engine Finalize 2024-07-27 01:29:09, Info CBS Execution Engine Finalize 2024-07-27 01:29:09, Info CBS Lock: Lock removed: TiWorkerClassFactory, level: 30, total lock:3 2024-07-27 01:29:09, Info CBS Lock: Lock removed: CCbsWorker, level: 5, total lock:2 2024-07-27 01:29:09, Info CBS Ending the TiWorker main loop. 2024-07-27 01:29:09, Info CBS Starting TiWorker finalization. 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: ExecutionEngineFinalize 2024-07-27 01:29:09, Info CBS CBS Engine already deactivated 2024-07-27 01:29:09, Info CBS CBS Engine already deactivated 2024-07-27 01:29:09, Info CBS CBS Engine already deactivated 2024-07-27 01:29:09, Info CBS CBS Engine already deactivated 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: PackageTrackerFinalize 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: CoreResourcesUnload 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: SessionManagerFinalize 2024-07-27 01:29:09, Info CBS Lock: Lock removed: CSIInventoryCriticalSection, level: 64, total lock:10 2024-07-27 01:29:09, Info CBS Lock: Lock removed: CCbsSessionManager, level: 11, total lock:9 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: CapabilityManagerFinalize 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: WcpUnload 2024-07-27 01:29:09, Info CSI 00000025 Direct SIL provider: Number of files opened: 26. 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: DrupUnload 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: CfgMgr32Unload 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: DpxUnload 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: SrUnload 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: TurboStackUnload 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: TurboContainerUnload 2024-07-27 01:29:09, Info CBS TurboContainer unload Successful 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: CbsEsdUnload 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: CbsOneSettingsFinalize 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: CbsEventUnregister 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: AppContainerUnload 2024-07-27 01:29:09, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end. 2024-07-27 01:29:09, Info CBS Ending TiWorker finalization. 2024-07-27 01:29:09, Info CBS Ending the TrustedInstaller main loop. 2024-07-27 01:29:09, Info CBS Starting TrustedInstaller finalization. 2024-07-27 01:29:09, Info CBS Winlogon: Stopping notify server 2024-07-27 01:29:09, Info CBS Winlogon: Unloading SysNotify DLL 2024-07-27 01:29:09, Info CBS Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6