BSOD's playing Squad, Wargame:RD - Always System_Service_Exception

Latest dump indicates a problem with aswMonFlt.sys.

Code:

BugCheck 3B, {c0000005, fffff8034c0ada32, ffffd0002a9810c0, 0}

*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
Probably caused by : aswMonFlt.sys ( aswMonFlt+6747 )

aswMonFlt.sys belongs to Avast anti-virus. Try uninstalling it then make sure Windows Defender and Windows Firewall are enabled and run with them for awhile, see if that resolves the problem.

The older dumps are inconclusive, many are Bugcheck 3B pointing at different kernel modules. Something else is causing the problem.

If removing Avast does not fix the problem, then enable Driver Verifier and see what that shows us:

===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to
PART TWO
and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.

Two new dumps in that zip. The first one 7/27 1:57PM does not have Verifier enabled. It does indicate a problem with dxggms.sys which is a Windows module and not the cause. I see quite a few references to atikmdag in the thread trace. This belongs to your AMD Radeon R9 200 Series video card driver.

Looks like you have the latest available:

Code:

Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Fri Jul 08 15:11:29 2016 (577FFAE1)

The newest dump is 7/27 7:02PM and Driver Verifier is enabled and setup correctly.

Code:

BugCheck 3B, {c0000005, fffff803df67d924, ffffd0005dbf56b0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+14 )

ntkrnlmp.exe is par tof the OS and not the cause of this failure either.

Looking at the thread trace, it indicates a problem with EasyAntiCheat.sys

Code:

ffffd000`5dbf6498  fffff801`3e19bdcdUnable to load image \??\C:\Windows\system32\drivers\EasyAntiCheat.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for EasyAntiCheat.sys
*** ERROR: Module load completed but symbols could not be loaded for EasyAntiCheat.sys
 EasyAntiCheat+0xbdcd

This is probably the real cause of your problems. Can you run your games without it?

I guess the EAC instability is due to the game being in Alpha.

That could very well be. Hopefully they will release an updated version soon that you can try.