sleighzy

@AnarchyZG, @PawelKPL, can you please attach your DCS log files, and dcs.log.<timestamp>.zip (contains crashes), files. Would be valuable to see if you're experiencing the same issues as reported by other users, or something else unrelated.

Not sure if something has changed with the DCS log analyzer but the log states that core parking is enabled but this wasn't flagged by the analyzer. Process Lasso was not mentioned in the logs so at this stage I'm assuming that this is the default that Windows 11 is setting now. 2025-04-27 09:05:55.394 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) You're already on Windows 11 so can you use something like ParkControl (https://bitsum.com/parkcontrol/) to disable core parking. This has resolved this issue for a number of users experiencing these issues on the latest patches. In addition to this I see that TrackIR is being reported: INPUT (Main): created [TrackIR] Can you confirm whether or not you do have TrackIR, or any other head tracking, in use. Can you also confirm that DCS is not being run as administrator, right-click on your DCS shortcut that you use, choose properties, and verify that "Run as administrator" is not checked under the Compatibility tab of that menu. EDIT: looks like the log analyzer is flagging core parking again now, I ran your log back through it to confirm, so ignore the first part of my comment re: it not showing up in the log analyzer.

@HR-Crumble, @Dedbeat Please attach your DCS log files, and any other dcs.log.<timestamp>.zip files when this occurs. Not much information to go on without these. There are a few reports of this problem across many forum posts. Would be good to see logs to determine if anything is common across these, and what others have done to resolve may also be applicable to you.

Recommend you attach your DCS log file, and any dcs.log.<timestamp>.zip files when this occur. Will help narrow down the cause, possible solution, and other tuning advice.

Handtracking is janky and not really supported in DCS. Almost impossible to do a lot of things. Definitely try it if you're curious, but I'm pretty sure you'll switch back to normal in short measure

So sounds like this is working fine for you now since the Windows 11 upgrade and allowing your PC to use all cores? This is generally the recommendation anyway as Windows 11 + DCS handle hybrid P/E cores much better now. If the problem comes back then drop another DCS log. If the problem comes back also try uninstalling OpenTrack, replicate the issue, and drop a log.

Use DLSSTweaks to enable the hud overlay. https://github.com/emoose/DLSSTweaks You don't need to copy any files into DCS, just run the DLSSTweaksConfig.exe file for configuration and set GlobalHudOverride to Enabled (all DLLs)

Can you confirm whether or not you have ever had TrackIR (or other head tracking), or have installed TrackIR software, or have one plugged into your machine? Do you still get these messages appearing? Can you also disable Device Hotplugging in the DCS controls settings, it’s the button at the bottom on the right hand side. Let me know if this is already disabled.

Thanks for that, much appreciated as always. Yeah, didn't realize this was across multiple machines. The stack traces all start with that "(World) wSimCalendar::DoActionsUntil", then have slightly different operations in between, and then look to be largely ending at "(edCore): LinkBase::Set" just prior to the ACCESS_VIOLATION. Given the number of machines hitting this and the followup items you've done now I'll defer to the ED dev team. @BIGNEWY , is this something your team could have a look at please.

Please replicate the issue and attach your DCS log file.

VR wasn't being used in this session, but I did notice TrackIR. Do you have TrackIR (and were using it)? 2025-04-27 08:36:40.536 INFO INPUT (Main): created [TrackIR] Couple of other points: You're running DCS as administrator, do you have another account you can use instead (for security reasons you shouldn't run stuff as administrator). I also ask this as users on Winwing MFDs experienced a similar issue when running as administrator, hence my question around TrackIR. You're running DCS from the bin-mt directory. Run DCS from the bin directory, they're both multithreaded and bin-mt will be removed in the future.

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.

Please attach your DCS log file and any dcs.log-<timestamp>.zip files associated with this crash.

Still the same C0000005 ACCESS_VIOLATION which indicates memory issue. Have you removed all overclocking and XMP profiles (BIOS) from your RAM? Run a memory test as well. Ran the other commands I posted previously?

Can you drop a DCS log file here with this occurring without TrackIR. Can you also run the Windows DxDiag tool, save the output report and drop here as well.

Can you please replicate the issue again and then drop a DCS log file here. Will help identify if there are common issues being experienced across these reports.

Is the right log file? That text does not display within it and the timestamp is wrong. C0000005 ACCESS_VIOLATION errors can sometimes be due to memory problems. I've dropped your log into the DCS log analyzer which seems to verify some of this based on the DxDiag report within the zip file: Windows Error Reporting (WER) Application Errors DCS.exe: was hung and killed Memory Timing Issues Remove any overclocking (XMP) from your RAM. 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. For the SFC and DISM commands you can run each of those separately as per the below. Run those from a command prompt as administrator. dism /online /cleanup-image /restorehealth sfc /scannow

I agree with this, we typically steer people away from SteamVR, admittedly I haven’t used SteamVR in a little while (and have no interest in installing it again to experiment). Everybody is different though, curious what others have to say. I use VirtualDesktop and the VDXR runtime it has has been the most performant for me, and others I’ve spoken with. SteamVR has a greater overhead than VDXR, as does the Meta app. I disagree that VDXR is aimed at AMD and not Nvidia, not sure of the relevance of this. If anything most AMD users on the VirtualDesktop Discord have issues largely in part due to the AMD drivers.

Open a command prompt within the DCS\bin directory and then run the below command (all one line). Delete your Saved Games\DCS\fxo and metashaders2 folders afterwards so that it rebuilds the texture caches again for that version. DCS_updater.exe update 2.9.14.8394@release

@Shimakaze514 Thanks for the feedback, very informative re: the TrackIR stuff in your last comment. In this comment you state that you don't have TrackIR, yet on Windows 10 you were getting device plugged/unplugged events for this. You haven't posted a log from that, so I can't confirm if those particular ones showed up in the log. These events do not show up in the log you posted. DCS will log these events, which can be related to either hotplugging (which you said you'd disabled), or other factors such as not using a powered usb hub, or usb power management. Or additional issues with too many devices on a hub causing saturation of the usb controller with bandwidth and interrupts etc. Based on your logs you have no additional peripherals such as MFDs etc. so I assuming not an issue around that. You said however you have no TrackIR device, but still get these issues. From the Windows 11 log you attached a few days ago it is definitely registering that a TrackIR device, or something reporting itself as being one by Windows, is connected. 2025-04-18 03:23:16.770 INFO INPUT (Main): created [Keyboard] 2025-04-18 03:23:16.825 INFO INPUT (Main): created [TrackIR] Are you able to determine further why a TrackIR device is being reported? Not sure if a tool like https://www.nirsoft.net/utils/usb_devices_view.html or https://www.uwe-sieber.de/usbtreeview_e.html would help with this.

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.

The game can crash for users for many many different reasons. I’d recommend you raise your own post along with the DCS log file containing this (and other dcs.log-<timestamp>.zip files) for this. Alternatively you can drop them in the Eagle Dynamics DCS Discord server in the #dcs-log-analyzer channel.

I also noticed that you were loading into Germany Cold War. Does this happen on other maps as well?

Wow, you win the award for most mods I seen yet The log is spammed with a bunch of errors for those. I'd recommend temporarily removing those and running a slow repair of the game. Even though they may not be used in a mission they will still be loaded. Delete your Saved Games\DCS\fxo and metashaders2 caches after this as well so that the cached textures are fresh and no old cruft is being loaded. Initial load time when it first recompiles those may increase, but all good afterwards. This will at least get you to a clean state and rule any of that out. I ran this log through the DCS log analyzer which confirmed a few things I saw in the log. You appear to be applying an affinity mask to this process, I don't see it in the process args but maybe either registry, Process Lasso (?), or somewhere else. You've basically prevented half of your CPU from being used. I'd remove that as well. system affinity mask: 11111111111111111111111111111111 process affinity mask: 1111111111111111 CPU: Intel(R) Core(TM) i9-14900K [1x L3 caches] CPU has uniform cache size 36 MB (per cache) all CPU cores have the same efficiency class 1 CPU cores have different performance classes: [1-2] logical cores with performance class 2: {4, 5, 6, 7} logical cores with performance class 1: {0, 1, 2, 3, 8, 9, 10, 11, 12, 13, 14, 15} common cores: {8, 9, 10, 11, 12, 13, 14, 15} render cores: {4, 5, 6, 7, 0, 1, 2, 3} IO cores: {} unavailable cores: {16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31} Dropping your preload radius down (currently max of 150000) may also help with loading times and reducing VRAM/RAM usage. You can also update your shortcut to run DCS from the bin directory vs. bin-mt now. They're both multithreaded and bin-mt will be removed in the future. Also prevents chances of other errors users have hit with this. Try the above and see what happens. The performance improvement after initial load is potentially all the assets have been cached at that stage, although not permanently. Note that the above are not guarantees, but will at least rule out a number of factors. DCS is becoming smarter around the way it manages it's CPU core usage so potentially additional changes in these latest releases. For example, it may use the E-cores for I/O thus freeing up your performance cores from performing this work. I'll see if I spot anything else in here, but would be good to get another log with this issue but without all the mod errors and in a known state to filter out the noise and see what happens with your CPU.

Bignewy mentioned that you have IC failures and to remove mods, however you stated you have no mods. The IC failures can actually be due to the out of memory errors and the textures are unabled to be loaded, this is a false positive that they are an IC failure, see example error below....you have a lot of these, which indicates the memory issue I mentioned earlier. 2025-04-22 19:44:18.941 ERROR EDCORE (2092): More out of memory in SharedBuffer for 11184952 bytes. 2025-04-22 19:44:18.941 ERROR EDCORE (2092): Not enough memory to decompress: uh1_tail_us_army.dds 2025-04-22 19:44:18.943 WARNING SECURITYCONTROL (2092): IC fail: /textures/uh1_tail_us_army @ bazar/textures/uh-1.zip 2025-04-22 19:44:18.943 ERROR BACKENDCOMMON (2092): Can't load image '/textures/uh1_tail_us_army.dds'. Reason: The parameter is incorrect.