Crash sometimes due to perf monitoring and diagnostic software

[Worrazen]

Looks like in some cases, doing something, or just nothing in particular with MSIAfterburner, RTSS, OBS, ProcessHacker can cause a crash with DCS.

 

One time MSIAfterburner it self crashed due to an invalid value I entered into it's PerfCounter item (out of bounds, invalid type), it crashing in a bad way also caused DCS to crash with a similar error message as show below, that occasion was in mid-gameplay on a longer session.

 

In this example, for which I provide the crash log and error image, I started DCS on the login screen, idling and doing something else in Firefox, I did not start any other game except ProcessHacker, OBS and MSI Afterburner with RTSS.

 

DCS was detected by RTSS but I wasn't actively doing anything with it because on the login screen, 3D wasn't loaded yet so there's no overlays or anything, and OBS was also started default to capture game from DCS but there was nothing shown nor did I actually need it to do anything, I was using those programs for an unrelated thing in this case, while DCS just happened to be idling on the login screen for no reason.

 

I exited all of those programs later, and then I logged in and DCS began launching, but it crashed right away with this:

 

Crash_SuspectDiagUtility_dcs.log-20210123-172743.zip

 

 

I was not able to repeat this in 5 attempts I tried, usually I have had no problems with these softwares with DCS, but I'm sure it's one of them, it happens to be rare thankfully.

 

EDIT: I was writing this in a hurry, I'm not sure what caused it, it happened twice on different circumstances, one of them very suspiciously timed with a problem in MSI Afterburner, but no real idea if these two are related. This report only includes the second case, when this error happened by it self without anything else going wrong.

Edited January 27, 2021 by Worrazen
No, im not sure about what's the cause, corrected wording