dlder Posted November 2, 2024 Posted November 2, 2024 This is a bit strange imho... I have 64 GB RAM 32 GB Pagefile 24 GB GPU memory And after changing from one map to the other (I'm not sure which; from Nevada to Persian Gulf maybe?) the game crashed. The log is attached. (line 2.680) How is that possible? Could it be the pagefile layout? C = 256mb (minimum for the small Windows dump file, if an error accurs) D = 32 GB Any ideas, tips welcome! I only have 26GB of free SSD space on C, so I can't use the main drive for the page file.... dcs.log 1 OpenXR-Switcher: to easily switch OpenXR runtimes as well as en-/disable API layers Kneeboard-Picture-Viewer: my own take on a Kneeboard for a 2nd monitor, that acts more or less as a better picture viewer. F-15CX mod: my own take on a simple F-15C upgrade English Avionics with Native Betty: you can now have English HUD on non US planes and still hear the native Betty!
sleighzy Posted November 2, 2024 Posted November 2, 2024 (edited) I've dropped your log into the DCS log analyzer and it had the following to say. Note that you do not have a 32Gb page file like you've said, the log analyzer says your page file is 258Mb. Make sure you only have one page file configured for your entire system, and that it is set to a custom size of 32768 for the initial and max values. Click set, apply, and restart your PC. Your System ran out of Memory Increase RAM or page file Your GPU ran out of VRAM Reduce Terrain Textures and Shadows. Doublecheck your page file. Tuning Tips Turn off SSLR. Enable Full Screen mode. Turn off SSAO. There are also some errors with sound scripts, I don't know if related to the ECHO19_CORE_ULTIMATE mod you're using. Edited November 2, 2024 by sleighzy AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
dlder Posted November 3, 2024 Author Posted November 3, 2024 Thanks, I'll try to get some more info if/why the GPU Ram is really filling up. Seems weird. But I did fear that I should only set 1 pagefile, though it shouldn't matter in any way. OpenXR-Switcher: to easily switch OpenXR runtimes as well as en-/disable API layers Kneeboard-Picture-Viewer: my own take on a Kneeboard for a 2nd monitor, that acts more or less as a better picture viewer. F-15CX mod: my own take on a simple F-15C upgrade English Avionics with Native Betty: you can now have English HUD on non US planes and still hear the native Betty!
dlder Posted November 3, 2024 Author Posted November 3, 2024 12 hours ago, sleighzy said: I've dropped your log into the DCS log analyzer Just a quick question: just for this reason, I've joined the DCS discord, dropped the log into the "dcs-log-analyzer" chat and... nothing happened. How does this work, so that I can help myself next time? OpenXR-Switcher: to easily switch OpenXR runtimes as well as en-/disable API layers Kneeboard-Picture-Viewer: my own take on a Kneeboard for a 2nd monitor, that acts more or less as a better picture viewer. F-15CX mod: my own take on a simple F-15C upgrade English Avionics with Native Betty: you can now have English HUD on non US planes and still hear the native Betty!
dlder Posted November 6, 2024 Author Posted November 6, 2024 I will from now on start DCS with hwinfo64 in logging mode to get to the bottom of this. I do have some more info because of the first 2 logs: I currently have the i7-14700, that means 8 pCores / 16 pThreads + 12 eCores/Threads and all threads will be used by the game! But for whatever reason, the eCores more then the pCores, except for the 1 main thread, which for me is running on pCores 4, Thread 0 Yes, the GPU memory will get filled up until..., well, its full. But that's by design, right? After loading the game, about 15 GB of GPU Mem are used. This will gradually fill to 22.9 - 23.7 GB of the 24 GB available. So, if the game erroneously fills up over this point, then that would point to a potential ingame problem of not removing old data from the video memory (if the game really would need more RAM, because of my chosen settings, it would fill up pretty much when loading a mission -> this happens when playing No Man's Sky in VR with the Pimax Crystal without DLSS, so I know what that looks like^^). What I do see though, that in the 2 gameplay sessions I logged, is that the Physical Memory (RAM) is used 46-59% (of 64 GB). That's no where near overfilling. -> that's also, why the page file isn't used at all, just as it should be! BUT: what does get filled up pretty high is the Virtual Memory: the 1st session isn't that wild, Vmem sits at up to 71%. But on the 2nd session, this reached a whooping 94%! It is rather easy to circumvent any such memory overflows, if one exits the game every few hours or at least, when changing the map. What I remember, Syria especially needs a lot of RAM, so I'm gonna play around that map next time and see what the numbers are then. OpenXR-Switcher: to easily switch OpenXR runtimes as well as en-/disable API layers Kneeboard-Picture-Viewer: my own take on a Kneeboard for a 2nd monitor, that acts more or less as a better picture viewer. F-15CX mod: my own take on a simple F-15C upgrade English Avionics with Native Betty: you can now have English HUD on non US planes and still hear the native Betty!
Lange_666 Posted November 6, 2024 Posted November 6, 2024 On 11/3/2024 at 9:52 AM, dlder said: Just a quick question: just for this reason, I've joined the DCS discord, dropped the log into the "dcs-log-analyzer" chat and... nothing happened. How does this work, so that I can help myself next time? Just copy/paste your log file into the dcs-log-analyzer and press enter. If you don't see anything happen, make sure you're on the bottom of that page. Pagefile: There is no need to set up a page file on the main (C) drive. I have mine set up on its own partition on another drive. Works fine. Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind pedals, TrackIR4, Rift-S, Elgato Streamdeck XL. Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!
dlder Posted November 6, 2024 Author Posted November 6, 2024 52 minutes ago, Lange_666 said: Pagefile Well, as my logs show: pagefile is never in use. Sure, I gotta check with Syria too, then I can be certain. 53 minutes ago, Lange_666 said: Just copy/paste your log file Hm, yeah, tried that. Waited quite some time too. I'll give it another go if it crashes again. OpenXR-Switcher: to easily switch OpenXR runtimes as well as en-/disable API layers Kneeboard-Picture-Viewer: my own take on a Kneeboard for a 2nd monitor, that acts more or less as a better picture viewer. F-15CX mod: my own take on a simple F-15C upgrade English Avionics with Native Betty: you can now have English HUD on non US planes and still hear the native Betty!
dlder Posted November 19, 2024 Author Posted November 19, 2024 So, after analyzing a lot of hwinfo logs: no pagefile is ever in use (as it should be, as long as RAM is available). But rarely the GPU memory (24 GB! What?) seems to fill up, causing a crash. This usually only happens when switching modules and maps, without quitting DCS. -> for me, this looks like a buffer overflow issue of the game. Old cached data isn't removed from the GPU Ram (fast enough). I mean, if this happens with a 4090, this should be a huge issue for smaller cards, one might think? Or is it, that this is so much memory, that the game says: Ah, it's fine, enough memory here! OpenXR-Switcher: to easily switch OpenXR runtimes as well as en-/disable API layers Kneeboard-Picture-Viewer: my own take on a Kneeboard for a 2nd monitor, that acts more or less as a better picture viewer. F-15CX mod: my own take on a simple F-15C upgrade English Avionics with Native Betty: you can now have English HUD on non US planes and still hear the native Betty!
Recommended Posts