BSOD while playing Dota 2. (Only when playing Dota 2)

Please help me, I'm always encountering BSOD when I opened applications in the past. I formatted my pc and changed OS. My PC got good on Windows 7 Ultimate 32-bit in opening browsers but when I played Dota 2, I found out something, it always occurs only when playing Dota 2. This is the archive file Attachment 361654 Please help me ASAP. I'm always "Abandon" in my games Thanks in advance.
[Edit]
Here's the zip file Attachment 361846

Hello and welcome Joshua mate we need the dump files - or at least I do see these and post back

Dump Files - Configure Windows to Create on BSOD
&
Blue Screen of Death (BSOD) Posting Instructions

Well mate you may have to wait for someone that can open RAR files as I can't - sorry.

Ok Joshua that is so much better mate and I am so sorry you have had THAT much trouble for starters I would recommend you uninstall the Catalyst Control Centre as it is prominent in the last dump.

Try running the machine in safe mode if you have to - to do that and we shall see where we are going hopefully.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {859d5510, 8da24188, 0, c}
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+9188 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 859d5510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 8da24188, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000c, Optional internal context dependent data.
Debugging Details:
------------------

FAULTING_IP: 
atikmpag+9188
8da24188 8bff            mov     edi,edi
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x116
PROCESS_NAME:  dota.exe
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
8c4f255c 99b5a07b 00000116 859d5510 8da24188 nt!KeBugCheckEx+0x1e
8c4f2580 99b4e937 8da24188 00000000 0000000c dxgkrnl!TdrBugcheckOnTimeout+0x8d
8c4f25a4 99b8a92c 009d5510 00000000 8c4f2668 dxgkrnl!TdrIsRecoveryRequired+0xb8
8c4f261c 99bb1c1d fffffcfb 00041d18 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8c4f2648 99b9b44b 86dd1008 8c4f2668 00000102 dxgmms1!VidSchWaitForCompletionEvent+0x16f
8c4f26e0 99b9caaf b364df80 00000008 00000000 dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x181
8c4f26f8 99bac751 b3712ad0 86ecb510 8c4f2794 dxgmms1!VIDMM_GLOBAL::WaitForAllPagingEngines+0x1b
8c4f2710 82def53b 8c4f2734 8c4f2794 8c4f28ec dxgmms1!VIDMM_MEMORY_SEGMENT::RotateCopyCallback+0x87
8c4f283c 99ba5ce1 3c973000 8c4f2884 00000000 nt!MmRotatePhysicalView+0x59c
8c4f288c 99bacce0 930b0f40 00000002 00000000 dxgmms1!VIDMM_PROCESS_HEAP::Rotate+0xe1
8c4f2978 99b96ac7 b3712ad0 00000001 86ecc838 dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x4b2
8c4f299c 99b9cdac 86ecc840 00000000 86ecc824 dxgmms1!VIDMM_GLOBAL::EvictAllAllocationInList+0x2f
8c4f29c0 99b9e87b 00000000 00000000 00000000 dxgmms1!VIDMM_GLOBAL::EvictAllReclaimedAllocation+0x2a
8c4f2ab8 99bb5850 a567b108 00000000 85e60d50 dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x925
8c4f2c18 99bb6141 85e98370 84e5b3e0 8c4f2c3c dxgmms1!VidSchiSubmitRenderCommand+0x1c0
8c4f2c28 99bb63de 85e98370 82c5650e 86dd1008 dxgmms1!VidSchiSubmitQueueCommand+0x61
8c4f2c3c 99bb6485 86dd1008 00000000 86ecb510 dxgmms1!VidSchiRun_PriorityTable+0x24
8c4f2c50 82e28f5e 86dd1008 a9c40b67 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8c4f2c90 82cd0219 99bb6406 86dd1008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
atikmpag+9188
8da24188 8bff            mov     edi,edi
SYMBOL_NAME:  atikmpag+9188
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  546e9eb0
FAILURE_BUCKET_ID:  0x116_IMAGE_atikmpag.sys
BUCKET_ID:  0x116_IMAGE_atikmpag.sys
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:0x116_image_atikmpag.sys
FAILURE_ID_HASH:  {e300aa8c-6915-3f37-7957-d2e4fc30a6fd}
Followup: MachineOwner

If I may; I did notice a problem.

John you could be working with a infected computer.

From joshua aquino 1 My System Specs.

Antivirus None