Tango777

I figured out what the problem was. The NVidia driver was updated and now everything runs as it should.

Thank you for the response but I do not have any mods.

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.

Thank you.

Is there a video processing software that you could recommend? Thank you.

I am using OBS Studio to record and it does an amazing job. However, I have noticed that if I set it to 43:18 or 16:9 with roughly the same duration, that the videos' file sizes are still huge and they obviously take forever to upload to YouTube. Any tricks of the trade out there to shorten upload times?

I do not have any mods. The Mods folder in the Saved Games\DCS subdirectory have two folders titled aircraft and tech, and both are empty.

Some guys that I fly with in a squadron are experiencing some of the same issues, and other problems as well in DCS more recently as well. Sometimes we reboot 3 times until everything works as it should. After running sfc /scannow there are now no more problems found on the entire drive.

It only happens after clicking on Multiplayer in DCS.

Well, that was a fast test. The moment DCS began populating the different servers after clicking on Multiplayer, DCS crashed and Windows locked up again. Something now has to do with the Multiplayer aspect of DCS because that is when it crashes. Attached are the latest DxDiag and DCS log. DxDiag.txt dcs.log

Thank you both for your replies! Much appreciated! My replies are: @Kanelbolle I do have the latest BIOS for the mobo. I have never touched the Intel settings, so I do use the Intel default settings. However, according to the MSI Center, there is an update available for the Intel chipset drivers. The reason I am reluctant in running that install is because it took forever for the BIOS update to finally work correctly and update. @sleighzy I run MSI Center which has a feature called FROZR AI Cooling before running a sim, DCS or FSX and one other program. The people at MSI, a few months ago, recommended that I run it because they claim that it does a very good job in running the fans on the computer, balancing software so that a sim will run at its optimal level regarding heating, etc. while I run any simulator, but it should only interface with the fans you can see, in other words all of the fans except: the CPU liquid cooler pump fan, the CPU fan, and the video card fans (the video card fans should not run all of the time but they do regardless of running FROZR AI or not) throttle up from their current state as needed. FROZR AI should not interface with the power supply, but for the time being I will leave FROZR AI off and see what happens. It does not have an effect when running Microsoft Flight Sim X. The reason that program has a history of ctd is because I was running an addon for FSX before starting FSX first as I should, if I start FSX first and then start the addon program FSX has no problems. So that ctd one is on me. What is important to note is that when DCS crashes, so does Windows. It is the only program that crashes Windows at the same time. When FSX ctd, I simply restart FSX immediately and it runs smoothly. I just ran the two commands in CMD as administrator as you suggested, so let's see how that effects things as well. After running sfc /scannow it did find corrupt files and it said that it successfully repaired them. Will keep you posted.

Well it happened again and I was not even flying yet. I was just looking at a map. Could it be a RAM issue? Attached are both the latest log and the dxdiag report. dcs.log DxDiag-Report.txt

I do not have any custom mods as the only things I have downloaded are missions from the DCS website, but I do not download missions that require custom mods. I just looked and in the Mods folder in the Saved Games\DCS subdirectory there are two folders titled aircraft and tech, but both are empty. The F-14 files (wherever they are located) have never been touched as I never touch any files in any DCS directory. I have ran the slow repair, but that has never helped anything. This problem with DCS does not only happen while flying the F-14. But I will do as you say and report back.

This began after two updates ago. Not the most recent update, but the update before the most recent update. Sometimes this happens only 10 minutes into the sim. DCS and Windows both freeze and the only option I have is to hold the power button down on the computer. The computer does not even respond to Ctrl Alt Del. After I reboot the computer, I can usually run DCS with no problems. Windows does not crash with any other software from my computer. The log from the most recent crash is attached. My computer specs are: Windows 11 Home 64-bit 13th Gen Intel(R) Core(TM) i7-13700F 32 GB RAM @ 2 x 16 GB DDR5-4800 16 GB RTX 4060 Ti (running the latest NVidia driver 565.90) 2 TB SSD CPU cores: 16, threads: 24, System RAM: 32579 MB, Pagefile: 32768 MB Any help would be greatly appreciated. dcs.log

I downloaded the update that was made available today and I tested the Phoenix, it now works in both TWS & STT. Using the multi thread version.

The bugs reporting sub-forum for Heatblur said that the following is a ED problem: With the latest DCS update, something with the Phoenix and Sparrow missiles are now very wrong. I have flown several missions and out of 36 Phoenix missiles that I fired, only 1 hit the target - every other Phoenix just continued flying straight and then either turned into the empty sky regardless of the type of lock. Technically one of them turned way off track by turning at least 45 degrees between me and my target which was 12 miles away, and then it downed a friendly that was half that distance away to my 2 o'clock. The Sparrows just fly straight and don't even turn toward the target regardless of the type of lock. The ranges at time of launching both of these missiles were all between 5 and 20 miles. Before the latest DCS update, the Phoenix and Sparrow missiles were pretty accurate. The Sidewinders still work as they always have, so at least they work. I am running into this problem in the Multi Thread version of DCS, but not the "Normal" version of DCS.

Got it.

I should have posted this here - my mistake: With the latest DCS update, something with the Phoenix and Sparrow missiles are very wrong. I just flew several missions and out of 24 Phoenix missiles that I fired, only 1 hit the target - every other Phoenix just continued flying straight and then either turned into the empty sky regardless of the type of lock. Well technically one of them turned between me and my target 12 miles away, then turned and downed a friendly. The Sparrows just fly straight and don't even turn toward the target regardless of the type of lock. The ranges at time of launching these missiles were all between 5 and 20 miles. Before the latest DCS update the Phoenix and Sparrow were pretty accurate. The Sidewinders still work as they always have, so at least they work. I am running into this problem in the Multi Thread version of DCS, but not the "Normal" version of DCS.

With the latest DCS update, something with the Phoenix and Sparrow missiles are very wrong. I just flew several missions and out of 24 Phoenix missiles, only 1 hit the target - every other Phoenix just continued flying straight and then either turned into the empty sky or turned and hit a friendly. The Sparrows just fly straight and don't even turn toward the target. The ranges at time of launching these missiles were all between 5 and 25 miles. Before the latest DCS update the Phoenix and Sparrow were pretty accurate. The Sidewinders still work as they always have, so at least they work. I am running into this problem in the Multi Thread version of DCS, but not the "Normal" version of DCS.

When DCS did not hang on me, that mission was not quite as slow to load as in your video but it did take a while for the textures on the ship to load as yours did.

That is it. What is strange is that I flew that mission several times and it did not begin to make DCS hang until this past weekend.

Ok. Understood on the pagefile. I downloaded the mission from DCS downloads website, and the name of it is Hormuz_Islands_Dispute_CAP_Supercarrier_save_2.

No MODS in the mission or anywhere in DCS. Please remember that I have 32 GB of ram and I still have 32 GB of ram pagefile.

Thanks for the advice. I found out that this only happens now with one mission, which is weird because that mission used to load just fine. Do I leave the pagefile setting at 32 GB or do I switch it back to where Windows controls it automatically?

It hangs at the exact same spot. And when I say it hangs, it reaches the point of "Wait for pooled tasks - 1" and it just sits there. I let DCS sit there for over 20 minutes and it eventually tells me that DCS has quit responding when I move the mouse. dcs.log dcs.log.old