sleighzy

That's Windows Firewall, not the same thing. You want Windows Defender for the antivirus settings. https://support.microsoft.com/en-us/windows/virus-and-threat-protection-in-the-windows-security-app-1362f4cd-d71a-b52a-0b66-c2820032b65e#ID0EBF=Windows_10 Add a new folder exclusion in it for your E:\Eagle Dynamics\DCS World folder.

Attach your DCS logs.

Some GPUs come with a factory over lock, you could confirm if this is the case with MSI Afterburner. For the unplug item could be a power issue (maybe related ), do you use a powered usb hub for them? …or unrelated, just interesting that it shows up unexpectedly in the logs.

Attach your DCS log file. DCS is now also all multithreaded, there is no MT and non-MT.

Both of these logs indicate a crash due to a GPU issue. I see also unplug events. There is a GPU-related error Remove any overclocking from your GPU. Uninstall your GPU driver with DDU and install a clean one. Also confirmed by this log message. DX11BACKEND (14804): failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED See the DCS FAQ on this. https://www.digitalcombatsimulator.com/en/support/faq/startup/#3312253 There are also unplug events in here which are also likely related: INFO APP (Main): Device unplugged: [HID] HID-compliant device

Please raise a new post with your logs attached. It sounds like you have a different problem so shouldn’t hijack other people’s posts which are now solved.

100% agree with this. All new posts raised for this exact same reason should be linked to the fix/workaround and immediately closed. There are hundreds of these across numerous posts, Discords, and Reddit. If only people could learn basic search skills. </rant>

As pointed out, you have a lot of mods. The DCS log analyzer also indicates that the cause of one of the crashes is due to a RAM issue. Memory Timing Issues Remove any overclocking (XMP) from your RAM. Take care of that and see if this continues to occur.

I've gone back through your logs manually for the Disable Hot Plug reference. The log analyzer bases this on plug/unplug events, which normally occur when hotplugging is on and it constantly scans for new devices and sees them being plugged/unplugged. In your logs there is the following: 2025-03-02 18:47:06.661 INFO APP (Main): Device plugged: [SWD] WAN Miniport (SSTP) 2025-03-02 18:47:07.688 WARNING LOG (18476): 1 duplicate message(s) skipped. 2025-03-02 18:47:07.688 INFO APP (Main): Device plugged: [SWD] WAN Miniport (IKEv2) 2025-03-02 18:47:07.716 WARNING LOG (18476): 1 duplicate message(s) skipped. 2025-03-02 18:47:07.716 INFO APP (Main): Device plugged: [SWD] WAN Miniport (L2TP) 2025-03-02 18:47:07.721 WARNING LOG (18476): 1 duplicate message(s) skipped. 2025-03-02 18:47:07.721 INFO APP (Main): Device plugged: [SWD] WAN Miniport (PPTP) 2025-03-02 18:47:07.765 WARNING LOG (18476): 1 duplicate message(s) skipped. 2025-03-02 18:47:07.765 INFO APP (Main): Device plugged: [SWD] WAN Miniport (PPPOE) 2025-03-02 18:47:07.809 WARNING LOG (18476): 1 duplicate message(s) skipped. 2025-03-02 18:47:07.809 INFO APP (Main): Device plugged: [SWD] WAN Miniport (IP) 2025-03-02 18:47:07.854 WARNING LOG (18476): 1 duplicate message(s) skipped. 2025-03-02 18:47:07.854 INFO APP (Main): Device plugged: [SWD] WAN Miniport (IPv6) 2025-03-02 18:47:07.898 WARNING LOG (18476): 1 duplicate message(s) skipped. 2025-03-02 18:47:07.898 INFO APP (Main): Device plugged: [SWD] WAN Miniport (Network Monitor) 2025-03-02 18:47:22.600 WARNING LOG (18476): 1 duplicate message(s) skipped. 2025-03-02 18:47:22.600 INFO APP (Main): Device plugged: [SWD] TOSHIBA TV 2025-03-02 18:47:25.294 WARNING LOG (18476): 4 duplicate message(s) skipped. 2025-03-02 18:47:25.294 INFO APP (Main): Device plugged: [SWD] HPB4CE71.home (HP OfficeJet Pro 7720 series) 2025-03-02 18:48:48.642 WARNING LOG (18476): 2 duplicate message(s) skipped. 2025-03-02 18:48:48.642 INFO APP (Main): Device plugged: [SWD] [TV] Samsung 6 Series (50) 2025-03-02 18:51:54.354 WARNING LOG (18476): 9 duplicate message(s) skipped. 2025-03-02 18:51:54.354 INFO APP (Main): Device unplugged: [SWD] [TV] Samsung 6 Series (50) The log is then spammed with plugged/unplugged events for your "[SWD] [TV] Samsung 6 Series (40)" throughout it. I don't know what is triggering this on your system or how it is connected to your PC so you might need to look into that. Constant plug/unplug events can cause performance issues and stuttering in the game. Sometimes this can be caused if these devices are connected via USB but don't have enough power, e.g. need a powered hub, or if power management isn't disabled for the USB controller in device manager which means it can causes them to sleep/awake. The log analyzer lists a couple of items that may or may not be an overall issue, the core isolation one I think falls into that bucket, as a suggestion for looking at, it can't confirm if that it actually the case but raises it for awareness. The crash is definitely GPU related however based on the results.

You've not supplied the full log file, that snippet isn't enough to determine root cause. Attach your full log to this post for review. There are numerous mods that can cause this as well, e.g. Su-30 is also known to be broken. Remove all those, run a slow repair of the game choosing the option to remove extra files. Mods may or may not be the problem, would need the full log.

This is on by default in Windows 11 (it didn't used to be in Windows 10). You can search for it in your Windows settings, Google should also have some steps for it. As to the GPU overclocking, some GPUs come with factory overclocks, believe you can use MSI Afterburner to check for this as well. Hopefully just reinstalling the drivers works fine for you. You should raise your own forum post, or take this to the Eagle Dynamics DCS Discord, instead of putting this on somebody else's post. Your problem sounds different. Also attach your DCS log files when a crash occurs so we can see what happened.

As well as updating page file ensure that you have deleted your C:\Users\username\Saved Games\DCS\fxo and metashaders2 folders. These can also be a cause of this. These folders do not get deleted when uninstalling and reinstalling the game so that would have had no effect on those.

This issue occurred after any patches, i.e. this dll was already on people's systems. It was only recently flagged when virus database updates came out recently. Based on that then it would not have been flagged at the time of initial development and distribution.

Most likely mods issue as rob10 said. Can you state which mods you have? There are a few, e.g. the Su57, which are causing naval vessels to not be shown. One user has identified these ones are being causes: null

Looks like slightly different than my Windows 11 task manager but yeah looks like a couple of cores pegged. You've said you're on Windows 11 which is good as the task scheduler should be better than Windows 10. Is that screenshot taken when flying, or just in the menu? In task manager for the Details tab can you right-click on the DCS.exe process and choose the affinity option. Toggle off the affinity for those cores that are pegged, see how it goes and then toggle them back on again, keep DCS running the entire time. See if they (and the others even) remain pegged at 100% on those once affinity is toggled back on again. In response to things being worse with the previous changes you could try reverting each one at a time, e.g. hardware accelerated graphics scheduling, etc. to see if DCS goes back to the previous state you had (or improves) to identify which one of those made it worse for you. Also make sure you're not running other performance monitoring tools, e.g. MSI Afterburner, or overlays in Nvidia App / Nvidia GeForce Experience.

With DCS running open Task Manager and on Performance tab go to your CPU tab which displays all your cores. Do you have a single one (or maybe 2) that are pegged at 100%?

Yes. It's a false positive. You will need to add a folder exclusion for the entire DCS installation folder in your antivirus software, e.g. Windows Defender. Then repair the game (Verify Files in Steam), or restore that file from your antivirus quarantine. If you do not do a folder exclusion then the file may be quarantined again.

@Skyracer, log analyzer back online so some further info. As per my previous comment, disable core parking. Additionally disable core isolation. Tuning Tips Enable Full Screen mode. Set Water to Medium or Low. Turn down Anisotropic Filtering. Turn off SSLR. Turn off SSAO. SSLR and SSAO are a performance hit with not a huge amount of benefit. I also note that your preload radius is set to the max of 150000. Drop that down to 60000 to save a bunch of VRAM and RAM. Check also the following: Game Mode is disabled Hardware accelerated GPU scheduling is disabled

It's not something they can fix like that. As per the official statement on the Heatblur Discord (the makers of this module) anti-virus software can incorrectly flag things as a false positive. This is not a defect in the product and has happened for other modules in the past. null

The DCS log analyzer is currently "broken" for some log files due to changes in the logging now after today's patch. My initial comment at this stage, given lack of that info from the analyzer, is that if nothing else has changed then: ensure all custom mods are removed run a slow repair of the game, with the option to remove files delete your Saved Games\DCS\fxo and metashaders2 folders. This will then allow DCS to rebuild the shader caches fresh using the new files from the latest patch. If this was running perfectly smoothly just prior to the patch then try that if you haven't already. Additionally make sure you have unparked your cores, this message is present in the log file: WARNING EDCORE (Main): CPU HAS PARKED LOGICAL CORES (this can be source of stuttering and reduced performance especially on hybrid CPUs with P/E-cores)

I found out recently (ED DCS Discord) that the cartridge message is if you have the Viggen installed. It also creates a file everytime in the Saved Games folder and you need to clean them up manually. Comment from Discord:

@Mrhuge, please attach your C:\Users\username\Saved Games\DCS\Logs\dcs.log file (may just be a text document named "dcs" if your Windows is hiding file extensions). Make sure you've started the game completely before grabbing the log.

HeatBlur (makers of the module) stated on their Discord server that this is a false positive, apologised for inconvenience to users, and provided the same workaround of excluding the DCS game folder in your anti-virus software and running a repair.null

Yup, all your settings will remain. Just need to put back the new DLSS4 310.x.x. dll again that has those fancy presets.

Did you update your DCS today? It will replace the dll files with the original ones and you need to replace them again. ...if that was the case for you.