Jump to content

Recommended Posts

Posted (edited)

Hi

Getting daily crashed doing missions in DCS, works well for mostly around 30-45 mins usually before the game freezes and crashes. 
Most often the crashed happens at the Caucasus missions for some reason in VR. 
This crash happed during attempts to learn how to bomb in the F-14B on the Persian Gulf map. 

I have removed all mods, undervolted CPU and GPU to see if they were a issue (they were not, low temperatures at crashes), updated every possible driver there is, repaired the game, checked the files.
Done stresstests on the GPU, RAM and CPU and gotten no errors at all there. 

DCS is the ONLY game i get crashes in, neither BMS, MSFS, Asetto Corsa Competzione, BG3, ETS2 or iRacing have crashed the last weeks while DCS does it a few times a day. 
 

dcs.log-20241112-225543.zip dcs.20241112-225543.crash dxdiag.txt dcs.20241112-225543.log

Edited by CannonFodder84
Posted

I've dropped your DCS zip file in the DCS log analyser which had the following to say:

Errors

Memory Timing Issues

Remove any overclocking (XMP) from your RAM.

The Integrity Check failed

Delete all unofficial mods and do a full slow repair of DCS, and choosing the option to remove files.

Error

Error:
attempt to call method 'getCoalition' (a nil value)

Line
2846

Script
l10n/DEFAULT/Ground Missions.lua

Error:
attempt to concatenate global 'iniUnitTypeName' (a nil value)

Line
1089

Script
l10n/DEFAULT/RAT.lua

There is a GPU-related error

Remove any overclocking from your GPU.

Uninstall your GPU driver with DDU and install a clean one.

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

Posted

Your DxDiag file contains the last 10 system/process crashes:

  • DCS (3 times) - you're aware of this one
  • The Oculus Tray Tool (4 times)
  • 3D Mark Speed Way
  • Live Kernel Event (2 times) - these ones have an error code of 141 which can indicate a hardware issue (particularly GPU overclocks in some cases). Even if you're not applying an overclock the manufacturer of your card may have. I believe MSI Afterburner may be able to identify that and remove.

 

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

  • 2 weeks later...
Posted

After a few busy days i decided to try again. 
Undervolted the GPU, made sure to select the undervolted profile again, updated EVERY possible hardware driver, didnt launch Oculus tray tool, ran a 3Dmark stresstest (got 1 incomplete, adjusted the GPU settings, passed the test), ran a RAM diagnosis with no error in windows. 
Yet i have crashed 3 times..
Tried two different maps, game starts, i take off and it freezes and crashes after a couple of minutes.. WTF
The log analyzer aint helpful today and gives me "interaction failed" message

Can anyone with skills in this sorta thing have a look and see any issues?

 

dcs.log-20241121-193340.zip

Posted
8 hours ago, CannonFodder84 said:

After a few busy days i decided to try again. 
Undervolted the GPU, made sure to select the undervolted profile again, updated EVERY possible hardware driver, didnt launch Oculus tray tool, ran a 3Dmark stresstest (got 1 incomplete, adjusted the GPU settings, passed the test), ran a RAM diagnosis with no error in windows. 
Yet i have crashed 3 times..
Tried two different maps, game starts, i take off and it freezes and crashes after a couple of minutes.. WTF
The log analyzer aint helpful today and gives me "interaction failed" message

Can anyone with skills in this sorta thing have a look and see any issues?

 

dcs.log-20241121-193340.zip 2.47 MB · 2 downloads

The crash in this log is different from the original crash in this post, unknown as to whether or not they are unrelated. In the case of this one have you tried disabling ReShade and running DCS for awhile to see if it crashes? Do you recall what ReShade version you're running? You can use the https://github.com/fredemmott/OpenXR-API-Layers-GUI tool to uncheck the ReShade box to disable that OpenXR API layer for testing purposes.

What version of Virtual Desktop are you on, and what other games do you use it for? You could always uninstall and reinstall the VD Windows streamer app in case there's any problem there.

Essentially, if you're using VD then you want to use the VDXR runtime vs. SteamVR. It's more performant as you're not loading all the SteamVR overhead.

I also noticed in your log you have the gunner_export hook from the OH-6 mod. This has documented performance issue than can cause stutters. There's a new release of this mod that apparently has a more performant hook, I don't know which version you're on, but otherwise it recommends to remove that hook. The mod itself is fine. Just something to look out for if you do notice stutters in the game.

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

Posted

I have deleted the reshade using the installer and deleted the files i found a couple of weeks ago. 
Using VD version 1.33.2 which is the newest one, might try a re-innstall. 
 

Gonna try using VDXR again soon, worked well in MSFS2024 both yesterday and today. 
But crashed 3 times in a very short time yesterday. 

I have also deleted every single mod exept taxview the last time i had crashes. 

Posted

Had similar problems i tried everything -  more RAM, larger pagefile, a new SSD, reinstalled win10, deactivated XMS profile, but nothing helped. With all other games and in 3Dmark, i didn´t had any problems, only with DCS.

The only solution for me, which solved the problem, was to enable the debug mode in NVidia driver. After that, everything worked well.

  • Recently Browsing   0 members

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