Crash Master Posted March 25 Share Posted March 25 I've been running DCS for many years without significant problems until I did a clean install a few days ago and have not been able to get DCS to launch since. Have done multiple Uninstall/installs, cleanups, repairs (short and long), disk repairs, anything I can think of. Drivers are up to date. I did see that, even though my installation directory is D:, several files are being installed on C:, including Logs, Metashaders2, Config, etc. I've never noticed that before, is this normal? Attached logs from several attempts this morning. dcs.log-20240325-173541.zip dcs.log-20240325-160905.zip dcs.log-20240325-161630.zip dcs.log-20240325-162300.zip dcs.log-20240325-171059.zip Link to comment Share on other sites More sharing options...
Flappie Posted March 25 Share Posted March 25 (edited) Hi. I see you have 128 GB of RAM, but for some reason, the sim complains of a lack of memory: 2024-03-25 17:35:40.192 ALERT EDCORE (Main): Out of memory in ed_malloc for 4371621096 bytes. 2024-03-25 17:35:40.227 INFO EDCORE (Main): try to write dump information 2024-03-25 17:35:40.957 INFO EDCORE (Main): # -------------- 20240325-173541 -------------- 2024-03-25 17:35:40.959 INFO EDCORE (Main): DCS/2.9.3.51704 (x86_64; MT; Windows NT 10.0.22631) 2024-03-25 17:35:40.961 INFO EDCORE (Main): D:\Program Files\Eagle Dynamics\DCS World\bin-mt\edCore.dll 2024-03-25 17:35:40.963 INFO EDCORE (Main): # 80000003 BREAKPOINT at 00007ffc702c77ab 00:00000000 2024-03-25 17:35:40.965 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'D:\Program Files\Eagle Dynamics\DCS World\bin-mt;', symOptions: 532, UserName: 'PB' 2024-03-25 17:35:40.967 INFO EDCORE (Main): OS-Version: 10.0.22631 () 0x300-0x1 2024-03-25 17:35:41.015 INFO EDCORE (Main): 0x00000000000277ab (edCore): ed::fatal_out_of_memory + 0x3B I found another user with the same symptoms, but I'm not sure the problem was ever solved: You should check your RAM: Edited March 25 by Flappie Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
Crash Master Posted March 26 Author Share Posted March 26 Thanks for your response. I checked RAM and everything seems fine. Attempted another clean installation this morning and got the error message shown. Retry does nothing and cancel just takes me back to desktop. Did a cleanup and quick repair with no change. Running a slow repair right now, but that will take a while. I was at least able to get to the main DCS screen prior to today. Any ideas? Link to comment Share on other sites More sharing options...
Flappie Posted March 26 Share Posted March 26 A full repair should work. If it does not, try running both exes in ".\DCS World\distr\", one after the other. One will probably tell you that it's installed already but that's OK. Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
Crash Master Posted March 28 Author Share Posted March 28 So, the full repair worked, and I was able to run DCS with the included aircraft and terrain. I decided to start installing my modules one at a time to continue testing, and after installing the first one and testing with the different default graphic settings, performance got increasingly worse, until the load times became unbearable. I did another slow repair and tried to test again with no luck. The time from launch to main DCS screen was 16 minutes. After selecting a mission, the load process took over 30 minutes and nearly completed until it crashed. That report is attached. I also installed the exes you suggested with no noticeable change. I think today I will install on my OS drive (C:) just to see what happens. dcs.log-20240328-002535.zip Link to comment Share on other sites More sharing options...
Flappie Posted March 28 Share Posted March 28 (edited) It usually happens with antivirus software. Try and add your main DCS path ("D:\Program Files\Eagle Dynamics\DCS World\") as an exception in your antivirus. If it doesn't help, we'll search for a drive issue, because the crash looks like a drive issue: 2024-03-28 00:23:43.753 WARNING FLIGHT (Main): No taxiroad found on Tbilisi-Lochini from 65 to 73 2024-03-28 00:23:49.134 INFO APP (Main): MissionSpawn:spawnShips 16 2024-03-28 00:23:53.553 WARNING EFFECTS2 (Main): OParticleSystem: preset '' not found in 'shipTrail.lua', using default 2024-03-28 00:23:57.966 WARNING LOG (6692): 3 duplicate message(s) skipped. 2024-03-28 00:23:57.966 INFO APP (Main): MissionSpawn:spawnShips 2 2024-03-28 00:25:34.964 INFO EDCORE (2844): try to write dump information 2024-03-28 00:25:35.274 INFO EDCORE (2844): # -------------- 20240328-002535 -------------- 2024-03-28 00:25:35.276 INFO EDCORE (2844): DCS/2.9.3.51704 (x86_64; MT; Windows NT 10.0.22631) 2024-03-28 00:25:35.278 INFO EDCORE (2844): C:\Windows\SYSTEM32\VCRUNTIME140.dll 2024-03-28 00:25:35.280 INFO EDCORE (2844): # C0000006 IN_PAGE_ERROR at 00007ffd8b611404 00:00000000 2024-03-28 00:25:35.285 INFO EDCORE (2844): SymInit: Symbol-SearchPath: 'D:\Program Files\Eagle Dynamics\DCS World\bin-mt;', symOptions: 532, UserName: 'PB' 2024-03-28 00:25:35.287 INFO EDCORE (2844): OS-Version: 10.0.22631 () 0x300-0x1 2024-03-28 00:25:35.289 INFO EDCORE (2844): 0x0000000000001404 (VCRUNTIME140): memcpy + 0x114 2024-03-28 00:25:35.293 INFO EDCORE (2844): 0x000000000006f3c8 (edCore): io::MemBinaryFileR::read + 0x68 2024-03-28 00:25:35.295 INFO EDCORE (2844): 0x000000000006ecb5 (edCore): io::IBinaryFileR::readUint8 + 0x15 2024-03-28 00:25:35.300 INFO EDCORE (2844): 0x00000000000042d9 (ModelDesc): model::InstanceData::alloc + 0x9D9 2024-03-28 00:25:35.305 INFO EDCORE (2844): 0x0000000000016e01 (ModelDesc): model::RenderNode::getDamageHandle + 0x1B1 2024-03-28 00:25:35.305 INFO EDCORE (2844): 0x000000000001b270 (ModelDesc): model::RootNode::getVisArgs + 0xD50 2024-03-28 00:25:35.305 INFO EDCORE (2844): 0x000000000001c24a (ModelDesc): model::RootNode::open + 0x5FA 2024-03-28 00:25:35.305 INFO EDCORE (2844): 0x00000000000389ce (NGModel): model::NGModelLodsMT::applyMults + 0x6AE 2024-03-28 00:25:35.305 INFO EDCORE (2844): 0x0000000000036290 (NGModel): model::NGModelLodsMT::~NGModelLodsMT + 0x650 2024-03-28 00:25:35.305 INFO EDCORE (2844): 0x0000000000034fb8 (edCore): ed::this_thread::yield + 0xB38 2024-03-28 00:25:35.305 INFO EDCORE (2844): 0x0000000000049ff6 (edCore): ed::this_thread::yield + 0x15B76 2024-03-28 00:25:35.306 INFO EDCORE (2844): 0x00000000000339c1 (edCore): ed::thread::_get_current_thread_id + 0x71 2024-03-28 00:25:35.306 INFO EDCORE (2844): 0x0000000000029333 (ucrtbase): _recalloc + 0xA3 2024-03-28 00:25:35.306 INFO EDCORE (2844): 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D 2024-03-28 00:25:36.879 INFO EDCORE (2844): Minidump created. Edited March 28 by Flappie Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
Crash Master Posted March 28 Author Share Posted March 28 FYI - I had my antivirus turned off when working on it yesterday. I just installed on my OS C drive and everything works perfectly, so perhaps it is a drive issue. I'm happy to leave it there for now, but my concern is running out of room, which is why I had it installed on a separate drive by itself. I've been thinking about replacing D with an SSD anyways, so this may be the time. Ironically, I tried to uninstall DCS from D and the files were corrupted, so I couldn't access .bin or even run a repair, I can't even uninstall using Windows. Just for fun, I thought about reformatting D and simply copying the DCS files from C to D, just to see what happens. I don't mind spending the time, do you see any danger in that? Link to comment Share on other sites More sharing options...
Flappie Posted March 28 Share Posted March 28 (edited) Maybe it's just a bad SATA cable. See a previous case, here: But since I understand your D:\ drive is a HDD, then look no further. It's probably time to say goodbye to it. There's absolutely no danger copying your installation from a drive to another. I'll mark the thread as solved, but if you have some bad news, answer back and I'll remove the tag. Edited March 28 by Flappie 1 Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
Czar66 Posted March 28 Share Posted March 28 If everything else fails, before nuking any kind of hardware, delete your windows/system temporary folder. I've seen hints of it making problems relating to editor files failing to compile on mission loading while troubleshooting other problem I've encountered in DCS. My issue was unrelated to the temporary files, it was the carrier crewmen statics preventing mission loading, for further information. 1 Link to comment Share on other sites More sharing options...
Flappie Posted March 28 Share Posted March 28 Just now, Czar66 said: My issue was unrelated to the temporary files, it was the carrier crewmen statics preventing mission loading, for further information. This issue should be fixed for good with the next update. 1 Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
Czar66 Posted March 28 Share Posted March 28 2 minutes ago, Flappie said: This issue should be fixed for good with the next update. Great to know! Thanks for the info, Flappie. Link to comment Share on other sites More sharing options...
Solution Crash Master Posted March 28 Author Solution Share Posted March 28 Thanks so much for your help, Flappie. Comforting to know there are responsive, knowledgeable people here to help. 1 Link to comment Share on other sites More sharing options...
Czar66 Posted March 28 Share Posted March 28 2 hours ago, Crash Master said: Thanks so much for your help, Flappie. Comforting to know there are responsive, knowledgeable people here to help. Crash Master. You marked as solved by your own comment? What was the solution to the issue, in case anyone else with the same problem comes to see how it was fixed? Link to comment Share on other sites More sharing options...
Crash Master Posted March 29 Author Share Posted March 29 The problem is a failing drive which I have since confirmed with additional testing. 2 Link to comment Share on other sites More sharing options...
Recommended Posts