BSOD 0x00000139 Crash

you were running ArmA2OA.exe

the directx detected a stack over run and shut down the system
here is the error code:
ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

I would scan for malware using malwarebytes, do a virus scan, scan your OS files for corruption: run cmd.exe as an admin then
sfc.exe /scannow
and confirm all corrupted files are fixed, if they are not fixed then run
dism.exe /online /cleanup-image /restorehealth


I would also update the game or make sure you don't have a hacked version.

in terms of drivers:
\SystemRoot\System32\drivers\amdide64.sys Wed Jul 08 07:18:07 2009
this is a pretty old SATA driver, you might look for a update.
\SystemRoot\System32\drivers\AtiPcie.sys Mon Aug 24 01:25:26 2009
another pretty old driver.
your network driver is very old, bugs in it can cause some issues with some online games:
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
\SystemRoot\system32\DRIVERS\Rt64win7.sys Thu Jun 09 23:33:15 2011
update here: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

some versions of the razer drivers tend to corrupt memory, I don't know if they ever fixed the problem but you should look for a updated drivers. C:\WINDOWS\system32\drivers\rzpmgrk.sys Thu Apr 17 12:36:12 2014

looks like you have logmein drivers (Hamdrv.sys) running, make sure you want this and it is not remote software hacking your machine. (could not see a file datestamp or checksum)




C:\Program Files (x86)\Common Files\BattlEye\BEDaisy.sys Wed Feb 18 06:22:31 2015
(very new anti cheat driver)

I added info on drivers to update.
a 3rd party app making incorrect programming calls could cause the problem, you should look for an update or google the error and the app name.
the debugger code was STACK_COOKIE_CHECK_FAILURE

This is just a guess but you have a usb audio device
C-Media Audio USB Driver
\SystemRoot\system32\drivers\CM10664.sys Thu Jan 16 19:44:46 2014

this driver might have a conflict with the high definition audio support in your graphics card or on your motherboard. If you don't get sound to your monitor speakers from your graphics card video cables, you might want to go to windows control panel device manager and disable. off the GPU high definition audio support. I don't see a driver for your motherboard sound so I assume it is already disabled.
------
\SystemRoot\system32\drivers\gfibto.sys Thu Sep 01 18:31:28 2011
not sure what this is, but it is old. listed as Possibly a VIPRE Antivirus driver
http://www.vipreantivirus.com/free-antivirus-trial/
you should remove it if you don't need it.

-------------
the system bugchecked because of a stack overflow in the graphics subsystem. This could be just a app that is making bad calls or attempting to break into the system. It could also be a BIOS problem or a GPU problem doing a direct memory access transfer to the video card.

You might also consider going into BIOS and resetting it to defaults, This should force the BIOS to rebuild the database of hardware settings that it passes to windows. I mention this because of the call to DMA buffer.



KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000002, Stack cookie instrumentation code detected a stack-based
buffer overrun.
Arg2: ffffd0015dd05810, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd0015dd05768, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved


PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

DEFAULT_BUCKET_ID: STACK_COOKIE_CHECK_FAILURE


here is the call stack:
4: kd> kc
Call Site
nt!KeBugCheckEx
nt!KiBugCheckDispatch
nt!KiFastFailDispatch
nt!KiRaiseSecurityCheckFailure
dxgmms1!_report_gsfailure
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer
dxgmms1!VidMmReferenceDmaBuffer
dxgkrnl!DXGCONTEXT::Render
dxgkrnl!DxgkRender
nt!KiSystemServiceCopyEnd
0x0
---------------
machine info:
BIOS Version 080015
BIOS Release Date 03/26/2010
Manufacturer ECS
Product Name A885GM-A2
Version 1.0

Manufacturer ECS
Product A885GM-A2
Version 1.0
Processor ID a00f1000fffb8b17
Processor Version AMD Phenom(tm) II X6 1100T Processor
Processor Voltage 8fh - 1.5V
External Clock 200MHz
Max Speed 3700MHz
Current Speed 3300MHz

Looks like there is a BIOS update for this machine but I don't know if it would help.
http://www.ecs.com.tw/ECSWebSite/Product/Product_Detail.aspx?DetailID=1120&CategoryID=1&MenuID=19&LanID=0

this is listed as a amd sata controller driver. it is pretty old, can you update it?
\SystemRoot\System32\drivers\amdide64.sys Wed Jul 08 07:18:07 2009
--------------

the first bugcheck was a stack overflow doing a direct memory access to
the second was bugcheck because some data was not in memory when the driver tried to read it and the driver had its interrupt priority too high so that the windows memory manager could not service the request. I would think it is a driver bug.

At this point I would: run cmd.exe as an admin, then run
verifier.exe /standard
then change the memory dump type to full or kernel so the debugging info is not removed from the memory dump. then reboot and run until you get another bugcheck with debug info.

when done run
verifier.exe /reset
this will clear the debugging flags and your system will run at full speed again.

it looks like a motherboard driver for a SATA controller as far as I can tell.

TiWorker.exe was running, I would think that the system was trying to install updates

for some reason you got a stack overrun where something overwrote beyond its owned space an into a protective buffer used to catch stack overruns. When this happen the system called a bugcheck.

STACK_COOKIE_CHECK_FAILURE

you are running windows 8 so you should confirm your windows files by running cmd.exe as an admin
then
dism.exe /online /cleanup-image /restorehealth

I would also clear my windows update cache
https://rahuldpatel.wordpress.com/2008/12/02/clearing-windows-update-cache-upon-update-failure/

on the assumption that it is corrupted for some reason, then look for the reason it was corrupted. most likely reason for corruption would be malware/hack programs blocking updates, bad network driver.
suspect driver:\C:\Windows\system32\Drivers\uxstyle.sys Mon Sep 23 04:19:02 2013
The Within Network UxStyle Kernel Driver (I just don't know anything about this driver, it may be fine)

I would also change the memory dump type from minidump to kernel dump and run verifier.exe and reboot, then run with verifier.exe checking until you get the next bugcheck. minidumps strip out a lot of the debug info needed to figure out the cause of corruptions. Verifier.exe can help by forcing the memory dump at the time of the corruption rather than later when it is detected because something fails.

otherwise you should run cmd.exe as an admin, then run
verifier.exe /standard /all
to turn on driver checking until you get another bugcheck.
verifier.exe /reset
to turn it back off.