Search the Community

Been flying DCS since 2016. I've really enjoyed being "along for the ride" as it's progressed from the days of "cotton ball" clouds, practically no DLC campaigns and the Caucasus to what we have today. But in over 8 years, I've never had the problems I've started having in the last few weeks. Regular CTD without any error messages, sometimes rendering the game completely unplayable. Tonight I was trying to teach my brother the Tomcat (he's a new brand DCS player), and it crashed 12 times in a single hour . I've had no problems playing other games besides DCS, but just in case it's my system, I've tried the following tests: * 3DMark Stress Test "Steel Nomad" - 99.0% pass. No issues identified. * MemTest86+ - "Pass" x 2 Within DCS, I've done the following: * Removed all mods * Done multiple "slow" Repairs Still getting regular CTDs after the above steps. I've captured multiple DCS logs just tonight, one after each crash. Will include a sampling of three below, I have many more. None have any information in the final lines saying "try to write dump information". What else can I do to fix this? DCS - Crash #1.log DCS - Crash #3.log DCS Crash - #14.log ADDENDUM: The only other item that's changed lately that might be related (?) is per Reflected's YouTube video "DCS 2.9 Optimization Guide in 2D and VR (Quest 2)" where he recommended unparking CPU Cores to remove stutters. I used the utility recommended in his video here: "https://coderbag.com/programming-c/disable-cpu-core-parking-utility". I used it to unpark cores, but after the CTDs, I closed the utility and reset my Windows 11 Power settings to "Balanced" and then "Best Performance", which should have reset CPU Core parking to defaults.

Been pulling my hair out this past month trying to figure out why I can’t seem to get DCS to run stable on my 14900k build and *I THINK* I figured it out. I tested this fix on the Syria map in single and multiplayer before sunrise, during sunrise and full on day time setting. The fix was incredibly basic and something that is so easy to miss. If you did not do this then it may be your RAM, your MEMORY. If you’re like me and built the system yourself or even if you had your system pre built then the numerical order of the ram in the “ram kit” that you bought may be incorrect. On 2 sticks it may not be an issue but either way, as a rule you should check the stickers on the sticks to ensure you have the number one stick in the primary dimm slot (check manual to find out what it is) and the number 2 stick in the secondary dimm slot. In my case I bought 2x32Gb memory of Corsair Vengeance 64Gb kit @6400Mhz. A week after finishing my build I decided that even though I’m running a dual channel board (MSI MPG Z790 Edge Wifi DDR5) I wanted to double it up to 128Gb. I did what everyone does and found the best deal at the time on Amazon, bought the exact same make, model, speed rating and timings as the first kit and installed it. In my mind I was like; - “same sticks so who cares what order they go in, right?” - BIG MISTAKE! DCS would run stable for a week or so and then the second there would be a Windows 11 update or Nvidia driver update or ANY update, DCS would crash and I’m back to square one troubleshooting. Yesterday, after watching one video on YouTube, I finally did what I hate doing and opened up my case, pulled out all 4 sticks of RAM and sure enough they all had a numerical order and none of them were in the right slot. I separated the 2 RAM kits and placed the fist kit in the primary and secondary dimm slots in their correct numerical order as per the numbering order in the stickers and placed the second kit in the third and fourth slot accordingly. NO MORE CRASHING. By this time I was a little burnt out trying for weeks to figure out why my game kept crashing but I was keen to stress test and jumped into a Syria Hoggit server to test. In the F-18 I pressed F2 a bunch of times to toggle between jets and clicked on the mirrors about 40 times as they were also causing crashes. I pressed F2 on my jet and jerked the mouse around to see if the quick rendering would cause a crash and then in circles around the jet to see if that caused a crash. Descended to 500 feet over Cyprus and did the same thing. Basically no matter what I did I could not trigger a CTD. Boy was I happy . All of your RAM sticks in a kit of two or more will be paired together at the factory and the stickers will reflect it IN SOME WAY. You will need to take a close look at the stickers to figure out which stick is the first one and which stick is second. I’m my case the first kit was had a bunch of identical numbers and letters all over the place but I noticed one had one had a 3 and the other had a 4. That’s all I needed to know that the #3 stick goes into the primary dimm slot and the 4 in the secondary slot. The other kit bought on Amazon had different stickers both identical but I saw -1 on one and -2 on the other. Same deal; Placed the -1 stick in the third slot and the -2 in the fourth slot. Now I’m running all 4 sticks at 5400 CL36 stable and no issues *so far*. Check it out if your’re close to throwing your computer out the window And to anyone who’s going to chime in and tell me that this is common knowledge. Dude, it ain’t! Common knowledge is that if you bought a 2 stick kit you can place them in any order you want. I can’t think of a single build video or article that has mentioned numerical order as per factory listed info on the stickers until I came across a Linus Tech tips video (ugh, I know I know but in this case it helped). Peace

Two CTDs in multiplayer, logs attached DxDiag.zip

All, I've been trying to troubleshoot a serious recurring CTD problem. It's brought my DCS playing almost entirely to a halt, very frustrating. MAXSenna and sleighzy have been great about jumping into help with ideas. One suggestion they made was to capture the Windows EventView log after these CTDs. I'd never used EventView before, but sure enough, it's capturing each of my DCS CTDs, even though DCS isn't throwing any error messages. Here's what I see in the most recent CTD. Does the community here have any ideas on how I can use this information to help isolate a cause? I'm just totally stuck on where to go next to get DCS working again.