sleighzy

Following on from silverdevil's comments if the installing a clean newer driver doesn't work then remove any overclocks on the GPU. Some GPU's come with a factory overclock so you can check that with MSI Afterburner. More info from the DCS log analyzer, looks like a number of issues identified in the DxDiag report, some of them video card related. Windows Error Reporting (WER) Your system crashes with Bluescreens. The following kernel-events have been detected: VIDEO_ENGINE_TIMEOUT_DETECTED,VIDEO_DXGKRNL_LIVEDUMP,IRQL_NOT_LESS_OR_EQUAL,PFN_LIST_CORRUPT,KERNEL_SECURITY_CHECK_FAILURE Remove any overclocking (including XMP). Run SFC and DISM to check your Windows. Check for any updates of your BIOS or chipset drivers. Application Errors DCS.exe: was hung and killed, c00000fd (edCore.dll) There is a GPU-related error (Re-)install the latest GPU drivers. Don't overclock your GPU or RAM. For the SFC and DISM checks open a command prompt as administrator and run the below two commands separately and then restart your PC. dism /online /cleanup-image /restorehealth sfc /scannow Some additional performance tuning tips from the log analyzer as well. Set Water to Medium or Low. Set Shadows to Medium. Turn off SSAO. Turn down Anisotropic Filtering. Turn off SSLR. Advice Verify that this is configured correctly in Windows: Game Mode disabled Hardware accelerated GPU scheduling disabled Core Isolation disabled

No crash in the log, so would imply that Windows killed the process. Appears to align with what's in the video. Run the Windows DxDiag tool, save the report, and drop the DxDiag.txt file here.

The stacktrace shows that this bubbled up from the OpenXR Toolkit. I see you are using both the ReShade and the OpenXR Toolkit api layers. I'd recommend that you install the below tool, and then untick the ReShade and OpenXR Toolkit layers and then try again to rule these out. If this works then re-tick and retry each individually to see which layer may be causing an issue. This tool will also show potential issues with these layers, and may fix them. https://github.com/fredemmott/OpenXR-API-Layers-GUI I'd also recommend the following: run a verify files for Steam for the game to do a repair deleting the Saved Games\DCS\fxo and metashaders2 directories. If it still continues then rename your Saved Games\DCS folder to Saved Games\DCS.old and try again. Rename, don't delete, the folder so that you can get your bindings back from the Config\Input folder in there.

Your issue is unrelated so you probably shouldn't hijack other people's posts on a different topic. Regardless, I've run your DxDiag report through the DCS log analyzer, plus some research on the "DPC_WATCHDOG_VIOLATION" error mentioned there. The DCS log file doesn't have a crash, so this will be Windows killing it. Your system crashes with Bluescreens. The following kernel-events have been detected: DPC_WATCHDOG_VIOLATION Remove any overclocking (including XMP)., Run SFC and DISM to check your Windows., Check for any updates of your BIOS or chipset drivers., Application Errors InstalledPackagesAgent.exe: c0000005 (InstalledPackagesAgent.exe) DeviceSetting.exe: was hung for 63.99s and killed For the SFC and DISM checks, open a command prompt as administrator and run the below two commands separately and then restart your PC. dism /online /cleanup-image /restorehealth sfc /scannow Have a google for the DPC_WATCHDOG_VIOLATION error as there are references there, namely around hardware and chipset drivers. If this continues to happen then raise a new post attaching your updated logs instead of this thread.

Drop your DCS log file (C:\Users\username\Saved Games\Logs\DCS\dcs.log) here so somebody can look at it and offer advice.

What version of DCS was fine prior to this occurring? Your log shows a driver 56633.DLSS Enabler for your AMD card. Seems like a mod of some description for DLSS-like support? Have you tried removing that as well? Probably unrelated. Your log file shows your Preload Radius is at the 150000 max, drop that to 60000. Run the Windows DxDiag tool, save the report, and drop that here as well.

Do you have exactly the same problem as this post and log errors? You probably shouldn’t hijack old posts. If you have an issue then raise a new post and attach your logs. You don’t need to install DCS again. Just remove any mods and run a slow repair of the game.

People’s DCS can crash to desktop for numerous reasons. If Windows is killing the process then it may be machine specific and something wrong with your PC. In which case there may not be a game fix. Run the Windows DxDiag tool, save the report, and attach it here as well. The log analyzer also had more items than the ones you listed there, eg turning off SSAO and SSLR, setting shadows to medium, etc. It also shows you have a custom mod. Have you removed all these mods, run a slow repair of the game, and deleted your Saved Games\DCS\fxo and metashaders2 folders as well?

Delete the C:\Users\username\AppData\Local\Temp\DCS folder

You shouldn't hijack other people's posts, especially if they're solved. Your issue is unrelated, and likely a different reason. There is also no crash in that log so it's possibly Windows killing the process, in which case run the Windows DxDiag tool, save the report, and post that and the log in a new post. I ran your log through the DCS log analyzer anyway, few items you can address but they may not solve your problem. Delete your Saved Games\DCS\fxo and metashaders2 folders if you haven't already done so since the upgrade. Advice Change your pagefile to at least 32768 MB (initial size). If you have stability or performance issues pointing to your GPU, rollback the GPU driver to version 566.36, Verify that this is configured correctly in Windows: Game Mode disabled, Hardware accelerated GPU scheduling disabled Tuning Tips Disable Tacview for performance reasons., Set Water to Medium or Low., Turn down Anisotropic Filtering., Set Preload Radius to max. 60000 (with your 32Gb RAM I'd probably recommend 30000)

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.

You're on Windows 11. Just make sure you have core parking disabled (can use ParkControl for that). You shouldn't restrict cores as this makes them unavailable to DCS. Windows 11 is smarter about the cores and DCS is able to use the E cores for the right things.

Possibly... Could be a VoiceAttack install issue as well. Could always try v2 as well then (it's $10, but it's your money). Do you use OpenKneeboard? You could add VoiceAttack as a Capture Window to that and then ingame see if you get anything logged, e.g. the active tx node message to see if a delay issue. If identical to Fox-one-76's issue then may not be able to be something I can replicate or fix on my end. If it's just a delay, and not a window focus issue, then I can provide a profile workaround to test.

Weird. I'm on v1.16 as well as others. Might have just been something with that particular install (permissions? ). Oh well, gremlins. Happy flying then! Sing out if you have any other issues.

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.

Hi @Fox-one-76. I've tried numerous things but am still unable to reproduce this. Can you confirm that you aren't running DCS as administrator, e.g. right-click both your shortcut for DCS, as well the DCS.exe file being used, and then select properties and make sure "Run as administrator" isn't ticked. I also run with OpenKneeboard and Open tablet driver so wouldn't expect an issue there. Can you try without the streamdeck and DCSBIOS? This issue occurs in both VR and 2D correct? I'll re-run all my tests again in VR but would expect this issue to exist across both. WhisperAttack transcribes the speech-to-text and then executes VoiceAttack with this, which will reuse the existing VoiceAttack if its already running. It's almost like this part of it is being blocked until focus is taken away from DCS. For example, when you start up VoiceAttack for the first time do you get a message "Do you want to allow this app to make changes to your device?". Is this VoiceAttack v1 or v2? I'm assuming this profile is configured with "Send this command to active window". (which is correct) null

WhisperAttack v1.2.0 is now available. What’s New? WhisperAttack now has a new screen for entering word mappings. These take effect immediately so no more needing to update the word mappings text file and restarting WhisperAttack. Fixes & Improvements Fixed an issue where the transcribed text could add unexpected dashes (- and --) at the end of words and sentences, these are now removed. Minor UI improvements Release v1.2.0 · nikoelt/WhisperAttack null @FredOfMBOX , this is now fixed in the latest v1.2.0 release.

Do you have any exported viewports, e.g. MFDs, etc.? Attach your DCS log C:\Users\username\Saved Games\DCS\Logs\dcs.log (it may just be a text document named "dcs" if your Windows is hiding file extensions)

That may be turned on by default in Windows 11. You can use the ParkControl software (can also be done via a registry key) to unpark the cores. As you are on Windows 11 then disabling core parking is advised, vs. using Process Lasso (which can cause stutters).

Can you attach a new log file after replicating the issue now that you have tried renaming Saved Games\DCS and run a repair of the game (did you choose the option to remove files when you ram the repair as well?) You are also running DCS in the bin-mt folder. Run the one in the bin folder instead, they’re both multithreaded, and bin-mt will be removed in the future.

DCS shipped with the latest DLSS version, but the default preset hasn't changed (they're still using C), so you shouldn't notice a perf decrease because of this. You have to explicitly update it in the DCS config to change the preset.

There is no information to go on here. 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). If there is a dcs.log-<timestamp>.zip file in there then also attach that.

There is no crash in that log file. You probably shouldn't hijack another person's post as your issue may be completely unrelated, especially one that is almost a year old. As there is no crash in the log then it may be Windows killing the process. In this case you need to run the Windows dxdiag tool, save the report, and attach that as well. I recommend raising your own post and attaching the log and the DxDiag report as these issues are likely unrelated.

@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.

No worries. It's quite possibly the dxgi.dll that was causing the issue. This doesn't ship with DCS so people put it there (automatically sometimes) when using ReShade, or DLSSTweaks for overriding presets. I'm assuming this is how it ended up in yours as well. May have conflicted with the Windows one and what DCS is depending on for it's graphics libraries. ....or something else Anyway, glad you're all sorted. Happy flying!