sleighzy

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.

I've run your DCS log file through the DCS log analyzer which has identified a couple of issues you should attend to. It also indicated you do have mods in there.
Note, one of the folk who runs some DCS support has also informed me that the MB-339 has been broken for almost 3 years.
Memory Timing Issues
Remove any overclocking (XMP) from your RAM. Some GPU cards come with a factory overclock, you can use MSI Afterburner to verify if this is the case.
Bluescreen
Your system crashes with Bluescreens. Remove any overclocking. Run SFC and DISM to check your Windows. Custom mod error
Error '=' expected near '-' Line 6 Script C:\Users\Clemens Klömpken\Saved Games\DCS.openbeta\Mods/tech/V...     (note that this is truncated in the logs so does not have the full name, but you definitely still have some mods in there  Your DCS has crashed
The crash occurred inside KERNELBASE.dll. Remove your custom mods. Try a slow repair of the game. 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.

Try disabling Hardware Accelerated Graphics (HAGS) if you haven’t already. 

You mean to start the game to get into the main menu, or starting a mission?
Your preload radius is maxed out at 150000 which is really really high, especially with 32Gb of RAM. This will be loading a large amount of the map and textures unnecessarily. Drop this down to 60000 or lower, could do 30000. This will effect loading time when starting a mission.
If you haven't already then also add an exclusion in your anti-virus software, e.g. Windows Defender, for the entire DCS installation folder and restart your PC.
For comparison purposes do your friends have the same number of modules and maps as you? I see the F4 sounds might take a while, do they also have the F4?
Unrelated side note, you have the game arguments `--force_enable_VR --force_OpenXR` which are not needed (force_OpenXR is redundant now as well).

You logs contain lots of errors around GPU instance being removed and DXGI_ERROR_DEVICE_REMOVED
Based on the below DCS FAQ this can be an issue with video drivers, or a hardware failure.
https://www.digitalcombatsimulator.com/en/support/faq/startup/#3312253
From the DCS log analyzer:
There is a GPU-related error
Remove any overclocking from your GPU. Uninstall your GPU driver with DDU and install a clean one. Further tuning advice from the log analyzer below. Note, these are tuning and performance recommendations, and likely not the root cause of your issue but may assist with smoother game play and fps.
(SSAO and SSLR are performance hits with little benefit).
Turn off SSAO. Enable Full Screen mode. Consider using DLAA. Turn off SSLR. Disable civil traffic. Verify that this is configured correctly in Windows:
Game Mode disabled Hardware accelerated GPU scheduling disabled Core Isolation disabled And disable Core Parking, which is currently enabled. You have numerous mods, some of which contain errors, so you might want to try removing those and running a slow repair as well. This is potentially not the cause though.

You have a number of mods, some of which are known to cause issues. Please remove your mods, run a slow repair of the game, delete your Saved Games\DCS\fxo and metashaders2 folders, and then try again.
In addition to this your preload radius is set to 150000 which is really high and you're unnecessarily loading a lot of stuff. The DCS log analyzer recommended to drop that to 60000, as well as turning off SSAO which is a performance hit with little benefit.
Looks like there is a track (.trk) file in that zip already so may or may not (if crashed without a chance to write this correctly) be from this occurrence.

I've dropped your DCS log file into the DCS log analyser which had the following feedback. Note, these items are performance related so are aren't strictly the cause of your loading time problem but worth resolving given the impacts that they have (and may help with that).
Turn off SSLR.
Turn off SSAO.
Disable civil traffic.
Consider using TAA instead of MSAA.
In addition to this I see you are also using the OH-6A mod, along with the gunner export script. This has known performance impacts on multiplayer servers with a large number of units. The advice on the GitHub site calls out this performance issue as well and has a recommendation to remove that script.
Remove gunner_export_hook.lua from Saved Games\DCS\Scripts\Hooks to avoid it (Doorgunner won't be functional anymore)
The log analyzer also states that your Windows version is out of date. There may be performance improvements in later versions.
If you haven't already then add an exclusion to your entire DCS installation directory in your anti-virus software.

The DCS log does not contain any crashes, so is probably Windows killing this, hence my request for the DxDiag report which shows the last 10 crashes in your system and the processes involved.
The DxDiag report shows numerous Blue Screen crashes (codes 7e, 3b, be) which appear to quite serious. It also contains a hardware failure (code 141), but may just be related to GPU drivers.
Make sure you've updated all your Windows drivers to the latest versions.
Can you run the a command prompt (cmd.exe) as an administrator and then run each of the below commands individually and then restart your PC.
dism.exe /online /cleanup-image /scanhealth
dism.exe /online /cleanup-image /restorehealth
dism.exe /online /cleanup-image /startcomponentcleanup
sfc /scannow
chkdsk /R /F /X
 
The LiveKernelEvent 141 error is usually associated with hardware problems, especially related to the graphics card or power.
For this one you can try reinstalling your graphics driver to see if it helps. You may need to use DDU to completely remove the old driver and install the latest if a basic driver reinstall doesn't work.
There may be hardware issues somewhere, but the above may help with this.
How much free space do you have on your SSDs as well, especially any that are hosting your Windows or page file?
 

I've had a look at this log, and dropped it into the DCS log analyzer. It doesn't contain a crash, so load into that multiplayer server and send one when this occurs. Here is the initial following feedback.
If you have FPS issues, try turning off VSYNC in graphics settings. Enable Full Screen mode. Turn off Depth of Field. Turn down Anisotropic Filtering. Set Preload Radius to max. 60000. Disable civil traffic. Your preload radius is currently really high (100000) so dropping that right down will reduce the amount of textures that get initially loaded. This may be why you get that long slow load time at the beginning. You only have an 8Gb VRAM card so once that's full it'll start spilling out into your system ram and page file, which will be much slower.
Are both DCS and your page file on SSD drives (preferably NVMe)?
If you haven't already then add the entire DCS installation folder as an exclusion into your anti-virus software as well and then restart your PC. Are you using Windows Defender for this, or another 3rd party anti-virus software?

This log file isn't from launching in VR so it's hard to tell. What I do see (and confirmed by the DCS log analyser) is that you have 32Gb of RAM (excluding your page file but that will be slower) and your preload radius is 150,000. Recommendation is to drop to 60,000. The preload radius is causing a lot of the map etc. to be loaded all at once (unnecessarily) which may explain this.

There are a lot of memory allocation errors in that log with it attempting to decompress texture files. I see your preload radius is set to 150,000 which is far too big for your processor, RAM, and card. The DCS log analyser recommends dropping that to 30,000.
It also states the following:
Set Water to Low. Enable Full Screen mode. Set Preload Radius to max. 30000. Turn down Anisotropic Filtering. Can you also run the Windows dxdiag tool and save the report it generates and attach it here as well.

Is being covered in this forum thread, you can track progress and provide info there. 

I also noticed you're using Varjo-Foveated. Worthwhile checking but DCS added a "Quad Views" option under the VR settings that enables/disables Quad Views a patch (or two) ago. This is off by default, so worth checking this to make sure it's on if you haven't done so already.

32Gb is not sufficient for larger multiplayer servers. This is evidenced by your system running out of memory based on the log. From the DCS log analyser:
Your System ran out of Memory
Increase RAM or pagefile There is a GPU-related error
Remove any overclocking from your GPU. Uninstall your GPU driver with DDU and install a clean one. Advice
Change your pagefile to at least 32768 MB (initial size). Tuning Tips
Enable Full Screen mode. Turn off SSAO. Consider using TAA instead of MSAA. Turn off SSLR. Set Shadows to Medium. Disable civil traffic. Set Water to Low. Decrease Terrain Textures. Turn down MSAA to 2x. For the page file issue (note that the below is a bandaid fix to give your system an additional 32Gb without actually adding an extra 32Gb physical RAM):
You only have a 5Gb page file, so I'm assuming a default Windows system managed one Set a custom page file with Initial and Max values of 32768, click Set and Apply, and then restart your PC Make sure you have a single page file and it's on your fastest SSD and remove any other page files

Try removing your previous firewall rules for DCS and then start the server again so that it asks you if you wish to add rules for it. It’s been mentioned that with the latest patches that DCS will now run the DCS.exe in the bin directly, was previously bin-mt, now that everything is multithreaded and that firewall rules need to updated for the new executable. Give it a shot anyway. 

@cobrabase, Which of those drives is DCS installed on? Hopefully not a HDD and is on an SSD....
You can drop your DCS log file here instead if you like.

I've dropped your crash log into the DCS log analyzer which has the attached output. My reference to installing the above files was from the VCRUNTIME error. Try the removal of the RAM overclocking first. Failing that, try the other options listed further down in that screenshot.
null

Cool, make sure you add the exclusions to Windows Defender as well and restart your PC before running a repair if/when you need to.

Had you made any changes to your system at all, no matter how insignificant? I've looked through your log and looks to be dying when attempting to initialise the GPU, the cuda library for it. I've dropped one of the logs into the DCS log analyser, see attached screenshot for info. It has some recommendations, although I'm not sure if they'll be helpful, but at least highlights the crash for you.
You've said that you deleted and reinstalled the display drivers. You could use DDU to ensure that everything is removed as expected, some driver related stuff could have been left behind, before reinstalling the drivers again. You could potentially look to install even a driver a couple of versions older that is known to be more stable.....
https://www.guru3d.com/download/display-driver-uninstaller-download/

One item that shows up in your log is a client/server version mismatch. Looks like you're not on the latest version of DCS. Should try upgrading to that and retry again, not saying that this'll fix your problem though.

Drop your zip file in the #dcs-log-analyzer channel in the DCS discord, https://discord.com/channels/542985647502393346/1179171301651402802 and it will provide some advice. I dropped it in there for you (but you’ll need to do yourself as well as it only last 5 mins) but it highlighted a potential crash with a RAM memory timing issue and to remove overclocking XMP on the RAM. There were a few other options for troubleshooting as well.