sleighzy

You have a large number of mods, some with errors. Can you remove these and run the repair again. Can you additionally rename Saved Games\DCS to Saved Games\DCS.old and start DCS again. Whilst this is not guaranteed to resolve the issue at least it rules out any issues with potential corruption in Saved Games\DCS.
Looks like you're also running DCS from the bin-mt folder. Can you instead use the one in the bin folder. Both executables are identical and use multithreading, the bin-mt folder will be removed in the future.

Looks like there's a 4 minute gap here around terrain and completed loading of the F15C. You running on a fast internal SSD?
2025-10-03 17:27:34.912 INFO Dispatcher (Main): load terrain done 2025-10-03 17:27:34.913 INFO LUA-TERRAIN (Main): Init done 2025-10-03 17:27:34.913 INFO INTER (Main): ITerrainGraphicsEntryPoint::close() 2025-10-03 17:27:34.913 INFO INTER (Main): ITerrainGraphicsEntryPoint::createTerrainGraphics() 2025-10-03 17:31:36.419 INFO EDCORE (24528): Loaded J:/DCS World/Mods/aircraft/F-15C/bin/F15.dll 2025-10-03 17:31:36.419 INFO WorldPlugIns (24528): loading "F-15C": 256.909 Ran your DCS log through the DCS log analyzer which highlighted a few things.
You have heaps of mods. Can you try removing those and delete your Saved Games\DCS\fxo and metashaders2 caches. You can put them back afterwards, but lets at least rule out any issues there. You have core parking enabled. You can use the ParkControl software to disable core parking for your power management profiles. Drop your preload radius down to 60000. It's currently 100000, this will save some of the load time along with reducing VRAM and RAM usage. If you haven't already then you can also add a folder exclusion to your anti-virus software, e.g. Windows Defender, for the entire DCS installation folder, and then restart your PC. This may help if it's scanning the DLLs while loading.

Not sure what those sources are, may be from years ago, but definitely do not run as admin. It can cause issues reading/writing files, and is frequently the cause of mass stuttering and pauses when used with Winwing MFDs. 
Yeah I think years ago it was spread that this was the way to run DCS as it gave higher priority / power management to the game thread and helped with performance. Don’t know if that was just bs but it isn’t needed and shouldn’t be done now. 

Delete your C:\Users\username\Saved Games\DCS\launcher.sqlite3 file and then start DCS again. Failing that rename your Saved Games\DCS folder to DCS.old (so you can copy back your bindings from Config\Input). Deleting the launcher.sqlite3 should fix it though.

Try deleting the Saved Games\DCS\launcher.sqlite3 file first. If it still errors then rename Saved Games\DCS to DCS.old. Rename not delete so that you can copy back your bindings from the Config\Input folder. 

Please attach your DCS log for review.
Note that the F-10 Map is a well known issue in VR. This can largely be due to VRAM overflow....and you only have an 8Gb 3060Ti (and low specs in general for a larger MP server).
Current workarounds (aside from lowering textures to reduce VRAM usage...which may still not help):
Alt-tab out of the game, and then alt-tab back in again after a few seconds. This can help clear VRAM. Ensure you center and zoom back in on your plane on the map prior to jumping back into the cockpit again Use OpenKneeboard along with the DCW Web Editor Moving Map (as a web dashboard tab). This will display a dynamic map with a lot of the F-10 map functionality. This can help with not even needing to use the F-10 map, depending on your usage.

Common error in the log being experienced by other users as well. Renaming Saved Games\DCS to Saved Games\DCS.bak as mentioned above will achieve the same result as just renaming Saved Games\DCS\MissionEditor to MissionEditor.old which is the current workaround for this error.
2025-09-23 07:07:40.857 ALERT LUACOMMON (Main): Error: GUI Error: [string "./MissionEditor/modules/me_news.lua"]:146: bad argument #2 to 'date' (number expected, got string) GUI debug.traceback: stack traceback: [C]: ? [C]: in function 'date' [string "./MissionEditor/modules/me_news.lua"]:146: in function 'showNews' [string "./MissionEditor/modules/me_news.lua"]:259: in function 'funCallBack' [string "./MissionEditor/modules/me_waitDsbweb.lua"]:90: in function 'updater' [string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40> I believe directly deleting the `news.lua` file in that folder has also solved for folk (which would also be the same as renaming the MissionEditor folder). I've tested this myself and that file gets recreated on next startup so seems to be safe.

Also confirm that you aren't running DCS as administrator, can check under the shortcut for the exe as well under the Shortcut and Compatibility tab and make sure that Run as administrator isn't ticked. This was a known issue a while ago with WinWing MFDs.
If you have modified the Windows UAC settings then this can also lead to things being run as administrator.
Looking for another reference as I believe there is also another app that DCS can be launched from that can cause this issue as well.

Can you also try renaming (DCS will create a new one) your Saved Games\DCS\launcher.sqlite3 file and starting DCS again. 

If you are using DLSS, or decide to try it, then use the DCS config for controlling the preset, and the ability to not have this applied to MFDs.
Add the below line to the C:\Users\username\Saved Games\DCS\Config\autoexec.cfg file, create it if it doesn't already exist.
DLSS_Preset = 'K' The additional optional line below can also be added to that file. This will bypass the HUD and MFD for DLSS, means greater control if you'd like to use DLSS4 for the game, but hate ghosting on the MFDs and don't want to apply to those. Best of both worlds.
HUD_MFD_after_DLSS = true Check your Meta app as well to see what you've set the resolution slider to, and increase that as needed, e.g. 1.3, 1.5 etc. The fact that can hardly see the MFDs sounds like your settings haven't been tuned / pumped up.

Does this work fine in other missions, multiplayer, etc. it's just this one mission?
If you haven't already then I'd also try the standard steps:
running a slow repair of the game and delete your Saved Games\DCS\fxo and metashaders2 folders. Next, delete %LOCALAPPDATA%\TEMP\DCS and try again., Next try renaming Saved Games\DCS to DCS.old and try again. Rename so you can copy your bindings back from the Config\Input folder. The DxDiag report indicates a number of failures that appear to be GPU related (see below). Could be corrupt drivers (try DDU'ing the existing drivers and then reinstall, you could also try version 566.36), hardware, or power issue.
Windows Error Reporting (WER)
Kernel Events
The following kernel-events have been detected:
VIDEO_ENGINE_TIMEOUT_DETECTED,FAULTY_HARDWARE_CORRUPTED_PAGE Remove any overclocking (including XMP). Run SFC and DISM to check your Windows. Check for any updates of your BIOS or chipset drivers. For the SFC and DISM commands open a command prompt as administrator, run the below two commands separately and restart your PC.
dism /online /cleanup-image /restorehealth sfc /scannow  
Of interest as well in this stack trace is something I've seen in a few other crash reports now. I'll see if I can locate the others as may need investigation by ED if this is becoming a common theme.
2025-06-30 04:54:49.270 INFO EDCORE (Main): # -------------- 20250630-045449 -------------- 2025-06-30 04:54:49.271 INFO EDCORE (Main): DCS/2.9.17.11733 (x86_64; MT; Windows NT 10.0.26100) 2025-06-30 04:54:49.272 INFO EDCORE (Main): C:\Program Files\DCS World\bin-mt\DCS.exe 2025-06-30 04:54:49.273 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff6ad40f554 00:00000000 2025-06-30 04:54:49.274 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Program Files\DCS World\bin-mt;', symOptions: 532, UserName: 'Nick' 2025-06-30 04:54:49.275 INFO EDCORE (Main): OS-Version: 10.0.26100 () 0x300-0x1 2025-06-30 04:54:49.276 INFO EDCORE (Main): 0x000000000073f554 (DCS): SW + 0x127434 2025-06-30 04:54:49.277 INFO EDCORE (Main): 0x0000000000797197 (DCS): SW + 0x17F077 2025-06-30 04:54:49.278 INFO EDCORE (Main): 0x000000000071778f (DCS): SW + 0xFF66F 2025-06-30 04:54:49.279 INFO EDCORE (Main): 0x000000000000461b (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x3EB 2025-06-30 04:54:49.279 INFO EDCORE (Main): 0x0000000000004c42 (World): wSimCalendar::DoActionsUntil + 0x262 Some errors in the DCS log with audio devices failing to load as well.
Some additional tuning tips from the DCS log analyzer:
Set Preload Radius to max. 60000. (yours is currently set to 100000 so will be loading potentially redundant data, and you only have 8Gb VRAM and 32Gb RAM). Decrease Terrain Textures. Set Clouds to High. Enable Full Screen mode. Set Water to Low. Latest log shows you're still running DCS from bin-mt vs. bin.

Yes, I would make the core parking changes. As to recent changes, Windows 11 has better support for hybrid P/E cores and will identify which is which. Based on other forum threads and Discord channel comments DCS now makes better decisions around which to use for what. For example, allocating I/O to E cores so that those operations aren't being performed on your Performance (P) cores.
Note: This may not solve your issue, but will be in a good state and filter this out going forward for any other logs or ongoing investigation.

What’s the actual user experience? For example, DCS just closes unexpectedly and there is no message stating that an error occurred and would you like to report or save error information?
There is no crash in that log so is possibly Windows killing the process for some reason. Can you run the Windows DxDiag tool, save the report, and attach that here as well. Check Event Viewer like @BJ55 said, this may provide detailed information. The DxDiag report contains information on the last 10 system issues (crashes).
Check also if you have any recent dcs.log-<timestamp>.zip files and attach those as well. Note, these will be created from a crash and not the process being killed. 

Tried renaming your Saved Games\DCS folder to Saved Games\DCS.old so that DCS will create a new one on startup? You can get your bindings back from the Config\Input folder in the backed up one afterwards. The Saved Games folder is not touched during a repair. The error trace points towards to the SQLite database, of which there is one in Saved Games\DCS for the launcher. Try the rename if you haven't already and see what happens.

@nxrvb You have a dxgi.dll file in your DCS\bin directory. I know of only two reasons why this would be there, e.g. ReShade or DLSSTweaks. Remove that and try again, this is part of the stack trace in your crash. Running a slow repair of the game, including selecting the Remove Files option should have removed it.
2025-05-25 18:28:53.893 INFO EDCORE (2324): DCS/2.9.16.10523 (x86_64; MT; Windows NT 10.0.19045) 2025-05-25 18:28:53.896 INFO EDCORE (2324): C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9d15b9aa9e1c885b\nvcuda64.dll 2025-05-25 18:28:53.897 INFO EDCORE (2324): # C0000005 ACCESS_VIOLATION at 00007fffc0e5c8a0 00:00000000 2025-05-25 18:28:53.899 INFO EDCORE (2324): SymInit: Symbol-SearchPath: 'G:\DCS World OpenBeta\bin;', symOptions: 532, UserName: 'Nicki Desktop' 2025-05-25 18:28:53.900 INFO EDCORE (2324): OS-Version: 10.0.19045 () 0x100-0x1 2025-05-25 18:28:53.903 INFO EDCORE (2324): 0x00000000004bc8a0 (nvcuda64): cuProfilerStop + 0x2449A0 2025-05-25 18:28:53.904 INFO EDCORE (2324): 0x00000000005b376a (nvcuda64): cuProfilerStop + 0x33B86A 2025-05-25 18:28:53.904 INFO EDCORE (2324): 0x00000200af353368 ((module-name not available)): (function-name not available) + 0x0 2025-05-25 18:28:53.904 INFO EDCORE (2324): 0x000000000002e7cb (dxgi): NVSDK_NGX_VULKAN_Init_ProjectID + 0x143B 2025-05-25 18:28:53.904 INFO EDCORE (2324): 0x000000000005443d (nvngx_dlss): NVSDK_NGX_DirectSR_Query + 0x18BBD 2025-05-25 18:28:53.904 INFO EDCORE (2324): 0x0000000000044efb (nvngx_dlss): NVSDK_NGX_DirectSR_Query + 0x967B 2025-05-25 18:28:53.905 INFO EDCORE (2324): 0x0000000000037f94 (nvngx_dlss): NVSDK_NGX_D3D11_EvaluateFeature + 0x124 2025-05-25 18:28:53.905 INFO EDCORE (2324): 0x000000000005b98d (_nvngx): NVSDK_NGX_D3D11_GetFeatureRequirements + 0x108D 2025-05-25 18:28:53.905 INFO EDCORE (2324): 0x000000000005a8ee (_nvngx): NVSDK_NGX_D3D11_EvaluateFeature + 0xE  
On a side-note your preload radius is set to 5300. You could bump that up to 60000 if you wanted to, would be fine with your VRAM/RAM. This can help performance, with the game needing to do fewer loads of resources (reduce disk IO) as it will cache more up front.

EDIT: See my last point I added re: the dxgi.dll in the bin-mt dir, I only just spotted that. Remove it (which the repair with remove files should do anyway, but do it yourself first to ensure it's not conflicting with the latest DLSS changes).
 
The DCS log analyzer shows this for your crashes:
Your DCS has crashed
The crash occurred inside VCRUNTIME140.dll.
Try a slow repair of the game, selecting the option to remove files. Delete Saved Games\DCS.openbeta\fxo and metashaders2 and try again., Next, delete %LOCALAPPDATA%\TEMP\DCS.openbeta and try again., Next, try renaming Saved Games\DCS.openbeta to DCS.old and try again. The VCRUNTIME140.dll issue is also mentioned below in the DxDiag report. I'd recommend downloading and installing/repairing your Windows C++ distributables. You want the vc_redist.x64 version from here.  Latest supported Visual C++ Redistributable downloads | Microsoft Learn
Note that this is not a gaurantee, but just to rule it out.
 
From the DxDiag report in that crash zip. Notice also the reference to VCRUNTIME again.
Windows Error Reporting (WER)
Application Errors
DCS.exe: was hung for 60.78s and killed, was hung for 35.79s and killed, was hung and killed, c0000005 (VCRUNTIME140.dll)
Microsoft Update / Store issues
Make sure you have enough free disk space., Run SFC and DISM to check your Windows., Run wsreset.exe to reset the Microsoft Store cache, .- Run the Windows Troubleshooter and select Windows Update.  
For the SFC and DISM commands you want to open a command prompt as administrator and run the below two commands separately, then restart your PC.
dism /online /cleanup-image /restorehealth sfc /scannow  
Additional items from the log analyzer:
Disable game mode Disable Hardware Accelerated GPU scheduling Disable Core Isolation You have another copy of the dxgi.dll in your bin-mt directory. I know of only two reasons for this. Remove it and see what happens as well.
You should also run DCS from the bin directory and not the bin directory as bin-mt will be removed in the future. Both bin and bin-mt are multithreaded now.

Your config is corrupt. Rename your Saved Games\DCS\Config\options.lua to options.lua.old and then restart DCS. It should regenerate new config again, you’ll need to reapply your graphics settings etc afterwards (it won’t lose your control bindings) 
You also have errors in the logs for it trying to start in VR and not finding an OpenXR runtime. In those cases it will just open in 2D. Can resolve that later if you do want to use VR. 

I dropped your log file into the DCS log analyzer which reported at least one item which aligns with your log file.
Update-Server unavailable
Make sure your Internet connection is available. Wait some minutes and try again. The log file shows internet auth issues attempting to contact the server.
2025-04-29 18:47:22.109 ERROR SECURITYCONTROL (20596): Auth data has expired. 2025-04-29 18:47:22.110 ERROR ASYNCNET (20596): Getting auth data failed becase server returned invalid reply. 2025-04-29 18:47:22.562 ERROR APP (Main): Failed to get authorization data. Error code is: 500 2025-04-29 18:47:22.562 INFO APP (Main): Loading cached Steam auth data... 2025-04-29 18:47:22.564 INFO APP (Main): Nope 2025-04-29 18:47:23.951 ERROR APP (Main): Failed to get authorization data. Error code is: 500 2025-04-29 18:47:23.952 INFO APP (Main): Loading cached Steam auth data... 2025-04-29 18:47:23.954 INFO APP (Main): Nope The crash appears to be it attempting to write (unpack) files.
2025-04-29 18:48:01.169 ERROR EDCORE (Main): [C:\Users\igort\AppData\Local\Temp\DCS\Mission/l10n/RU/TF-51_FOT_ru{066DE39B-A9A7-4679-B36B-5785C8AFBDA9}.png] CreateFile(REWRITE): Access is denied. 2025-04-29 18:48:01.169 ERROR EDCORE (Main): Can't open file 'C:\Users\igort\AppData\Local\Temp\DCS\Mission/l10n/RU/TF-51_FOT_ru{066DE39B-A9A7-4679-B36B-5785C8AFBDA9}.png' from real path fs. 2025-04-29 18:48:01.169 ALERT LUACOMMON (Main): Error: GUI Error: [string "./Scripts/dictionary.lua"]:579: VFS_open_write: Can't create file C:\Users\igort\AppData\Local\Temp\DCS\Mission/l10n/RU/TF-51_FOT_ru{066DE39B-A9A7-4679-B36B-5785C8AFBDA9}.png GUI debug.traceback: stack traceback: [C]: ? [C]: in function 'unzUnpackCurrentFile' [string "./Scripts/dictionary.lua"]:579: in function 'unpackFiles' [string "./MissionEditor/modules/me_mission.lua"]:2258: in function 'load' [string "./MissionEditor/modules/me_quickstart.lua"]:275: in function 'func' [string "./Scripts/UI/ProgressBarDialog.lua"]:154: in function 'updater' [string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40> You'll see there that it doesn't have permissions to write to that file path. Can you delete the "C:\Users\igort\AppData\Local\Temp\DCS" directory and try again.
Have you ever attempted to run DCS as an administrator? Don't do this, but just wondering if file permissions error.

I dropped your log file into the DCS log analyzer. It’s identified the crash as being a GPU related issue. Reinstall your GPU drivers. In addition to this make sure any overclocks have been removed from your GPU.
This log file still shows a large number of mods installed. Reinstall clean GPU drivers using DDU to remove all traces of old drivers first. If the latest driver still has issues you could try rolling back to 566.36 Remove you mods and run a slow repair, replicate the issue again if it still occurs and drop a new log. 

Running DCS as admin is not advised.
In particular as of a couple of patches ago this caused major performance issues with WinWing MFDs. Ensure that your shortcut is not set to run as administrator under the compatibility tab. 

Your log is spammed with GPU related issues, see examples below. I've dopped your log file in the DCS log analyzer which has also confirmed this.
There is a GPU-related error
Remove any overclocking from your GPU. Note, some GPUs come with a factory overclock so you use MSI Afterburner to confirm this. Uninstall your GPU driver with DDU and install a clean one. 2025-04-26 20:09:42.395 ERROR DX11BACKEND (2872): DX device removed. Reason: 0x887A0005 2025-04-26 20:09:42.398 ERROR DX11BACKEND (2872): Can't map structured buffer. 2025-04-26 20:09:42.398 ERROR DX11BACKEND (2872): Failed assert `0` 2025-04-26 20:09:42.407 ERROR DX11BACKEND (24512): failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2025-04-26 20:09:42.407 ERROR DX11BACKEND (24512): Failed assert `false && "failed to create vertex buffer"` The DxDiag report also shows the following:
Application Errors
DCS.exe: c00000fd (edCore.dll), c0000005 (Scene.dll), was hung for 58.12s and killed VPforce-TelemFFB.exe: c0000005 (python311.dll) svchost.exe_FontCache: c0000005 (fntcache.dll) NVIDIA App.exe: was hung for 30.65s and killed, c0000005 (libcef.dll) Memory Timing Issues
Remove any overclocking (XMP) from your RAM.  
Additional tuning tips from the log analyzer:
Remove the OH6GunnerExport script for performance reasons. Enable Full Screen mode. Disable Tacview for performance reasons.  
Side note. You might want to turn off auto-updates for your Meta link software and headset. The latest Meta v72 release is known to be causing crashes for some users on Meta link.

There are no crashes in the DCS log file, which would indicate that Windows may be killing the process. Run the Windows DxDiag tool, save the output report, and attach that here as well.
Additional notes from the DCS log analyzer. Note the disabling of the of hot plugging. You have a bunch of unplug events in your logs for your devices. If hot plugging in DCS controls is already disabled then may be a usb power issue, e.g. use a powered usb hub and disable the power management in Windows for your usb controllers in device manager.
Hot plug Events
Disable hot plug in your CONTROLS section. Advice
The log file shows core parking which can lead to performance issues and stuttering. Upgrade your OS to Windows 11 to better support your CPU or disable cores 16,17,18,19 in Windows or Process Lasso. Those are the efficiency cores, disabling them will mean DCS is using the performance cores. I noticed the DCS log analyzer now has slightly different output for the above than it previously did. Windows 11 has better support for cores, additionally check and disable core parking if it is on.
Tuning Tips
Turn off Depth of Field. Set Preload Radius to max. 60000. Turn down Anisotropic Filtering. Consider using DLAA. Set Water to Low.

I've dropped your log into the DCS log analyser which had the following to say. Note that your preload radius is 100000 and is really high for the amount of RAM you have. This will be loading a lot of unnecessary stuff when the mission loads.
Set Preload Radius to 30000 Disable civil traffic Upgrade your RAM to at least 16 GB to play DCS multiplayer. Change your pagefile to at least 24576 MB (initial size). Create a single custom page file, remove any system managed ones, with Initial and Max values of 24576, click Set, Apply and restart your PC. Ensure that Game Mode disabled Ensure that Hardware accelerated GPU scheduling disabled You also have the OH-6 gunner export hook installed. Remove this as has been known to cause performance issues. It doesn't look like you have the OH-6 mod anymore, but the export hook still exists in your Saved Games\DCS\Scripts\Hooks directory.

This one has still come back as a memory timing issue (C00000005 access error I believe is what the log analyzer uses to determine this).
Did you have any existing overclocks, XMP / EXPO profiles on your RAM that you removed? Maybe run a memory test as well to see if that identifies anything, Windows has a tool for that.
Memory Timing Issues
Remove any overclocking (XMP) from your RAM. Further items referenced by the analyzer.
Your DCS has crashed
The crash occurred inside ARF.dll. Try a slow repair of the game, select remove other files option as well. Delete Saved Games\DCS\fxo and metashaders2 and try again. Next, delete %LOCALAPPDATA%\TEMP\DCS and try again. Next, try renaming Saved Games\DCS to DCS.old and try again.

I see you have the SU-30 mod which has been known to cause issues, recommend removing that and running a slow repair of the game (Verify Files for Steam).
I've run the logs through the DCS log analyzer which indicates that this was due to a memory timing issue. Remove any overclocking, e.g. XMP profiles, from your RAM.
null
You should also add a custom page file on your fastest SSD, removing any existing ones, e.g. system managed. Set the Initial and Max values to 32768, click Set, Apply, and restart your PC.
Your preload radius is also maxed out at 150000. This will be loading a lot of redundant stuff into your RAM. Drop this down to 60000.
Some additional performance tuning items. Up to you if you choose to change them. SSAO and SSLR in particular can be a performance hit with little benefit.
Turn down Anisotropic Filtering. Set Shadows to Medium. Disable civil traffic. Turn off SSAO. Decrease Visib Range to Ultra or lower. Decrease Terrain Textures. Set Clouds to High. Turn off SSLR. Set Water to Low.