Tango777 Posted March 23 Posted March 23 It started with Windows Defender seeing the F-14 as a Trojan virus. So I simply made the DCS folder as an exclusion in Windows Defender, and the F-14 error message went away upon DCS startup. However, when I ran DCS Repair in "Check all files" mode it found that the F-14 file was a 0 byte file, so I clicked on the option of deleting it. Problem might be solved, but don't know if I can fly it or any other aircraft, because: In DCS, when I move the mouse to Instant Action, Mission, or Settings (etc.) for example, it takes DCS almost 5 seconds to acknowledge that I am pointing at it. I then click on it and it takes another 5 seconds for DCS to acknowledge the actual mouse click. Then, after that, DCS crashed to the desktop. My NVidia driver is 572.42. I know other users are experiencing the same problem in the forums regarding the F-14 issue, but I could not find a post like this one. Any help would be most appreciated. i7-13700F - 32GB DDR5 RAM - NVIDIA GeForce RTX 4060Ti 16GB - 2TB NVMe SSD - Windows 11
Czar66 Posted March 23 Posted March 23 17 minutes ago, Tango777 said: I know other users are experiencing the same problem in the forums regarding the F-14 issue, but I could not find a post like this one. There are a few threads open about this on this forum section. Remove all your mods and see if the problem resolves. Rename your DCS folder in 'saved games' to DCS_Old and try to access the menu and launch a mission. If it is resolved with this, it is some of the mods you're using. I have only the A-4 mod and Tacview so I know those two are not causing it. I saw some post talking about the Su-30 mod. Best of luck. Hopefully it is an easy fix with removing mods for the time being. 1
Tango777 Posted March 23 Author Posted March 23 1 hour ago, Czar66 said: There are a few threads open about this on this forum section. Remove all your mods and see if the problem resolves. Rename your DCS folder in 'saved games' to DCS_Old and try to access the menu and launch a mission. If it is resolved with this, it is some of the mods you're using. I have only the A-4 mod and Tacview so I know those two are not causing it. I saw some post talking about the Su-30 mod. Best of luck. Hopefully it is an easy fix with removing mods for the time being. Thank you for the response but I do not have any mods. i7-13700F - 32GB DDR5 RAM - NVIDIA GeForce RTX 4060Ti 16GB - 2TB NVMe SSD - Windows 11
sleighzy Posted March 23 Posted March 23 45 minutes ago, Tango777 said: Thank you for the response but I do not have any mods. Repeat the crash and then attach your DCS logs. You may have a dcs-<timestamp>.zip file from the crash, attach that as well. And when you say crash to desktop did DCS display a message that it crashed, or Windows just closed it? If Windows just closed it then run the Windows DxDiag tool, save the report, and attach that here as well. 1 AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
Tango777 Posted March 25 Author Posted March 25 On 3/23/2025 at 12:09 AM, sleighzy said: Repeat the crash and then attach your DCS logs. You may have a dcs-<timestamp>.zip file from the crash, attach that as well. And when you say crash to desktop did DCS display a message that it crashed, or Windows just closed it? If Windows just closed it then run the Windows DxDiag tool, save the report, and attach that here as well. I figured out what the problem was. The NVidia driver was updated and now everything runs as it should. 2 i7-13700F - 32GB DDR5 RAM - NVIDIA GeForce RTX 4060Ti 16GB - 2TB NVMe SSD - Windows 11
Recommended Posts