Akula

I had to disable hyperthreading for my 14900k and it solved literally every crash I’ve had. It knocked me down to 16 physical cores so it’s not too bad. I can’t even tell the difference in performance and I have actually been TRYING to trigger a crash. All mods work. Spamming the F2 map only caused a crash on MP but that’s because i was forcing the video card to create and recreate images faster than i was hitting F2 which it could not do, hence the crash. That’s it. Play the game normally and I don’t have a single issue.

Last week I disabled Hyperthreading in the BIOS and POOF! No more problems. Try it and see if that helps. You can re-enable them at any time so just do it as a test. If you have no issues at least you have this as a temporary fix until DCS gets their $hit together. I re-enabled it to test (no issues since lat update) but I might just keep it off as it still leaves me with 16 good cores and I'm not constantly apologizing to my friends for crashing in the middle of a mission lol. I don't trust DCS's multi thread support. It's getting better but it is not where it needs to be.

Need FULL SPECS, exact brands and models to help further. You’ve only provided half.

Reading through this discussion. Here is what I would do if I were you. I would go back to the barebones basics. NO RIVA TUNER, NO MSI AFTERBURNER, NO KAPERSKY, NO OVGME OR MOD MANAGING SOFTWARE. To get rid of these programs 100% you will need to remove them using Revouninstaller. Its removes all traces of a program done to the registry. I use it all the time. Uninstall all of those apps and use Revouninstaller to uninstall DCS. Make sure to back up your HOTAS bindings, missions and liveries before uninstalling. restart windows and then shut down and start it up again to wipe everything out (overkill but at least this way you know you’re reset). Try another game and see how it runs. If everything looks good and runs as it should reinstall DCS but ONLY DCS and ONE JET, just one module. NOTHING ELSE! No maps, no mods, NOTHING. Set your system settings to get the graphics the way you want and then shut down DCS and to be safe, restart the computer (overkill but I would do it to guarantee the settings take full effect and the jet you installed is solidly installed). if you have no issues and can fly a mission, land and exit the game back into windows good for you. You have established a baseline. Now one by one, over the next few days, add a jet or map; JUST ONE AT A TIME! Restart and then test. If it goes well add another module or map. Try a mod and see how that goes but do it ONE AT A TIME. The goal is to test add, test, add, test, add. All that to isolate what is causing the issue. Lastly, DO NOT INSTALL SUPER CARRIER! We already know it’s causing issues so leave that for last. Doing it this way will isolate the cause and get you on the right path vs trying a bunch of stuff at the same time and not knowing what’s causing the problem. I have MSI afterburner and turn it off as well as HWINFO64 before playing DCS. Good luck.

According to your log, your cores are parked. Try unparking your cores and see how that impacts you. You’ll need to Google how to do this. Very easy

To anyone running a Z790 board with a 14900k and cannot get DCS to run stable. As a last ditch effort, try disabling hyperthreading and see if that solves it. I finally did it after a month of troubleshooting and despite trying to trigger a CTD or a BSOD, DCS will NOT crash. It’s super stable so far. Looking forward to finally getting to max out my system settings and using mods again in DCS to make it look as good as it should given the components I’m now using. Quite honestly I have not noticed a drop in performance across all Windows 11 apps and programs. I’m also still running 16 cores with HT disabled so not missing hyperthreading at all.

Just a little update since I can relate to all these crashes as all my crashes were similar. BSOD due to memory issues according to windows 11 on a 14900k. I was also getting the same “soft” CTDs which freeze the game for a few seconds and then it all disappears and you’re back at the desktop as if you had pressed ESC and clicked on “quit to desktop”. So far the only solid solution I have found is to disable hyperthreading which may not be practical for you since you’re running an i7 but I will add that with hyperthreading disabled I COULD NOT trigger a CTD or BSOD no matter what I tried in the game. I even maxed out all my settings and yeah the FPS dropped by a lot but the mission kept chugging along. It seems that whatever DCS did in the patch in September to “improve multithreading support” they completely ruined with the update in mid October. For me running on an i9 14900k with 128Gb RAM and an RTX3090 on a Z790 board, the update released on October 2nd fixed my game and I wasn’t getting any CTDs or BSODs. On top of that I didn’t have to use Process Lasso to restrict threading nor did I have to set affinity or priority. That October 2nd update was THE BEST update DCS has released in a long time and then they F-ed it up again with the next patch. Very frustrating and quite honestly a motivation killer. Have a look at my other posts as I have been troubleshooting and researching the hell out of these problems. Even with hyperthreading disabled I’m running 16 cores so DCS is smooth as butter. Not holding my breath but I hope DCS goes back to fixing the enhanced threading support they say they released with the October 2nd patch and messed up with the ones that followed.

Update.... This fix did help but it did NOT solve my CTD issues. So after AAAAALLLLL the troubleshooting I did with this rig This final measure has prevented all my crashing to date. The 14900k is so threaded with so many fake cores that the solution was to: - Disable Hyperthreading in the BIOS Now I'm running (what looks like) 16 physical cores and despite my efforts I cannot trigger a CTD. Still testing so I will keep you up to date. SIDE NOTE, THIS site helped me rule out many possible causes for CTD's. Definitely worth a read.

You’re welcome. You should be OK especially if it’s just two sticks. This fix is a little outdated for two sticks and more of an issue when 2 kits of 2x32Gb technically identical BUT unmatched kits of DDR5 as in my case. Hence my inclination to just revert back to 64Gb since recent testing has exposed more CTDs.

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

I’m starting to wonder the same thing. I don’t even think a system restore will remove it since MS really hates it when you try to go back to what works.

This is getting ridiculous. I have ensured that: - All drivers are up to date - DCS has been repaired (the slow way) - No mods in the game whatsoever - BIOS up to date. - All DCS folders pertaining to the game (except the downloads folder) has been added to the Defender Exclusion list. - DCS profile in Nvidia has been untouched except for the setting "Prefer Maximum performance" - Windows Recall disabled. Like, I feel like Ive done absolutely EVERYTHING to get this F-ing game to work and nothing. Crash logs don't seem to reveal much but I'll attach anyways. My GOD, DCS got it right with the patch before this and messed it up with the last one. F-ing frustrating to have to go back and forth between it running all the time and it crashing all the time. dcs.log

For those interested, here is a good walk through for disabling Windows Recall in 24H2

I’ll check and make sure I have it. I assume updating to windows build 24H2 installed it but we know that they say when some assume

So far it’s crashing due to some mods and I can live with that. Still testing in the vanilla environment. Deleting FXO and meta shaders folder before every start up to ensure it’s not the cause. for anyone experiencing crashes or BSODs in windows ELEVEN (not 10), windows Recall seems to be quite the intrusive culprit. Basically what Windows Recall does is take screenshots of your PC screen whenever it’s convenient for MS and use the data to track you and sell to third parties. This super secret program that windows makes very hard to disable and/or remove is mandatory as of update 24H2 release a few days ago but in time I’m sure we will see some way to get rid of it. Patience for now. Just Google “Windows 11 24H2 Windows RECALL” to get up to date on this and see what can be done. I’m holding off for now until more info on this app is released by independent media content creators. Not going to trust MS with this garbage app.

Thanks. DCS loaded much quicker. Fewer crashes now.

I’m running 2 NVME’s, one SSD AND 2 SATA so a lot but in testing with a friend in MP, we tried using windows defender exclusions and excluded Simmap pro, Trackir, both DCS executables and it made the largest difference. No crashing and bitter smooth no matter what I pressed. (F2, toggling through jets and land vehicles/carriers. So it seems to be better now but still testing.

Thank you everyone for your help. Quick update. I managed to narrow down this game crash after using the log analyzer in Discord (thanks ED, great tool) SSAO, SSLR and Civilian traffic was the cuplirt. for good measure I also disabled birds and DLSS. DCS is running much better and now onto more testing on an MP server. I joined one of the 4ya Syria servers and everything was perfect until I started pressing F2 to toggle through he various jets in the area. DCS crashed to desktop like I had selected Quit to Desktop before the 4th plane was fully rendered (Razbam's F-15E if that makes a difference). Attached is my crash log for this CTD but I'm thinking that it may just be because the server had so much going on that the game or my 3090 could not handle it anymore and crashed. TIA dcs.log

Yeah, sorry for not mentioning it earlier. Now that you bring it up, yes it was crashing the same way before I reinstalled Windows. The Nvidia app was before the windows clean install so it’s not a factor anymore. I thought it might be a memory or voltage issue since I’m running 5.5Gb clock speed on all Pcores and running under 1.2volts which is conservative for the 14900k but more voltage than it was getting before for 5.5Gb. All my tweaking in the BIOS didn’t work and once I installed all the drivers for the peripherals windows stopped giving me BSODs. I haven’t been back to my simpit yet but I’ll keep testing to see what it might be and see if I can get a flight out of it. Fingers crossed.

I did DDU a few times on Thursday when I first started having this issue…. It’s a longer story than you think so I’ll try to keep it short. I removed GeForce experience to try Nvidia app and DCS started crashing. I used Revo Uninstaller to removed the Nvidia App and DDU to reinstall the card drivers. DCS was still crashing. Nothing would fix it so I went down a rabbit hole trying to troubleshoot and ended up corrupting windows so badly that I had to do a clean reinstall. Total nightmare. The constant BSODs after the install, unbeknownst to me, was due to me not installing all of the proper drivers for the devices I had connected via USB so after I had figured that out, onto installing and testing DCS…… and here we are lol. All this to say it’s been done and to no avail so far. I’ll play around with my settings to see if that fixes anything but thanks for the help. Any other tips would be greatly appreciated. Dude I know what you mean. Thursday was a nightmare. Everything you did to resolve the issue, I was doing on Thursday haha! DCS is definitely a love hate relationship

Thanks for the help everyone, My mistake. I had 64Gb when I wrote that up. I've since bumped it up to 128Gb 4x32.... I've tested the memory using memtest and all 4 sticks are stable and not defective or flawed. "Memory try it" is MSI's tool that allows the layman to use 4 sticks of memory on a dual channel board and set the timings easily without having to mess about in the BIOS. It has worked perfectly so far so no reason for me to suspect the memory. The actual experience is as i have described it with the CTD being a total lock up in DCS with the mouse working if I remember correctly and it all just disappears as if I pressed "Quit to Desktop". Windows remains unaffected. DXDIAG log attached DxDiag.txt

That's weird because it did crash. No the overclock has nothing to do with it. I actually clocked it lower to get a lower voltage since my most recent posts. As for the logs not showing a crash.... It crashed. No reason for me to lie about it. I did my ramp start, rolled out on the runway and I'll either CTD as soon as I line up or shortly after takeoff. Strange that it would say "Application shutdown" if it did then it would not go into a crashlog, correct?

I had the same issue yesterday after doing a clean Windows 11 reinstall and multiple BSODs trying to run DCS. Every Google result that came back for the BSOD codes hinted a hardware issue. After multiple changes to the BIOS settings it finally dawned on me that I hadn’t yet installed all the drivers for the hardware I had connected to it. After doing that I was able to get into DCS but now struggling with a CTD that I think is linked to the 14900k and it’s threading. DCS just isn’t equipped to handle that many threads (32 on total). Waiting on replies from the CTD section.

Hi all, Just wondering if someone who knows how to read log files can chime in on mine. I had set affinity to just the physical 8 cores and still got a CTD. Tried a few more times after rebooting and same thing so any advice would be appreciated. Thanks System - March, 2024 - Windows 11 64 24H2 - Phanteks (PH-ES620PTG-DBK01) Enthoo Pro 2 Full Tower - EVGA PSU 1200W - Intel® CoreTM i9-14900K - MSI MPG Z790 EDGE WIFI - CORSAIR VENGEANCE DDR5 RAM 128GB (4x32GB) 6400MHz CL32 **downclocked** to 5400 CL36 - MSI Ventus 3X GeForce RTX 3090 OC - thermal pad upgrade, much cooler now. - SAMSUNG 49-inch Odyssey G9 Gaming Monitor | QHD, 240hz - Trackir 5 Professional Premium Head Tracking - ARCTIC Liquid Freezer III 360 A-RGB - AIO dcs.log

Does anyone know how to add buildings in maps without using the static object portion in the ME? I don’t know how to better explain this but my goal is to add buildings and infrastructure without bogging down the mission editor so that the buildings show as small black dots as seen in the populated areas in maps. if I add them as per the mission editor is would kill a mission as there would be too many static objects on the ground crippling performance.