Istari6 Posted February 2 Posted February 2 (edited) 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. Edited February 2 by Istari6 1
MAXsenna Posted February 2 Posted February 2 @Istari6 A repair will not touch Saved Games, so for a temporary solution, you can rename the DCS Saved Games folder. (There can be corrupted files there, and forgotten mods). Also make sure your pagefile is set to 32768MB if you have 32GB RAM or less. Another trick is to exclude the DCS installation folders and Saved Games in your Anti-Virus solution. 1 1
rob10 Posted February 2 Posted February 2 This seems to be the common error in your logs. Can't say I've seen it before (at least not enough times in a log that it stood out): 2025-02-02 03:33:21.981 ERROR EDCORE (Main): Failed to set thread's affinity mask (id:18884 priority:13). Error:87 That's way beyond my knowledge level, so I can't really suggest anything in relation to it. The other thing seems to be this: WARNING BACKENDCOMMON (7840): Need to reprocess [DDS] image '/textures/Deck_Normal.dds'. Reason: Conversion requires - expanded pixel size, setting alpha to known value. Source is an 8:8:8 (24bpp) format ... which is more common but I can't remember what it suggests right at the moment. I'd agree with @Flappie that renaming your "Saved games" would be a good starting point. Definitely seems to be some questionable files hiding somewhere 1
sleighzy Posted February 2 Posted February 2 You attached log files still show parked cores. Were they taken after this? I so then you may need to look at a registry key for this. Disable core isolation and disable core parking. The logs also do not contain a DCS crash, so this is potentially Windows "killing" it vs. DCS itself. Run the Windows DxDiag tool, save the report, and then drop that here as well. AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
Istari6 Posted February 3 Author Posted February 3 18 hours ago, MAXsenna said: @Istari6 A repair will not touch Saved Games, so for a temporary solution, you can rename the DCS Saved Games folder. (There can be corrupted files there, and forgotten mods). Also make sure your pagefile is set to 32768MB if you have 32GB RAM or less. Another trick is to exclude the DCS installation folders and Saved Games in your Anti-Virus solution. Thanks - I would have never thought of wiping out the old Saved Games folder. I did rename it tonight, and so far had a 45 min missions without a crash. It'll take awhile to reset up all the old bindings, graphical settings etc, but promising so far. I need to fly some more time before I can confirm problem fixed, but optimistic so far! I'll do a search on the forum to see if there's any way to read out the old Graphics settings, etc from the old data. 8 hours ago, sleighzy said: You attached log files still show parked cores. Were they taken after this? I so then you may need to look at a registry key for this. Disable core isolation and disable core parking. The logs also do not contain a DCS crash, so this is potentially Windows "killing" it vs. DCS itself. Run the Windows DxDiag tool, save the report, and then drop that here as well. I restored the basic Windows 11 power settings, thinking that unparking the CPU cores might have contributed to the problem. That's why they still show as parked. I am trying the approach of wiping out the old Saved Games folder and seeing if that restores stability. If I get another crash, will definitely get that Windows DxDiag report. Appreciate the quick responses so far. 1
Istari6 Posted February 3 Author Posted February 3 (edited) 9 hours ago, sleighzy said: You attached log files still show parked cores. Were they taken after this? I so then you may need to look at a registry key for this. Disable core isolation and disable core parking. The logs also do not contain a DCS crash, so this is potentially Windows "killing" it vs. DCS itself. Run the Windows DxDiag tool, save the report, and then drop that here as well. OK after some more testing, just had another CTD, probably 15 minutes into a mission. This is after renaming my Saved Games folder and then going through and manually setting up options again. The only files I brought back over to my new Saved Games folder were a mission for testing, and my F-14 Kneeboard. Same pattern as before. Mission seems to be going fine, then just crash to desktop. DCS just seems to close, but no popup messages, nothing. I'm just back to my Windows desktop without a clue what happened. Here's the DCS log from the crash tonight and the Windows DxDiag report. Does this provide any clues? DCS - Crash #1 020225.txt DxDiag_020225.txt Edited February 3 by Istari6 1
sleighzy Posted February 3 Posted February 3 (edited) 16 minutes ago, Istari6 said: OK after some more testing, just had another CTD, probably 15 minutes into a mission. This is after renaming my Saved Games folder and then going through and manually setting up options again. The only files I brought back over to my new Saved Games folder were a mission for testing, and my F-14 Kneeboard. Here's the DCS log from the crash tonight and the Windows DxDiag report. Does this provide any clues? DCS - Crash #1 020225.txt 173.85 kB · 0 downloads DxDiag_020225.txt 145.82 kB · 0 downloads The DCS log analyzer for this ones shows a corrupt file as well. I don't know if this was previously corrupt and the deletion of Saved Games you did earlier helped clear it up at the time. Config File Corruption Delete Saved Games\DCS\MissionEditor and try again. Some additional notes as well, note the reference to the core parking. Verify that this is configured correctly in Windows: Game Mode disabled Hardware accelerated GPU scheduling disabled Core Isolation disabled And disable Core Parking, which is currently enabled. The DxDiag shows primarily app crashes for DCS. There are however two in there for LiveKernelEvent with a code of 141. This is normally indicative of a GPU issue. You could try reinstalling your GPU drivers, may need to use DDU to cleanup the old one. There are other Microsoft help references around the LiveKernelEvent 141 and some additional steps, but start with the above first. Edited February 3 by sleighzy 1 AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
MAXsenna Posted February 3 Posted February 3 1 hour ago, Istari6 said: It'll take awhile to reset up all the old bindings Hi! Everything @sleighzy said. And you can copy back the config\input folder to restore all your bindings. Could you check the Windows EventViewer log, to see if the crash is recorded, and what the error is?
Istari6 Posted February 3 Author Posted February 3 3 hours ago, sleighzy said: Config File Corruption Delete Saved Games\DCS\MissionEditor and try again. Some additional notes as well, note the reference to the core parking. Verify that this is configured correctly in Windows: Game Mode disabled Hardware accelerated GPU scheduling disabled Core Isolation disabled And disable Core Parking, which is currently enabled. OK, done the following: * Deleted Saved Games\DCS\MissionEditor * Game Mode OFF (it was ON) * Hardware accelerated GPU scheduling OFF (it was ON) * Updated the NVIDIA driver from 566.36 to 572.16 Figured I'd give this a go first before doing Core Isolation and disabling Core Parking. -> CTD again, but more info below... 3 hours ago, MAXsenna said: Hi! Everything @sleighzy said. And you can copy back the config\input folder to restore all your bindings. Could you check the Windows EventViewer log, to see if the crash is recorded, and what the error is? Based on this, I pulled the Windows EventView log, which I'd never used before. Interesting - it is seeing the DCS Application crash, with error codes. See screenshot below, along with newest DCS log file and DxDiag after latest crash. With this info from Windows EventView, does this help narrow down what the cause could be? Nice to finally have some information to work with instead of a mysterious CTD! DxDiag_02032025.txt DCS Crash #1 Feb 3 2025.log
Istari6 Posted February 3 Author Posted February 3 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. 1
Flappie Posted February 3 Posted February 3 Hi, the Event Viewer won't say much. It's better to open your latest crash .zip file (you'll find it in your Saved Games/DCS.../Logs folder) and edit the dcs.log file it contains. Here's a troubleshooting guide. Please attach the whole zip here, we'll see if we can help you. 1 ---
MAXsenna Posted February 5 Posted February 5 Hi, the Event Viewer won't say much. It's better to open your latest crash .zip file (you'll find it in your Saved Games/DCS.../Logs folder) and edit the dcs.log file it contains. Here's a troubleshooting guide. Please attach the whole zip here, we'll see if we can help you.True! I suggested the EventViewer in case something external crashed. That's how I fixed my Nvidia issue.@Istari6 This probably won't help, but try to run DCS.exe from the bin folder and not the bin-mt. Sent from my SM-A536B using Tapatalk
Istari6 Posted February 5 Author Posted February 5 (edited) On 2/3/2025 at 2:49 PM, Flappie said: Hi, the Event Viewer won't say much. It's better to open your latest crash .zip file (you'll find it in your Saved Games/DCS.../Logs folder) and edit the dcs.log file it contains. Here's a troubleshooting guide. Please attach the whole zip here, we'll see if we can help you. OK gotcha. Sorry for delay in responding, had a busy work schedule the last few days. Just had a chance to fire up DCS to reproduce the issue, and sure enough, crash within 5 min of mission start. See how short the DCS.log is for how quickly these CTDs happen. What else can I provide to help isolate the issue? BTW - I did follow the troubleshooting guide you linked, and I'm definitely category "C: DCS Crashes during a mission" and I'm the first category inside C, "There's no such line". dcs.log 19 hours ago, MAXsenna said: True! I suggested the EventViewer in case something external crashed. That's how I fixed my Nvidia issue. @Istari6 This probably won't help, but try to run DCS.exe from the bin folder and not the bin-mt. Isn't the non-MT version basically retired at this point? Edited February 5 by Istari6
silverdevil Posted February 5 Posted February 5 1 hour ago, Istari6 said: Isn't the non-MT version basically retired at this point? officially it is the other way around. ST is what is being deprecated. currently the DCS.exe in both folders are the same. 1 hour ago, Istari6 said: What else can I provide to help isolate the issue? look in the same folder you got the DCS.LOG from and grab the latest zip file. it will be named similar to dcs.log-20241001-214432.zip. it will be named with a date code. AKA_SilverDevil Join AKA Wardogs Email Address My YouTube “The MIGS came up, the MIGS were aggressive, we tangled, they lost.” - Robin Olds - An American fighter pilot. He was a triple ace. The only man to ever record a confirmed kill while in glide mode.
MAXsenna Posted February 6 Posted February 6 Isn't the non-MT version basically retired at this point? Yes. But for some strange reason, it should not happen, as both bin folders are now identical. I did get different results when running one or the other. It's totally unexplainable to me. Sent from my SM-A536B using Tapatalk
Istari6 Posted February 6 Author Posted February 6 (edited) 13 hours ago, silverdevil said: look in the same folder you got the DCS.LOG from and grab the latest zip file. it will be named similar to dcs.log-20241001-214432.zip. it will be named with a date code. Attached below. The "good" news is that this CTD problem is so frequent that I can easily create additional files if we need more examples. The strange thing is that I had a mission the other day with friends flying the P-51D that went for almost an hour without any CTDs, but F-14 or F-16 and I get CTD within usually 10 min, sometimes less. I've done full Repair multiple times on my DCS installation, and even renamed the Saved Games folder to try to eliminate any corrupt files. dcs.log-20250203-225439.zip Edited February 6 by Istari6
Flappie Posted February 6 Posted February 6 This crash seems to be linked to your Varjo device: your device gets unplugged, then plugged again, then DCS crashes. 2025-02-03 22:54:27.714 INFO VISUALIZER (Main): [14:54:27.752][Info ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_VISIBLE->XR_SESSION_STATE_SYNCHRONIZED session=2158809808400 time=1000051232682532000 2025-02-03 22:54:27.714 INFO VISUALIZER (Main): [14:54:27.752][Info ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_SYNCHRONIZED->XR_SESSION_STATE_VISIBLE session=2158809808400 time=1000051232682535400 2025-02-03 22:54:27.714 INFO VISUALIZER (Main): [14:54:27.752][Info ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_VISIBLE->XR_SESSION_STATE_FOCUSED session=2158809808400 time=1000051232682537900 2025-02-03 22:54:29.216 INFO APP (Main): Device unplugged: [HID] HID-compliant vendor-defined device 2025-02-03 22:54:29.303 INFO APP (Main): Device unplugged: [USB] USB Input Device 2025-02-03 22:54:29.324 INFO APP (Main): Device unplugged: [USB] USB Serial Device (COM5) 2025-02-03 22:54:29.363 WARNING LOG (5780): 1 duplicate message(s) skipped. 2025-02-03 22:54:29.363 INFO APP (Main): Device unplugged: [HID] HID-compliant vendor-defined device 2025-02-03 22:54:29.384 INFO APP (Main): Device unplugged: [USB] USB Input Device 2025-02-03 22:54:29.404 INFO APP (Main): Device unplugged: [USB] Generic USB Hub 2025-02-03 22:54:29.425 INFO APP (Main): Device unplugged: [USB] USB Serial Device (COM7) 2025-02-03 22:54:29.447 INFO APP (Main): Device unplugged: [HID] HID-compliant vendor-defined device 2025-02-03 22:54:29.468 INFO APP (Main): Device unplugged: [USB] USB Composite Device 2025-02-03 22:54:29.488 INFO APP (Main): Device unplugged: [USB] Varjo Headset Audio 2025-02-03 22:54:29.615 WARNING LOG (5780): 5 duplicate message(s) skipped. 2025-02-03 22:54:29.615 INFO APP (Main): Device unplugged: [HID] HID-compliant consumer control device 2025-02-03 22:54:29.636 INFO APP (Main): Device unplugged: [USB] USB Composite Device 2025-02-03 22:54:29.656 INFO APP (Main): Device unplugged: [HID] HID-compliant vendor-defined device 2025-02-03 22:54:29.717 WARNING LOG (5780): 2 duplicate message(s) skipped. 2025-02-03 22:54:29.717 INFO APP (Main): Device unplugged: [USB] USB Composite Device 2025-02-03 22:54:29.739 INFO APP (Main): Device unplugged: [USB] Generic USB Hub 2025-02-03 22:54:29.760 INFO APP (Main): Device plugged: [USB] Generic USB Hub 2025-02-03 22:54:30.294 WARNING LOG (5780): 1 duplicate message(s) skipped. 2025-02-03 22:54:30.294 INFO APP (Main): Device plugged: [USB] USB Composite Device 2025-02-03 22:54:30.322 INFO APP (Main): Device plugged: [USB] USB Serial Device (COM7) 2025-02-03 22:54:30.349 INFO APP (Main): Device plugged: [HID] HID-compliant vendor-defined device 2025-02-03 22:54:30.390 INFO APP (Main): Device plugged: [USB] USB Composite Device 2025-02-03 22:54:30.420 INFO APP (Main): Device plugged: [HID] HID-compliant vendor-defined device 2025-02-03 22:54:30.596 WARNING LOG (5780): 2 duplicate message(s) skipped. 2025-02-03 22:54:30.596 INFO APP (Main): Device plugged: [USB] USB Composite Device 2025-02-03 22:54:30.655 INFO APP (Main): Device plugged: [USB] Varjo Headset Audio 2025-02-03 22:54:30.868 WARNING LOG (5780): 5 duplicate message(s) skipped. 2025-02-03 22:54:30.868 INFO APP (Main): Device plugged: [HID] HID-compliant consumer control device 2025-02-03 22:54:30.904 INFO APP (Main): Device plugged: [USB] USB Input Device 2025-02-03 22:54:30.940 INFO APP (Main): Device plugged: [HID] HID-compliant vendor-defined device 2025-02-03 22:54:30.978 INFO APP (Main): Device plugged: [USB] USB Serial Device (COM5) 2025-02-03 22:54:31.044 WARNING LOG (5780): 1 duplicate message(s) skipped. 2025-02-03 22:54:31.044 INFO APP (Main): Device plugged: [USB] USB Input Device 2025-02-03 22:54:31.078 INFO APP (Main): Device plugged: [HID] HID-compliant vendor-defined device 2025-02-03 22:54:39.428 INFO EDCORE (Main): signal caught: 'Abnormal termination' 2025-02-03 22:54:39.431 INFO EDCORE (Main): try to write dump information 2025-02-03 22:54:39.433 INFO EDCORE (Main): # -------------- 20250203-225439 -------------- 2025-02-03 22:54:39.433 INFO EDCORE (Main): DCS/2.9.12.5336 (x86_64; MT; Windows NT 10.0.26100) 2025-02-03 22:54:39.434 INFO EDCORE (Main): C:\WINDOWS\System32\KERNELBASE.dll 2025-02-03 22:54:39.434 INFO EDCORE (Main): # FFFFFFEA (Unknown exception code) at 00007ffcbfd7837a 00:00000000 2025-02-03 22:54:39.435 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World\bin-mt;', symOptions: 532, UserName: 'cjpet' 2025-02-03 22:54:39.435 INFO EDCORE (Main): OS-Version: 10.0.26100 () 0x100-0x1 2025-02-03 22:54:39.436 INFO EDCORE (Main): 0x00000000000c837a (KERNELBASE): RaiseException + 0x8A 2025-02-03 22:54:39.436 INFO EDCORE (Main): 0x0000000000006b59 (edCore): ed::current_exception_stack_trace + 0x279 2025-02-03 22:54:39.437 INFO EDCORE (Main): 0x00000000000c1ee9 (ucrtbase): raise + 0x1D9 2025-02-03 22:54:39.437 INFO EDCORE (Main): 0x00000000000a5011 (ucrtbase): abort + 0x31 2025-02-03 22:54:39.437 INFO EDCORE (Main): 0x00000000002dc29f (vrclient_x64): HmdSystemFactory + 0x1BE6EF 2025-02-03 22:54:39.437 INFO EDCORE (Main): 0x00000000002f9749 (vrclient_x64): HmdSystemFactory + 0x1DBB99 2025-02-03 22:54:39.437 INFO EDCORE (Main): 0x00000000000a3538 (vrclient_x64): xrNegotiateLoaderRuntimeInterface + 0x50108 2025-02-03 22:54:39.437 INFO EDCORE (Main): 0x00000000000a2d72 (vrclient_x64): xrNegotiateLoaderRuntimeInterface + 0x4F942 2025-02-03 22:54:39.437 INFO EDCORE (Main): 0x000000000027497e (VarjoOpenXR): Varjo::VrActionController::pollOpenVREvents + 0x7E 2025-02-03 22:54:39.437 INFO EDCORE (Main): 0x00000000002748ca (VarjoOpenXR): Varjo::VrActionController::pollEvent + 0x1A 2025-02-03 22:54:39.437 INFO EDCORE (Main): 0x00000000002e0d18 (VarjoOpenXR): Varjo::IVrSession::pollEvent + 0x368 2025-02-03 22:54:39.437 INFO EDCORE (Main): 0x000000000030343b (VarjoOpenXR): vxrPollEvent + 0x5B 2025-02-03 22:54:39.437 INFO EDCORE (Main): 0x00000000002f9c99 (VarjoOpenXR): vxrSubmitDebugUtilsMessageEXT + 0x2A19 2025-02-03 22:54:39.437 INFO EDCORE (Main): 0x00000000001b0b0f (Visualizer): TransformComponent::validatePositionsTree + 0x2B0EF 2025-02-03 22:54:39.437 INFO EDCORE (Main): 0x000000000019b026 (Visualizer): TransformComponent::validatePositionsTree + 0x15606 2025-02-03 22:54:39.438 INFO EDCORE (Main): 0x0000000000122c2a (Visualizer): try_get_HMDcontroller_pos + 0xB7DA 2025-02-03 22:54:39.438 INFO EDCORE (Main): 0x000000000010e0ff (Visualizer): HMD::processUserInput + 0x1F 2025-02-03 22:54:39.438 INFO EDCORE (Main): 0x000000000093a620 (DCS): SW + 0x44DB30 2025-02-03 22:54:39.438 INFO EDCORE (Main): 0x00000000008f4a94 (DCS): SW + 0x407FA4 2025-02-03 22:54:39.438 INFO EDCORE (Main): 0x00000000008f61c3 (DCS): SW + 0x4096D3 2025-02-03 22:54:39.438 INFO EDCORE (Main): 0x0000000002266183 (DCS): AmdPowerXpressRequestHighPerformance + 0x11D117F 2025-02-03 22:54:39.438 INFO EDCORE (Main): 0x0000000000cd5eb2 (DCS): SW + 0x7E93C2 2025-02-03 22:54:39.438 INFO EDCORE (Main): 0x000000000002e8d7 (KERNEL32): BaseThreadInitThunk + 0x17 2025-02-03 22:54:39.576 INFO EDCORE (Main): Minidump created. 1 ---
Istari6 Posted February 6 Author Posted February 6 (edited) 3 hours ago, Flappie said: This crash seems to be linked to your Varjo device: your device gets unplugged, then plugged again, then DCS crashes. Huh! I knew I was having a problem with the Varjo power cord connection at the headset getting loose, but typically if there would be an issue, it would lose power when I was putting it on. The HMD would go dark, then come back on, the IPD would reset and if DCS was already running, it would crash with the blue error popup message (conventional DCS crash). I'd have to restart DCS if that happened, but it seemed stable once it was on my head. I never had the issue where the HMD went dark and reset once it was on. So it sounds like it's only momentarily losing power during flight, not enough to reset the whole Varjo HMD, but enough to throw off DCS and trigger a CTD. Wild. Thanks for the information! Let me try to better secure that power connection at the headset and see if the CTD goes away. Then I can return and mark this as the "Solution". It's awesome to finally have a lead to pursue in fixing this really annoying problem. Edited February 6 by Istari6
Istari6 Posted February 8 Author Posted February 8 Unfortunately, I'm back. I don't think the Varjo power cable is the cause of the CTD issue I've been having lately. Yes, if the Varjo headset cable gets loose in the socket, I get a "conventional" crash in DCS. I think that's what you're seeing in those .ZIP files. It's a standard DCS crash where the screen freezes, I get a blue pop-up within DCS telling me DCS crashed, and I have to restart. In these cases, the Varjo headset goes black, then comes back on, and the lenses reset for IPD. This is a separate issue from the CTDs I'm having. I've known about those and I know what to do to avoid them (don't bump the cable while putting on the headset). But I've now secured the power cord connection tightly, fired up my standard test mission just now, and very quick CTD within minutes of mission start. No black view in headset, no IPD resizing, etc. I don't think the Varjo is losing power. To support this, I'm noticing that when I look in the DCS Log folder, I see the DCS.log file with data from today right up the moment of the crash. But there's no updated ZIP file. The .ZIP file in the Log folder is back from 2/3/25, I think that's the data dump that happens when the headset gets unplugged. How else can I proceed in isolating a cause? Here's the DCS log from just now, and the .ZIP file that's in the same Log folder. As you can see, one is updated from today's hard CTD, the other is an older .ZIP file, not updated after today's crash. dcs.log dcs.log-20250203-225439.zip
Istari6 Posted February 8 Author Posted February 8 (edited) To confirm my theory that it was the power cord issues you were seeing in the other log, I ran DCS, then deliberately pulled the plug on my Varjo Aero. Sure enough, I get the files below, with the section you were quoting above. This is not the cause of the CTD. Losing power to the Varjo Aero causes a conventional DCS crash (blue pop up windows) with the logs generated below. I know how to avoid this problem. There's something else going that's making DCS almost unplayable for me. What I'm having are sudden CTDs in mission with no DCS .ZIP file generated, nothing showing in the DCS log. It looks like Windows is killing DCS for some reason in the EventView log, but I don't know how to diagnose the cause. Quote 2025-02-08 03:35:35.369 INFO EDCORE (Main): # -------------- 20250208-033535 -------------- 2025-02-08 03:35:35.370 INFO EDCORE (Main): DCS/2.9.12.5336 (x86_64; MT; Windows NT 10.0.26100) 2025-02-08 03:35:35.370 INFO EDCORE (Main): C:\WINDOWS\System32\KERNELBASE.dll 2025-02-08 03:35:35.370 INFO EDCORE (Main): # FFFFFFEA (Unknown exception code) at 00007ffe1ef3837a 00:00000000 2025-02-08 03:35:35.371 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World\bin-mt;', symOptions: 532, UserName: 'cjpet' 2025-02-08 03:35:35.371 INFO EDCORE (Main): OS-Version: 10.0.26100 () 0x100-0x1 2025-02-08 03:35:35.372 INFO EDCORE (Main): 0x00000000000c837a (KERNELBASE): RaiseException + 0x8A 2025-02-08 03:35:35.373 INFO EDCORE (Main): 0x0000000000006b59 (edCore): ed::current_exception_stack_trace + 0x279 2025-02-08 03:35:35.374 INFO EDCORE (Main): 0x00000000000c1ee9 (ucrtbase): raise + 0x1D9 2025-02-08 03:35:35.374 INFO EDCORE (Main): 0x00000000000a5011 (ucrtbase): abort + 0x31 2025-02-08 03:35:35.374 INFO EDCORE (Main): 0x00000000002dc29f (vrclient_x64): HmdSystemFactory + 0x1BE6EF 2025-02-08 03:35:35.374 INFO EDCORE (Main): 0x00000000002f9749 (vrclient_x64): HmdSystemFactory + 0x1DBB99 2025-02-08 03:35:35.374 INFO EDCORE (Main): 0x00000000000a3538 (vrclient_x64): xrNegotiateLoaderRuntimeInterface + 0x50108 2025-02-08 03:35:35.375 INFO EDCORE (Main): 0x00000000000a2d72 (vrclient_x64): xrNegotiateLoaderRuntimeInterface + 0x4F942 2025-02-08 03:35:35.375 INFO EDCORE (Main): 0x000000000027497e (VarjoOpenXR): Varjo::VrActionController::pollOpenVREvents + 0x7E 2025-02-08 03:35:35.375 INFO EDCORE (Main): 0x0000000000275297 (VarjoOpenXR): Varjo::VrActionController::syncActions + 0x117 2025-02-08 03:35:35.375 INFO EDCORE (Main): 0x00000000002f4a36 (VarjoOpenXR): vxrSyncActions + 0x2F6 2025-02-08 03:35:35.375 INFO EDCORE (Main): 0x00000000002f9ef9 (VarjoOpenXR): vxrSubmitDebugUtilsMessageEXT + 0x2C79 2025-02-08 03:35:35.375 INFO EDCORE (Main): 0x00000000001b0d92 (Visualizer): TransformComponent::validatePositionsTree + 0x2B372 2025-02-08 03:35:35.375 INFO EDCORE (Main): 0x0000000000192adc (Visualizer): TransformComponent::validatePositionsTree + 0xD0BC 2025-02-08 03:35:35.375 INFO EDCORE (Main): 0x0000000000122961 (Visualizer): try_get_HMDcontroller_pos + 0xB511 2025-02-08 03:35:35.375 INFO EDCORE (Main): 0x000000000010e10b (Visualizer): HMD::processUserInput + 0x2B 2025-02-08 03:35:35.375 INFO EDCORE (Main): 0x0000000000914d2b (DCS): SW + 0x42823B 2025-02-08 03:35:35.375 INFO EDCORE (Main): 0x000000000093a652 (DCS): SW + 0x44DB62 2025-02-08 03:35:35.375 INFO EDCORE (Main): 0x00000000008f4a94 (DCS): SW + 0x407FA4 2025-02-08 03:35:35.375 INFO EDCORE (Main): 0x00000000008f61c3 (DCS): SW + 0x4096D3 2025-02-08 03:35:35.375 INFO EDCORE (Main): 0x0000000002266183 (DCS): AmdPowerXpressRequestHighPerformance + 0x11D117F 2025-02-08 03:35:35.375 INFO EDCORE (Main): 0x0000000000cd5eb2 (DCS): SW + 0x7E93C2 2025-02-08 03:35:35.375 INFO EDCORE (Main): 0x000000000002e8d7 (KERNEL32): BaseThreadInitThunk + 0x17 2025-02-08 03:35:35.675 INFO EDCORE (Main): Minidump created. dcs.log dcs.log-20250208-033535.zip Edited February 8 by Istari6
silverdevil Posted February 8 Posted February 8 7 hours ago, Istari6 said: It looks like Windows is killing DCS for some reason in the EventView log, but I don't know how to diagnose the cause. i do not see it mentioned to test your hardware. i suggest to strip as much external hardware from your rig as possible to see if a component is causing the issue. reattach them one by one to see if the issue comes back. if you cannot get through a mission without a crash, then it is something deeper. if so, test memory. i always suggest taking out the dimms and reseat them. maybe they are just a little loose now. also move them to opposite slots. and take half of them out. see if a specific dimm is bad. another idea is to run chkdsk. lastly remove any overclocking from ram and gfx. even factory overclock. if windows is 'killing' the dcs process, there is likely a hardware issue. oh and this was an issue with some other users. check your power supply. even to the point of plugging directly to wall socket. @Flappie and @MAXsenna will remember this fun one. keep at it. we will figure this out. 1 AKA_SilverDevil Join AKA Wardogs Email Address My YouTube “The MIGS came up, the MIGS were aggressive, we tangled, they lost.” - Robin Olds - An American fighter pilot. He was a triple ace. The only man to ever record a confirmed kill while in glide mode.
Istari6 Posted February 8 Author Posted February 8 6 hours ago, silverdevil said: i do not see it mentioned to test your hardware. i suggest to strip as much external hardware from your rig as possible to see if a component is causing the issue. reattach them one by one to see if the issue comes back. if you cannot get through a mission without a crash, then it is something deeper. if so, test memory. i always suggest taking out the dimms and reseat them. maybe they are just a little loose now. also move them to opposite slots. and take half of them out. see if a specific dimm is bad. another idea is to run chkdsk. lastly remove any overclocking from ram and gfx. even factory overclock. if windows is 'killing' the dcs process, there is likely a hardware issue. oh and this was an issue with some other users. check your power supply. even to the point of plugging directly to wall socket. @Flappie and @MAXsenna will remember this fun one. Thanks for the additional ideas! I've run a full 3DMark Steel Nova stress test on my entire system, passed 99.0%, no issues identified. I've also done a complete MemTest86+ check on my RAM modules, which passed. So i don't think it's the factory-set overclocking or RAM. On your point about hardware, I did some more testing last night, and I was able to run an entire mission without any CTDs in "flat screen" (2D) mode. This is a mission that is particularly unstable for CTDs, almost always crashes in the first 5-10 minutes. So I'm now thinking it has something to do with the chain of layers to my Varjo Aero headset. I generated more CTDs last night, and plugged the Windows Event Log data into ChatGPT (o3-mini-high) for suggestions. Remember, I'm not getting any error message from DCS and no crash log generated - it just crashes straight to Windows. The DCS log just terminates, no "minidump" or other information. So I'm left trying to use the Windows Event View logs to find out why it's crashing. Interestingly, ChatGPT says the following: What the Logs Tell Us Faulting Module & Exception Code Faulting Module: edCore.dll (a core part of DCS’s engine) Exception Code: 0xc00000fd This code typically means stack overflow, which generally indicates that a function (or a chain of functions) is calling itself repeatedly until the stack runs out of space. Fault Offset: 0x0000000000182e37 This is the location within edCore.dll where the error occurs. Without symbol files (debug information) from Eagle Dynamics, it’s hard to pinpoint the exact function. However, the fact that it’s within a core engine DLL suggests the problem is internal to DCS when executing a particular code path. VR-Only Occurrence You mentioned that DCS runs fine in “flat screen” (2D) mode and only crashes in VR mode. This strongly suggests that the crash (i.e., the stack overflow) is triggered by the VR code path inside DCS. In many cases, the VR rendering or related logic (possibly interfacing with the OpenXR runtime or Varjo-specific routines) may be executing a recursive or improperly bounded call sequence. ------------------- So now I'm trying to figure out what are the "variables" to check in the VR pathway? I also fly IL-2 on occasion, haven't had any crashes there, but that runs in SteamVR. So I'm thinking it might be something in the OpenXR pathway that's causing these crashes, as DCS is the only VR application I'm using with OpenXR. 1. I've updated my NVIDIA drivers to the latest (572.16) after the CTDs started. That hasn't changed anything. 2. I haven't touched anything with OpenXR. Is there a file, driver, or library here that should be updated? 3. I've updated Varjo Base to the latest, will test today. Anything else that I can try to fix in the DCS OpenXR VR pathway? 1
Istari6 Posted February 8 Author Posted February 8 (edited) ADDENDUM: Doing a Google search using the search term "0xc00000fd exception Code DCS" cued me to two threads here in the forum: -- - These sound like exactly the same kind of problem I'm having, crashing hard within a few minutes of mission start. The 2nd thread mentions finding and deleting an extra TrackIR profile. That doesn't help me as I don't use TrackIR. The first thread mentions reseating RAM modules, I can try that - although RAM did pass MemTest86+ just fine. But the author in the first post mentions that he the following: Quote "CRASHING ISSUE FIXED! Removed & reinstalled memory sticks back into different slots. Deleted temp files, optimise & rebooted. Went from acute Chaos to Karma in one afternoon. Rig running better than ever & DCS smooth as silk. Crazy man." Does anyone know what "Deleted temp files, optimise and rebooted" means? What temp files is he referring to? I'm happy to try reseating the RAM, but would love to follow all the steps that worked for him. Edited February 8 by Istari6
Nate--IRL-- Posted February 8 Posted February 8 (edited) I went through a painful few months of something similar, DCS crash ing or a full reboot after 10 to 30 mins in DCS. I was ready to splash out on a new GPU as I'd a feeling that was the issue. By chance I noticed in windows that my RAM voltage was 0.1 or 0.2v above what was set in the BIOS. My Motherboard was slightly over-volting my RAM, compared to what was set by SPD. So I manually set the voltage a little below what it should be, and hey presto, my system has been rock solid for over a year. This is not to say this is your issue, but rather a suggestion to double and triple check everything is as it should be with all parts of the system and BIOS Nate Edited February 8 by Nate--IRL-- Ka-50 AutoPilot/stabilisation system description and operation by IvanK- Essential Reading
Recommended Posts