ACG_Jaydog Posted Tuesday at 08:49 PM Posted Tuesday at 08:49 PM (edited) Ever since the last update that included upload of CW Germany map, the game crashes at least 75% of the time when switching to F10 map while aircraft is starting. Additionally, it takes far too long to load missions/maps now in MP and SP . It's quite annoying and wastes too much time trying to join servers and actually get airborne. DCS ran perfectly prior to last update to version ending in 599. My specs are below. I don't know if it also an issue for 2D players, but I fly in VR using the Pimax Crystal. Motherboard: ASUS Prime Z790-V D5 (Wi-Fi) CPU: i9-14900k GPU: MSI RTX 4090 128GB RAM DDR5 4800MHz Kingston FURY Beast 1500W Corsair HX1500i (Modular) (80 Plus Platinum) Storage Set 1: 1x SSD M.2 (4TB Kingston Fury Renegade) (NVM Express) Storage Set 2: 1x SSD (4TB Samsung 870 EVO) Storage Set 3: 1x SSD M.2 (1TB Digital Storm M.2 Performance Series) (NVM Express) dcs.log-20250430-203856.zip Edited Wednesday at 08:42 PM by ACG_Jaydog adding log file
sleighzy Posted Wednesday at 12:30 AM Posted Wednesday at 12:30 AM Recommend you attach your DCS log file, and any dcs.log.<timestamp>.zip files when this occur. Will help narrow down the cause, possible solution, and other tuning advice. AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
ACG_Jaydog Posted Wednesday at 09:03 PM Author Posted Wednesday at 09:03 PM This constant game crashing basically makes it unplayable. ED really needs to hurry and find a fix. I can't be the only one having this issue since the last update.
sleighzy Posted Wednesday at 10:21 PM Posted Wednesday at 10:21 PM Dropped your log into DCS log analyzer, sounds like you have a few issues going on there. If you haven't already then general first steps: Try a slow repair of. the game, verify files in Steam Delete Saved Games\DCS\fxo and metashaders2 and try again. Next, delete %LOCALAPPDATA%\TEMP\DCS and try again. Critical items from both DCS and your Windows DxDiag report: Windows Error Reporting (WER) Kernel Events The following kernel-events have been detected: BUGCODE_USB3_DRIVER Remove any overclocking (including XMP). Run SFC and DISM to check your Windows. Check for any updates of your BIOS or chipset drivers. Application Errors DCS.exe: c0000005 (Effects.dll), was hung for 14.47s and killed, was hung for 41.06s and killed Memory Timing Issues Remove any overclocking (XMP) from your RAM. Generic Windows or Hardware Issues Remove any overclocking (including XMP). Run SFC and DISM to check your Windows. Check for any updates of your BIOS or chipset drivers. For the SFC and DISM commands, run a command prompt as administrator as run the two separate commands below: dism /online /cleanup-image /restorehealth sfc /scannow Additional advice. Note that upgrading to Windows with offer better support for DCS and use of hybrid P/E cores. I would highly recommend that. Upgrade your OS to Windows 11 to better support your CPU, or disable cores 16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31 in Windows or Process Lasso You have core parking turned on in your system. Install something like ParkControl and disable core parking. This has resolved this issue for a number of users, especially those upgrading to Windows 11 as well Verify that this is configured correctly in Windows: Game Mode disabled Hardware accelerated GPU scheduling disabled AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
ACG_Jaydog Posted Thursday at 05:01 PM Author Posted Thursday at 05:01 PM 18 hours ago, sleighzy said: Dropped your log into DCS log analyzer, sounds like you have a few issues going on there. If you haven't already then general first steps: Try a slow repair of. the game, verify files in Steam Delete Saved Games\DCS\fxo and metashaders2 and try again. Next, delete %LOCALAPPDATA%\TEMP\DCS and try again. Critical items from both DCS and your Windows DxDiag report: Windows Error Reporting (WER) Kernel Events The following kernel-events have been detected: BUGCODE_USB3_DRIVER Remove any overclocking (including XMP). Run SFC and DISM to check your Windows. Check for any updates of your BIOS or chipset drivers. Application Errors DCS.exe: c0000005 (Effects.dll), was hung for 14.47s and killed, was hung for 41.06s and killed Memory Timing Issues Remove any overclocking (XMP) from your RAM. Generic Windows or Hardware Issues Remove any overclocking (including XMP). Run SFC and DISM to check your Windows. Check for any updates of your BIOS or chipset drivers. For the SFC and DISM commands, run a command prompt as administrator as run the two separate commands below: dism /online /cleanup-image /restorehealth sfc /scannow Additional advice. Note that upgrading to Windows with offer better support for DCS and use of hybrid P/E cores. I would highly recommend that. Upgrade your OS to Windows 11 to better support your CPU, or disable cores 16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31 in Windows or Process Lasso You have core parking turned on in your system. Install something like ParkControl and disable core parking. This has resolved this issue for a number of users, especially those upgrading to Windows 11 as well Verify that this is configured correctly in Windows: Game Mode disabled Hardware accelerated GPU scheduling disabled That's odd that it recommends removing overclocking. That is pretty much standard XMP for intel. I wont remove XMP. That is nonsense. I have had that running since day 1. I have deleted fxo and metashaders repeatedly and the game verified in steam without errors. Like I said, I never had this issue until the last update t version ending in 599. 1
sleighzy Posted Thursday at 10:41 PM Posted Thursday at 10:41 PM 5 hours ago, ACG_Jaydog said: That's odd that it recommends removing overclocking. That is pretty much standard XMP for intel. I wont remove XMP. That is nonsense. I have had that running since day 1. I have deleted fxo and metashaders repeatedly and the game verified in steam without errors. Like I said, I never had this issue until the last update t version ending in 599. That’s fine then, standard response from the analyzer when it sees memory timing issues so may be unrelated. Have a look at the other items and see if those help with what you’re experiencing. 1 AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
ACG_Jaydog Posted Thursday at 10:54 PM Author Posted Thursday at 10:54 PM 9 minutes ago, sleighzy said: That’s fine then, standard response from the analyzer when it sees memory timing issues so may be unrelated. Have a look at the other items and see if those help with what you’re experiencing. Yeah, I will keep messing with it. I did roll back my nvidea driver two previous versions ago before the patch to see if that is linked. I'll see if that is it or maybe mess with the mhz a little. Seems like every patch, people always get set back in performance for one reason or another. I had been pretty much unaffected until now.
Recommended Posts