Jump to content

DCS Random Crashes -


PaulG

Recommended Posts

I'm getting frequent and random crashes.

 

The goes blank, and a loud sound plays from the speaker. The only way to get out of this is to hold the power button down for several seconds to turn the PC off.

 

So here is what I know and have done...

it only happens in DCS, no other flight sim (MSFS, Elite Dangerous) and no other games

I'm running the latest version download yesterday

It's not the load on the GPU or CPU. I can stress test both for a significant amount of time.

All updates to Windows and graphics drivers have been done

I have reinstalled completely DCS (not in the default directory as I do not have enough space on the C:\ drive)

 

My specs are...

i7-6700k

Gigabyte Z170

Radeon Vega 64

32gb ram

Gigabyte 1tb SSD (I have tried other discs as well)

CH Pro throttle, fighter stick, Thrustmaster pedals and  T16000M stick

Home made "TrackIR" clip and a PS3 Eye camera

VoiceAttack

 

Actually I have put the fighter stick grip on the T16000M base, as the fighter stick gimbals horrendous around centre, and the base of the T16000M has lots of buttons.

 

When I look at the logs, there is no consistency in the last few lines in the log file

 

Any ideas? Anyone else having issues like this?

 

It's really stopping me getting into the game as it can happen are 5mins, 1 hour or more. Just random

 

Thanks

 

Paul

 

dcs.log

Link to comment
Share on other sites

Maybe a question of time playing

When increasing swap, the limit is far away than before ( if this is a limit problem...)

 

 

You should check memory usage when playing, if it is increasing continously or not...

 

And what about free memory available while playing...

 

I am interested about a link of 'hot swap connect' you mentionned

Link to comment
Share on other sites

39 minutes ago, PaulG said:

regarding logs I don’t get any detailed ones with time stamps

how do I enable this?

Look into "C:\Users\username\Saved Games\DCS...\Logs\": attach the most recent zip file you can find in there.

 

27 minutes ago, fab.13 said:

Flappie phone number should be  911 😉

So sweet. 😇

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

Just to describe the problem again.

 

When I get these crashes (only in DCS) the screen goes blank, and to only way to recover is to hold the power button for several seconds to force the PC to turn off

 

I have never see the crash dialog in DCS

 

I've reinstalled on my main C drive, and on my big SSD where I hold my steam games.

 

Updated the graphic driver and windows.

 

i7-6700k

Z170 chipset

32 GB ram

Radoen Vega 64

 

Can anyone this of anything else

 

Thanks

 

 

Link to comment
Share on other sites

Thank you for all this. I see you have a lot of free space in all your drives, that your game is installed on an NVMe drive, and that your system is installed on an SSD.

 

In your dxdiag log, I see a lot of opentrack.exe crashes. Can you try launching the game without launching the OpenTrack software? Does DCS still crash or not?

 

Windows Error Reporting:
+++ WER0 +++:
Fault bucket 2292295323547509199, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: opentrack.exe
P2: 0.0.0.0
P3: 5f3e37fd
P4: opentrack-tracker-wii.dll
P5: 0.0.0.0
P6: 5f3e3852
P7: c0000005
P8: 00001025
P9: 
P10: 


+++ WER1 +++:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: opentrack.exe
P2: 0.0.0.0
P3: 5f3e37fd
P4: opentrack-tracker-wii.dll
P5: 0.0.0.0
P6: 5f3e3852
P7: c0000005
P8: 00001025
P9: 
P10: 


+++ WER2 +++:
Fault bucket 2292295323547509199, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: opentrack.exe
P2: 0.0.0.0
P3: 5f3e37fd
P4: opentrack-tracker-wii.dll
P5: 0.0.0.0
P6: 5f3e3852
P7: c0000005
P8: 00001025
P9: 
P10: 


+++ WER3 +++:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: opentrack.exe
P2: 0.0.0.0
P3: 5f3e37fd
P4: opentrack-tracker-wii.dll
P5: 0.0.0.0
P6: 5f3e3852
P7: c0000005
P8: 00001025
P9: 
P10: 


+++ WER4 +++:
Fault bucket 2292295323547509199, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: opentrack.exe
P2: 0.0.0.0
P3: 5f3e37fd
P4: opentrack-tracker-wii.dll
P5: 0.0.0.0
P6: 5f3e3852
P7: c0000005
P8: 00001025
P9: 
P10: 


+++ WER5 +++:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: opentrack.exe
P2: 0.0.0.0
P3: 5f3e37fd
P4: opentrack-tracker-wii.dll
P5: 0.0.0.0
P6: 5f3e3852
P7: c0000005
P8: 00001025
P9: 
P10: 


+++ WER6 +++:
Fault bucket 2292295323547509199, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: opentrack.exe
P2: 0.0.0.0
P3: 5f3e37fd
P4: opentrack-tracker-wii.dll
P5: 0.0.0.0
P6: 5f3e3852
P7: c0000005
P8: 00001025
P9: 
P10: 


+++ WER7 +++:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: opentrack.exe
P2: 0.0.0.0
P3: 5f3e37fd
P4: opentrack-tracker-wii.dll
P5: 0.0.0.0
P6: 5f3e3852
P7: c0000005
P8: 00001025
P9: 
P10: 

 


Edited by Flappie

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

Ok I’ll try without opentrack again. I’m sure I did before. 

any ideas about the opentrack crashes?


I’ll also try without any joysticks plugged in, and not voiceattack either

Not playable like this but might narrow the problem down

 

ran a memtest86 overnight. All passed. 
 

Thanks

 

 

 

Link to comment
Share on other sites

The problem with this dxdiag log history of crashes is that it has no dates. But it's OK, I had a doubt about opentrack, but you've just lifted the doubt. The truth is elsewhere.

 

I don't understand why DCS detects a small 4GB pagefile, when you seem to have forced it to a minimum of 16GB, as seen in our post above.

 

2021-02-17 17:40:39.937 INFO    DCS: CPU cores: 4, threads: 8, System RAM: 32686 MB, Pagefile: 4864 MB

 

However, I don't see the usual "E_OUTOFMEMORY" error message...

 

I'm thinking the freezes could come from your antivirus blocking some files. Please add the following folders as exceptions in your antivirus:

  • G:\DCS World\
  • C:\Users\username\Saved Games\DCS\

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

thanks for all the help here. Really appreciate it.

 

Since I have loads of space on my drives and set a 32gb page file.

Which drive should I use? the windows C drive or my game drive G

min 32768 max 32786?

 

I don't have any anti-virus other than the standard windows 10 protection.

It's my gaming PC so not critical. 

 

I'm also going to test the vram. i doubt there is a probelm here as I also have MSFS 2020 which maxes out the vram.

 

 

Link to comment
Share on other sites

It doesn't matter if the pagefile and the game are stored in separate drives. The pagefile should be stored on a fast drive with sufficient free space. If both your C:\ and G:\ drives are fast, you can try to move it from one drive to another to see if it's any better.

 

Initial 32768 / max 32768 is good, yes (as far as I know, DCS doesn't need more than a 32GB pagefile so far).


Edited by Flappie

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

Thanks. I see your crashlog are still silent. It means it's a freeze from DCS point of view, not a "proper" crash.

 

Here are a few solutions that worked for some users having infinite freezes just like you:

 

  • Uninstall Razer Synapse 3 (it was messing with an SSD for an unknown reason).
  • Empty "C:\Users\username\AppData\Local\Temp\DCS" or "DCS.openbeta" folder.
  • Rename Saved Games\DCS folder to get a new one.
  • Try running DCS with all unneeded drives unplugged, and especially HDDs.

 

It would be interesting to see what Windows Resource Monitor (resmon) has to say about this. I don't know if you're already in the process of reinstalling, but here's what I need you to do to make sure this isn't an issue with file access timings:

  1. Open the Resource monitor (resmon).
  2. Select the Disk tab.
  3. Maximize the window and sort the bottom table on the Response time column (highest on the top).
  4. Run DCS, launch an instant action mission, enable autopilot mode, and Alt+Tab to get back to resmon.
  5. Select "DCS.exe" in the top list.
  6. Make several screenshots of resmon and attach them here.

 

Here's an example:

 

image.png

 


Edited by Flappie

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

Perfect.

 

We're looking for long response times, which can cause freezes. Considering you have very fast drives, their response times should stick under ~50ms. That's what I get with an old SSD drive (860 EVO 1TB). Yet, we can see some DCS file accesses had long response times: 338ms, 127ms and 101ms (third screenshot). It doesn't look catastrophic, but I think it's not a good sign either. And I take it you haven't seen what resmon shows when DCS is about to freeze.

 

I don't know much about NVMe drives, but I know they share the PCIe bus with graphics cards. Maybe there's a conflict somewhere? A BIOS setting maybe?

You should start by running a speed test on your G:\ drive. Is it anywhere close to the official specs?

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

  • Recently Browsing   0 members

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