Jump to content

Crashing on first mission of F-18C campaign


Go to solution Solved by sleighzy,

Recommended Posts

Posted
1 hour ago, nickexists said:

This crash is happening consistently for me about 1 minute after takeoff in the 1989 campaign. I tried updating my graphics driver, but that doesn't seem to matter.

hello,

first thing is you may be crashing because of low memory

2025-06-29 20:50:18.725 INFO    APP (Main): CPU cores: 8, threads: 16, System RAM: 32373 MB, Pagefile: 7680 MB

add a pagefile of initial size 32768

i doubt it matters but try running the DCS.exe in the BIN folder instead of BIN-MT. 

2025-06-29 20:54:57.485 INFO    EDCORE (Main): C:\Program Files\DCS World\bin-mt\DCS.exe

also remove any mods. i didn't see any. then run a repair.

  • Like 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.

Posted

Thanks, I had previously tried using the BIN version instead of BIN-MT which didn't help. Setting the fixed pagefile seems to have resolved this.

  • Solution
Posted (edited)

Does this work fine in other missions, multiplayer, etc. it's just this one mission?

If you haven't already then I'd also try the standard steps:

  • running a slow repair of the game and delete your Saved Games\DCS\fxo and metashaders2 folders.
  • Next, delete %LOCALAPPDATA%\TEMP\DCS and try again.,
  • Next try renaming Saved Games\DCS to DCS.old and try again. Rename so you can copy your bindings back from the Config\Input folder.

The DxDiag report indicates a number of failures that appear to be GPU related (see below). Could be corrupt drivers (try DDU'ing the existing drivers and then reinstall, you could also try version 566.36), hardware, or power issue.

Windows Error Reporting (WER)

Kernel Events

The following kernel-events have been detected:

  • VIDEO_ENGINE_TIMEOUT_DETECTED,FAULTY_HARDWARE_CORRUPTED_PAGE
  • 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 open a command prompt as administrator, run the below two commands separately and restart your PC.

dism /online /cleanup-image /restorehealth

sfc /scannow

 

Of interest as well in this stack trace is something I've seen in a few other crash reports now. I'll see if I can locate the others as may need investigation by ED if this is becoming a common theme.

2025-06-30 04:54:49.270 INFO    EDCORE (Main): # -------------- 20250630-045449 --------------
2025-06-30 04:54:49.271 INFO    EDCORE (Main): DCS/2.9.17.11733 (x86_64; MT; Windows NT 10.0.26100)
2025-06-30 04:54:49.272 INFO    EDCORE (Main): C:\Program Files\DCS World\bin-mt\DCS.exe
2025-06-30 04:54:49.273 INFO    EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff6ad40f554 00:00000000
2025-06-30 04:54:49.274 INFO    EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Program Files\DCS World\bin-mt;', symOptions: 532, UserName: 'Nick'
2025-06-30 04:54:49.275 INFO    EDCORE (Main): OS-Version: 10.0.26100 () 0x300-0x1
2025-06-30 04:54:49.276 INFO    EDCORE (Main): 0x000000000073f554 (DCS): SW + 0x127434
2025-06-30 04:54:49.277 INFO    EDCORE (Main): 0x0000000000797197 (DCS): SW + 0x17F077
2025-06-30 04:54:49.278 INFO    EDCORE (Main): 0x000000000071778f (DCS): SW + 0xFF66F
2025-06-30 04:54:49.279 INFO    EDCORE (Main): 0x000000000000461b (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x3EB
2025-06-30 04:54:49.279 INFO    EDCORE (Main): 0x0000000000004c42 (World): wSimCalendar::DoActionsUntil + 0x262

Some errors in the DCS log with audio devices failing to load as well.

Some additional tuning tips from the DCS log analyzer:

  • Set Preload Radius to max. 60000. (yours is currently set to 100000 so will be loading potentially redundant data, and you only have 8Gb VRAM and 32Gb RAM).
  • Decrease Terrain Textures.
  • Set Clouds to High.
  • Enable Full Screen mode.
  • Set Water to Low.

Latest log shows you're still running DCS from bin-mt vs. bin.

Edited by sleighzy

AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2

Posted

I followed all of Sleighzy's advice except that I didn't mess with my graphics driver or rename my Saved Games/DCS folder. There was also a minor update available which I installed. I'm not sure exactly what fixed it but I can confirm that the crash is no longer occurring. Thanks for the help!

  • Like 1
  • Thanks 1
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...