sleighzy

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

Yeah, can't comment on that one too much, just something it pulled out of the DxDiag report along with general recommendations that could resolve that. The DxDiag contains the last 10 Windows system errors so don't know if it's in there since the Windows update or not. When did the black screen start occurring, just since the last DCS update, or since that and has fine up until today? Any other changes around the same time this started happening? Was happening before or just after the Windows update? Just trying to nail down a timeline for anything that could have changed in your system.

I've dropped your log into the log analyzer. As expected based on the starting entries in your log file you have corrupted files in your Saved Games\DCS folder. Repairing the game won't fix that. Config File Corruption Delete or rename Saved Games\DCS.openbeta\Config\options.lua and try again. If that still doesn't work then rename your Saved Games\DCS.openbeta folder to DCS.openbeta.old (rename so you can get back your bindings in the Config\Input directory so you don't lose your control bindings)

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.

One thing I noticed here from your screenshot was the message that multiple Vaicom plugins were found. Can you check your VAICOM installation and make sure you have only one in VoiceAttack apps and there is only a single dll file. null You also appear to have the "PTT: Use an active TX node" message similar to the other user, I don't know if this is related...although your issue is slightly different.null

Hi @VirusAM. Can you enable debug within Vaicom and then replicate this issue and then drop your C:\Users\username\AppData\Local\WhisperAttack\WhisperAttack.log file here. Please also provide a screenshot from VoiceAttack so I can see the full output from the debug. Can you also ensure that the Vaicom window is closed, i.e. completely closed so that it is just in the system tray. Can you also try this by updating your settings.cfg file in WhisperAttack so that the whisper model used is tiny.en (I think it's small.en by default). I see in your screenshot the message "PTT: use an active TX node" when this occurs. Vaicom has a timeout from when you release the tx button till it receives the actual command. This means that VoiceAttack gets the command, sends it to Vaicom, but due to it taking too long it won't do anything in the game. It seems like maybe there is a timing issue and it is taking too long from when WhisperAttack hears your command until VoiceAttack processes it after you release the button. What video card do you have? I have only seen this with one user before, it seemed to be a VoiceAttack issue of some description at the time. Are you on VoiceAttack v1 or v2? There is a profile tweak we can make that may help but would be good to see the whisper attack log file for this issue first to confirm. You also mentioned that the default Windows speech engine works just as well for you as WhisperAttack. If that engine is working for you then WhisperAttack may not be needed, this was just beneficial for users for whom the Windows one doesn't work well. There is no ability to train this whisper model.

The removing of the overclocking, e.g. XMP profile, that comes from the log analyzer is because the error code in the stack trace (and DxDiag reports if they are there as well) in the log generally indicates a memory timing issue at the time. You can sometimes get timing issues with 4 sticks of RAM vs. 2 (overclocked and XMP), inconsistent RAM, overclocking, or other faults. Disabling the XMP profiles (or other overclocking) is a good way to initially troubleshoot this in case the memory timing issue is related to this and helps to rule it out. If not, or issue resolved by other means, then turn back on again.

Your issues could be totally unrelated to the one raised in this post. This post has already been resolved due to a presumably different problem. Please raise a post of your own. I ran one of your logs through the log analyzer which prompted the following: Try a slow repair of the game, including the option to remove files Delete Saved Games\DCS\fxo and metashaders2 and try again (although you mentioned you've already done this) Next, delete %LOCALAPPDATA%\TEMP\DCS and try again Next, try renaming Saved Games\DCS to DCS.old and try again (note that this is renaming and not deleting so that you can get your bindings back from the Config\Input folder) Additional tuning items: Set Preload Radius to max. 60000., Enable Full Screen mode., Consider using DLAA

Those settings will work in VR. Note that if you're using C then nothing will have changed elsewhere in the game as C is the default that DCS has always used. The 2nd line is just so that it doesn't apply DLSS to MFDs. Do you notice any difference in the MFDs when using DLSS vs. not using DLSS?

The driver won't matter. 566.36 did not contain the DLSS4 K preset, but the latest DCS ships with the DLSS4 dll so will have that preset. Note, if you've changed NVPI setting to override the dll used then it won't apply for 566.36

I don't see the antifreeze issue in that log. The DX11BACKEND errors in the logs may be a redherring, I get these in my logs as well and are common to other users. About the web browsers etc. trying turning off Hardware Accelerated Graphics (HAGS) on your PC if you haven't already. Installing the Steam version won't change anything, the Standalone and Steam versions are identical.

Not sure what 6 attributes you mean, is only 2. The config file is in Saved Games so won’t be overridden. Those config changes were also made public on some channels by ED themselves so should be safe.

The DxDiag report contains a number of LiveKernelEvent errors with error code 117. This is also indicative of corrupted GPU drivers based on internet references. The DCS log analyzer also had the following to say about the DxDiag report: Windows Error Reporting (WER) Your system crashes with Bluescreens. The following kernel-events have been detected: DPC_WATCHDOG_VIOLATION,VIDEO_TDR_TIMEOUT_DETECTED 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: c0000005 (d3d11.dll) Generic Windows or Hardware Issues 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 references you would need to open a command prompt as administrator and then run the two commands below, these are run separately and then restart your PC. dism /online /cleanup-image /restorehealth sfc /scannow

This error is normally indicative of GPU drivers issue. See https://www.digitalcombatsimulator.com/en/support/faq/startup/#3312253 for more info. Use DDU to remove your existing video cared driver and install the latest one. (Installing an older stable 566.36 driver release may also be an option). Drop another log if this is still occurring following on from that. I'd recommend removing your mods as well to ensure you're testing this with a clean base, you can put them back afterwards. This is an interesting error from the logs that repeats for this issue which I haven't seen before, a clean driver may resolve this. I'm assuming that you've made no other changes to other settings in your system, e.g. Nivida Profile Inspector, which could have triggered this? Potentially revert those as well. Failed to NVSDK_NGX_D3D11_EvaluateFeature for DLSS, code = 0xbad00002, info: N Your friend's issues are possibly completely unrelated so they should raise a separate issue and attach their logs and crash log zip to that.

Please replicate the issue and then attach your C:\Users\username\Saved Games\DCS\Logs\dcs.log file (just a text document named "dcs" if your Windows is hiding file extensions).

Not needed anymore. Natively supported in DCS now. Add the below line to your C:\Users\Saved Games\DCS\Config\autoexec.cfg file (create it if it doesn’t exist) to set the preset for DCS DLSS_Preset = "K" You can add this line as well if you don’t want DLSS applied to MFDs and HUD to keep them sharp with no ghosting for greater control. HUD_MFD_after_DLSS = true

Awesome-sauce. Yup, log analyzer tool is amazing, would have been the first thing I would have done with your log before digging in further

May be minutely GPU hit compared to using nothing at all. Yes, this is “hidden” away (should have been better documented in release notes). The second option is not everybody wants DLSS for MFDs due to the ghosting it can cause with cursors etc on radar screens and other things. I reckon it’s a great addition and compromise. Youre right though, it could have defaulted to K instead of C and people could override if they wanted to. The K (and J) presets are going to be a little less performant than some others.

The autoexec.cfg file is just flat lines, v.s. a lua like syntax, so just the below: DLSS_Preset = 'K' HUD_MFD_after_DLSS = true

Can you also enable the debug flag in Vaicom and the VA window will then show when the tx button is pressed and released. With DCS running, but viewing the VA window, can you see if holding down the mic button and talking shows the tx press line, but doesn’t show the tx release line until you finish talking and release it…or if the release is being triggered immediately.

I’m away for a couple of days so can’t dig in too much right now sorry. Can you confirm that you don’t have the radios bound to your hotas in the DCS controls settings for that plane. Based on that log for 80bytes the stop command looks to be occurring at the same time, or a few milliseconds after the start command. Can you drop a screenshot of your VA Vaicom profile that is expanded to show all the press and release plugin actions for your tx buttons. Can you also let me know which plane and tx button you’re using On a side note, in your last couple of commands you won’t need (and VA won’t recognize) using the sender in the command, eg Enfield11

No longer required either. Add the below line to your C:\Users\Saved Games\DCS\Config\autoexec.cfg file (create it if it doesn’t exist) to set the preset for DCS DLSS_Preset = "K" You can add this line as well if you don’t want DLSS applied to MFDs and HUD to keep them sharp with no ghosting for greater control. HUD_MFD_after_DLSS = true

Based on your comment I’m assuming you have set up a Meta developer account then and have hand tracking enabled. The drop-down will only display the Hands option if you are in VR and in the actual game, ie not from within the launcher or 2d. Is this the case?

Follow the steps in the link @Art-J provided. There is also steps for enabling the hud overlay to display the preset, Ive never used NVCleanInstall but that might be fine instead. There are other versions of the NVPI which may enable that overlay as well. If it still doesn’t work then drop a screenshot of the things you’re changing on the Nvidia Profile Inspector, including the selected profile.