DrSparrius

Just as an additional bit of information to this, I had a few good games after seemingly fixing the issue as per above, only for the crashes to return later today. I updated to the most recent open beta build, had an unremarkable flight without CTDs, only for the CTDs to return again, almost according to the same pattern I've described before. Only they seemed to occur much earlier than previously, even striking while my plane was still on the carrier whereas before it was usually something that happened 10-15 mins into gameplay. Note that I was not running on the MT exe (I got flickering lights all over my textures when I tried that in multiplayer). After the first CTD, I tried essentially bottoming out my graphics settings again but to no avail. So I reset the DCS saved games folder (backed up the old one), and that appears to have fixed the issue again. Also, I adjusted the graphics settings a bit further, they're no longer bottomed out, some stuff is back on (for example SSAA or whatever it's called). In any case, I've attached the log files from the previous CTDs for your viewing pleasure. dcs.log dcs.log.old

It appears that one of the above fixes (I applied all of them at once, including extending the firewall exceptions) solved the issue. It was probably down to moving the saved games folder to E: and changing the pagefile to E: Thank you again!

Alright i) the graphics settings are already pretty much bottomed out, except for cockpit textures, where I need that extra resolution to be able to read the gauges on my monitor (it's not a particularly high resolution or big monitor). Elsewise, pretty much the lowest settings, and the game runs smooth in terms of FPS except for the crashes. ii) this computer originally had two drives, C (237 GB SSD) and D (1 TB HDD). Windows, and the user data, are stored on that small SSD drive. Now, DCS was originally installed on the D (1 TB HDD) drive, but I moved it to a fresh, new E (1 TB SSD) drive last summer, to improve performance. And true enough, performance was much improved after that move. Additionally, some crashes, which were similar to the ones I experience now, disappeared after moving (removing and then installing again) DCS from the D to the E drive. However, all DCS save game/user files still remain on that original, small C SSD drive, where there's roughly 50 GB of free space out of that 237 GB volume. The pagefile size is set at roughly 32 GB per the instructions in that video, for the C drive, whereas it is disabled for the D and E drives. iii) (as of this writing, I haven't tried this yet) iv) No, I was able to run the Instant Action Cold Start single player mission with no crashes, and generally better performance v) (as of this writing, I haven't tried this yet) I'll get back to you with more information once I've done point iii) and v), but I thought the above information might be useful at this stage, anyway

Ran a repair, but unfortunately the game crashes again, according to the same pattern. Here is the latest log file. Once again, the issue appears to be memory related. It is so strange though, that the issue should come back, having been fixed once already. Oh well, any other ideas? dcs.log

Hi folks! You might remember me for the thread, 'recurring crashes', which I posted in january: To reiterate, I got reliable CTDs 10-15 mins into gameplay. The game ran smooth elsewise. I was provided with a solution, which amazingly solved the issue for approximately two months (basically until a game session today), however now the CTDs are back with a vengeance and following the exact same pattern as before. The logs, which I have provided below, specify memory issues as the underlying cause. Going into the virtual memory settings, they are set as recommended since last time (32768 - 32768 for the fastest drive, and disabled for the other drives). My system specs: NVIDIA GeForce GTX 1080 Intel Core i7 8700K CPU @ 3.70 GHz 3.70 GHz 16 GB RAM MSI Z730-A PRO motherboard The game is installed on an SSD. dcs.log dcs.log.old

Thanks! That appears to have fixed it

Oh okay. Here are the two most recent .log files then, I think! I mistakenly thought the .zips were what I was supposed to attach dcs.log dcs.log.old

Hello, I have just about had it with these CTDs now. Approximately 10-15 minutes into any flying (note! I may spend any amount of time on the ground, not flying, without having a CTD), I will invariably run into a CTD. The CTD appears different from time to time, sometimes there is a simple CTD without any preceding symptoms and sometimes my monitor goes into standby mode and the sound repeats for a few seconds, before I am returned to the desktop, with DCS gone. The game runs smoothly before the CTD and I usually run on lower settings (reflecting my hardware, see below). Last summer I noted the CTDs tended to happen on the busier multiplayer servers, and in particular (for some reason) around the Forrestal Class carrier. I also had issues with long loading times, stuttering and general instability. Back then, DCS was installed on an HDD, so I bought and installed an SSD towards the end of the summer and subsequently reinstalled the game on the SSD. The CTDs vanished, as did the stuttering, and the load times improved by several orders of magnitude. However, a couple of patches in, towards november I think, the CTDs returned. There is no stuttering or any other issues, however. I'm running on a rather old (prebuilt MSI Codex) system: NVIDIA GeForce GTX 1080 Intel Core i7 8700K CPU @ 3.70 GHz 3.70 GHz 16 GB RAM MSI Z730-A PRO motherboard I have attached the two most recent crash reports. Note that I couldn't find the .log file, only the .crash file, for the most recent crash on january 27. There are several entries of "access violation" in the crash files in general, there is another .crash file from january 10 saying # C0000005 ACCESS_VIOLATION at 00007FFECE9FFD91 00:00000000 instead of at EAD5F8F1. dcs.20230127-190152.crash dcs.log-20230110-222319.zip