BSOD when I start playing Dota 2

kingfisher · 09 Feb 2014

I have never seen this error before. However, I got this error yesterday when trying to play Dota 2. I tried to format C drive, and re-installing Windows 7, I still got this error. Would you mind If I want to ask for help?
ps: this is my error after restarting from BSOD:

Code:

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7600.2.0.0.256.1
  Locale ID:    1033

Additional information about the problem:
  BCCode:    116
  BCP1:    FFFFFA8003D99010
  BCP2:    FFFFF88003B9E3F8
  BCP3:    0000000000000000
  BCP4:    0000000000000002
  OS Version:    6_1_7600
  Service Pack:    0_0
  Product:    256_1

Files that help describe the problem:
  C:\Windows\Minidump\020914-19780-01.dmp
  C:\Users\kingfisher_ph\AppData\Local\Temp\WER-46675-0.sysdata.xml

koolkat77 · 10 Feb 2014

Please follow the: Blue Screen of Death (BSOD) Posting Instructions

kingfisher · 11 Feb 2014

I followed all instructions. Here's my result.

koolkat77 · 11 Feb 2014

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\SF_11-02-2014\SF_11-02-2014\021014-23540-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`0308ce70
Debug session time: Mon Feb 10 17:33:05.828 2014 (UTC + 6:00)
System Uptime: 0 days 0:05:44.217
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8004f67010, fffff88003e073f8, 0, 2}

*** 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+73f8 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8004f67010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003e073f8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
atikmpag+73f8
fffff880`03e073f8 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03378988 fffff880`042e1000 : 00000000`00000116 fffffa80`04f67010 fffff880`03e073f8 00000000`00000000 : nt!KeBugCheckEx
fffff880`03378990 fffff880`042e0d0a : fffff880`03e073f8 fffffa80`04f67010 fffffa80`05c89d50 fffffa80`054d6010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`033789d0 fffff880`04387f07 : fffffa80`04f67010 00000000`00000000 fffffa80`05c89d50 fffffa80`054d6010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03378a00 fffff880`043b1b75 : 00000000`ffffffff 00000000`00005557 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03378ae0 fffff880`043b02bb : 00000000`00000102 00000000`00000008 00000000`00005557 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`03378b10 fffff880`043832c6 : ffffffff`ff676980 fffffa80`054d6010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03378bb0 fffff880`043afe7a : 00000000`00000000 fffffa80`05552d50 00000000`00000080 fffffa80`054d6010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03378cc0 fffff800`0315e47a : 00000000`fffffc32 fffffa80`06146060 fffffa80`03ca6b30 fffffa80`06146060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03378d00 fffff800`02e9dda6 : fffff880`009f0180 fffffa80`06146060 fffff880`009fafc0 fffff880`01228b14 : nt!PspSystemThreadStartup+0x5a
fffff880`03378d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+73f8
fffff880`03e073f8 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+73f8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e9bc523

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner
---------

2: kd> lmvm atikmpag
start             end                 module name
fffff880`03e00000 fffff880`03e4f000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Mon Oct 17 12:03:15 2011 (4E9BC523)
    CheckSum:         000544D9
    ImageSize:        0004F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Take your time and go through this guide: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

kingfisher · 11 Feb 2014

OMG, thank you very very very much. After following your instruction, I solved my BSOD by increasing the GPU processing time by adjusting the timeout detection and recovery registry value.