Game crash in 2.7

[ConkersBFD]

Hello,

 

I sometimes get random crashes where DCS stops responding but doesn't CTD. I can still hear RWR and engine sounds but the image freezes and task manager shows "no response" from DCS so I have to force quit.
I cannot find out what's causing it.

DCS Openbeta
Win10
i5 6600k

rtx3070

32g ram

Log file from latest crash

dcs.log

Edited July 6, 2021 by ConkersBFD

[Flappie]

Hello. It seems a device is reponsible for this. There are the last lines of your log:

 

2021-07-06 16:13:02.335 DEBUG   LuaGUI: ---side---	1	1
2021-07-06 16:13:02.336 DEBUG   LuaGUI: ---side---	1	0
2021-07-06 16:13:03.567 DEBUG   LuaGUI: ---onShowPool()----
2021-07-06 16:14:58.209 INFO    DCS: Device plugged: \\?\SWD#DAFUPnPProvider#uuid:11490c80-0022-1000-ab77-0c89108ae7d6#{2a323d9d-edf1-430b-ab95-5860894493d4}
2021-07-06 16:15:38.317 INFO    DCS: Device plugged: \\?\SWD#DAFUPnPProvider#uuid:11490c80-0022-1000-ab77-0c89108ae7d6#{ac4630a5-0b64-46e5-981b-12535fc1f5de}

 

I assume "SWD\DAFUPnPProvider\uuid:..." points to a storage device. Is your DCS stored on a removable drive?

Please attach your dxdiag log (how to get one).

 

Please attach this file as well: "C:\Windows\INF_setupapi.dev.log". It should help identifying the device.

Edited July 6, 2021 by Flappie

[ConkersBFD]

1 hour ago, Flappie said:

Hello. It seems a device is reponsible for this. There are the last lines of your log:

 

2021-07-06 16:13:02.335 DEBUG   LuaGUI: ---side---	1	1
2021-07-06 16:13:02.336 DEBUG   LuaGUI: ---side---	1	0
2021-07-06 16:13:03.567 DEBUG   LuaGUI: ---onShowPool()----
2021-07-06 16:14:58.209 INFO    DCS: Device plugged: \\?\SWD#DAFUPnPProvider#uuid:11490c80-0022-1000-ab77-0c89108ae7d6#{2a323d9d-edf1-430b-ab95-5860894493d4}
2021-07-06 16:15:38.317 INFO    DCS: Device plugged: \\?\SWD#DAFUPnPProvider#uuid:11490c80-0022-1000-ab77-0c89108ae7d6#{ac4630a5-0b64-46e5-981b-12535fc1f5de}

 

I assume "SWD\DAFUPnPProvider\uuid:..." points to a storage device. Is your DCS stored on a removable drive?

Please attach your dxdiag log (how to get one).

 

Please attach this file as well: "C:\Windows\INF_setupapi.dev.log". It should help identifying the device.

 

Thanks for your fast answer 
DCS is installed on a NVME SSD drive (separate from windows installation)

 

Here are the DxDiag and setupapi files

DxDiag.txt setupapi.dev.log

[Flappie]

I couldn't retrieve the two GUIDs seen in your crash log.

However, when I google the first figures of the uuid:

uuid:11490c80-0022-1000-ab77-0c89108ae7d6

...all I can find are Samsung equipments.

 

And I see your DCS is installed on a Samsung SSD, not an NVMe drive. So maybe your Samsung SSD gets disconnected/reconected for an unkown reason.

Now, I see in your dxdiag log that your Razer Synapse 3 is having crashes... which rang a bell:

 

 

Please uninstall Razer Synapse 3 and see if you keep having these crashes. If you can't live without Synapse 3, simply disable it before starting DCS.

Please let us know if this solves your crash problem.

[ConkersBFD]

My DCS is installed on a Samsung SSD 970 EVO Plus, which is a NVMe M.2. I'll try what you suggested with Synapse. I'm also using Razer Cortex to free a little bit of CPU and RAM usage, I'll try and disable it as well if that doesn't work.

Many thanks, I'll keep you posted !

[Flappie]

My bad: I didn't know Samsung was selling SSD and NVMe drives under the same name (I have a 970 EVO SSD).

You're welcome.

[ConkersBFD]

No joy  I just had a crash on Marianna in MP again. Same symptoms (no CTD, DCS freezes).

I redid a DxDiag (in case it's useful, I'm not sure) and the log file.

I noticed the same lines as before:
2021-07-06 21:58:15.150 INFO    DCS: Device plugged: \\?\SWD#DAFUPnPProvider#uuid:11490c80-0022-1000-ab77-0c89108ae7d6#{2a323d9d-edf1-430b-ab95-5860894493d4}

But this time a new challenger appeared:

2021-07-06 21:58:16.825 INFO    DCS: Device plugged: \\?\SWD#DAFUPnPProvider#uuid:0f7f4900-0004-1000-b1b5-0c89108ae7d6#{fdec7c7a-f51d-4f93-98de-31d05a3f059f}

 

DxDiag2.txt dcs.log

Edited July 6, 2021 by ConkersBFD

[Flappie]

It seems the new uuid also points to a Samsung device.

 

Please disable DCS hotplug devices management and see if crashes keep coming:

 

You should also take a look at your Event viewer ("Observateur d'évènements" in French). Open the "Journaux Windows" section, and look into "Applcation" and "Système". You may find some event related to a Samsung device (most probably your NVMe) at the time of your last crash.

 

[Flappie]

By the way, have you installed 970 EVO drivers? If so, try reinstalling them. See this thread (BSOD caused by 970 EVO broken drivers):

 

 

[ConkersBFD]

Ok ! 

I reinstalled the Samsung Nvme driver (mine was already up to date) 

I also disabled Razer Cortex last night and didn't have any issues. I didn't play for very long though so not 100% sure it's the culprit. 

 

I'll try the rest of your suggestions and if everything runs smoothly I'll do some tests to pinpoint if Razer Cortex can be a culprit. 

Razer Synapse already being a problem I wouldn't be surprised.

Edited July 7, 2021 by ConkersBFD

[ConkersBFD]

I've been playing a few longer sessions and everything is working perfectly now, thanks @Flappie ! 
 

[Flappie]

Great news! Thanks for your feedback.