Jump to content

Recommended Posts

Hello everyone,

a friend of mine bought the F14 a few days ago. 
Now DCS crashes as soon as he tries to connect to an MP server. SP works fine for him. The problem only occurs in the F14. 
The F18, for example, works great here. He starts DCS with steam from an HDD. As I said, no problem in the F18 (130FPS +). 
Do you have a simple solution here? I'll ask him about log files. That might make it easier. 
Oh, maybe I should say that files on Steam have already been repaired, DCS reinstalled, F14 reinstalled and the Persian Gulf map too.

 

Edited by Hahnperator
Link to post
Share on other sites

Please make sure he is on the latest open beta. 

 

Run a full cleanup and repair or verify if steam version. 

 

if you still see the crash please attach your dcs.log from your saved games dcs log folder.

 

thank you

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 10 Pro x64, NVIDIA MSI RTX 2080Ti VENTUS GP, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 32GB DDR @3000, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to post
Share on other sites

Hi BIGNEWY,

 

I have to correct the description of Hahnperator a bit. The crash does not occur when connecting to the server, but when I am on the server, select my plane role and click "fly".
The cockpit appears in the approach and then the crash comes to the desktop. Sometimes it starts to load all textures and objects on the map and then crashes after a short time (ca.- 2 min.).
Mainly this crash seems to occur now with the map "Persian Gulf".


I do not have such problems with the F-18. Also with planes from the "Flaming Cliff" DLC I could already fly on the map.

 

Previous correction / error prevention attempts

- Reinstallation of the "open beta - public beta versions"
- Deleting the "fxo" and "metashader2" folders (after info in a forum post)
- Reinstallation of the "Persian Gulf" DLC

- In addition, I also used the repair function on steam, but there were no missing files or errors found.

 

Attached you can find the crash log from today. (tryed to to jump into the F-14 on Persian Gulf)

I hope it is the right log file.

 

My basic system information:

I7 - 8700K

16 GB DDR4 RAM

GeForce 1080TI

HDD (on which DCS is installed)

Win10 64bit

dcs.20210218-200736.crash

dcs.log


Edited by SchwalbeAUF6
Link to post
Share on other sites

Hi @SchwalbeAUF6, you're having E_OUTOFMEMORY crashes:

 

2021-02-18 20:07:35.935 INFO    EDCORE: # -------------- 20210218-200736 --------------
2021-02-18 20:07:35.935 INFO    EDCORE: DCS/2.5.6.61527 (x86_64; Windows NT 10.0.19041)
2021-02-18 20:07:35.935 INFO    EDCORE: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
2021-02-18 20:07:35.935 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at E38D16E9 00:00000000
2021-02-18 20:07:35.935 INFO    EDCORE: SymInit: Symbol-SearchPath: '.;D:\Steam\steamapps\common\DCSWorld;D:\Steam\steamapps\common\DCSWorld\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Flo'
2021-02-18 20:07:35.935 INFO    EDCORE: OS-Version: 10.0.19041 () 0x100-0x1
2021-02-18 20:07:35.936 INFO    EDCORE: SymInit: Symbol-SearchPath: '.;D:\Steam\steamapps\common\DCSWorld;D:\Steam\steamapps\common\DCSWorld\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Flo'
2021-02-18 20:07:35.936 INFO    EDCORE: OS-Version: 10.0.19041 () 0x100-0x1
2021-02-18 20:07:35.961 ERROR   DX11BACKEND: failed to create index buffer. Reason: E_OUTOFMEMORY
2021-02-18 20:07:35.961 INFO    EDCORE: try to write dump information
2021-02-18 20:07:35.961 INFO    EDCORE: # -------------- 20210218-200736 --------------

 

Manually set your pagefile like this:

 

Initial size: 16384 (MB)

Max size: 32768 (MB)

 

But first, you must ensure there's sufficient room in the drive your pagefile is stored in. You can identifiy this drive by running this "cmd" command:

wmic pagefile list /format:list

Edited by Flappie
Link to post
Share on other sites

Hi @Flappie,

 

Thanks for your help.

I have tested this solution and so far it works. 
Now only strong lags in connection with frame drops remain (sometimes 2-3 sec.). It seems like loading sequences that occur sporadically. 

Do you see a possibility how I can possibly eliminate this?

 

 

Link to post
Share on other sites

Hi @SchwalbeAUF6. Occasional lag is often a consequence of slow file accesses. Let's try this:

  1. Start DCS, Alt+Tab back to Windows, start the Windows Resource monitor (resmon), maximize its window, display the Disk tab, tick "dcs.exe", then sort by response time (higher on top). There, you will see all files being accessed by the game as it starts (game files, temp files, shaders, system pagefile...) and the response time for each file being accessed. When DCS is installed on an SSD, one is supposed to see very short response times (comprised between 0 and ~50 ms for the most part).
  2. Now, go back to DCS and enjoy your flight. As soon as you encounter lag, immediately Alt+Tab back to resmon and hit PrintScreen (you can also save data in resmon but I haven't tested this yet). What we're looking for is unusually long response times.

Here's a beautiful example of a faulty SATA cable messing with an SSD response times (second picture: 571 ms, 609 ms, 646 ms...).

 

Lag can also be caused by a bad WiFi connection when in an MP session (been there, saw that), paranoid antivirus software, gaming software such as MSI Dragon Center, bloatware... but first, let's concentrate on you file access times.


Edited by Flappie
Link to post
Share on other sites

I have another crash with F-14 module. The last 2 months, all of my crashes happens with this module. I think its not related with pagefile or mem, or system overclocking, maybe it could be a issue with that module?. It happened exactly when opening wheel comms with F-14, just after taking off from carrier. Attached logs

dcs.log-20210221-184053.zip

Link to post
Share on other sites
30 minutes ago, Flappie said:

I don' think this crash is caused by the Tomcat module. I've seen a number of crashes like yours, lately ("SoftMaxShader"), and one of them happened to a Hornet pilot.

Thanks for your quick answer. My system is perfectly stable with other modules, other games, other benches (OCCT or prime95 many hours....), fumark... etc and I can have any crashes. Maybe it could be a bug from DCS software itself?

 

It surprise to me that my crash file it´s exactly the same as crash#2. Even the same codes! so it seems to me a software bug, due code similarities

 

0x0000000000439F70 (nvwgf2umx): NVDEV_Thunk + 0xBC8B0
0x00000000010B5D4F (nvwgf2umx): cask::ShaderList<cask::SoftmaxShader,cask::SoftmaxOperation>::availableShaders + 0x7916F
0x00000000010B5CCA (nvwgf2umx): cask::ShaderList<cask::SoftmaxShader,cask::SoftmaxOperation>::availableShaders + 0x790EA
0x00000000010AAEED (nvwgf2umx): cask::ShaderList<cask::SoftmaxShader,cask::SoftmaxOperation>::availableShaders + 0x6E30D
0x0000000000681B4A (nvwgf2umx): cask::SafeEnum<cask::GemmChip_ENUMCLASS_SCOPEWRAPPER>::SafeEnum<cask::GemmChip_ENUMCLASS_SCOPEWRAPPER> + 0x165CA
0x000000000163776C (nvwgf2umx): OpenAdapter12 + 0x3A88FC
0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14
0x000000000004D241 (ntdll): RtlUserThreadStart + 0x21

 

In addition, searching on DCS forums, results with "SoftMaxShader" issue  are only showed since 27th january. No more results before that date, in other years, so I suspect it is a software bug (or maybe a wrong Nvidia driver / W10 update).


Edited by Gryzor
Link to post
Share on other sites

Definitely agree it is some kind of new issue that hasn't been there in the previous open beta version. I've suffered similar crashes today, as well as a few in the past days. I got right here since today's was triggered by spawning in a Tomcat twice in a row (until I called it quits with DCS for the evening). The other day it happened on a flight in a Hornet upon being hit by something. So there definitely is a correlation with some events withinin DCS. Sadly no proper log has been produced for my incidents today. DCS just plain ceased to be.


Edited by Kang
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...