Microsoft (R) Windows Debugger Version 6.6.0003.

5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\komputer\Desktop\071113-22479-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Kernel base = 0xfffff800`02e06000 PsLoadedModuleList = 0xfffff800`03049670
Debug session time: Thu Jul 11 01:25:34.148 2013 (GMT+2)
System Uptime: 0 days 2:47:55.381
Loading Kernel Symbols
................................................................................
.....................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*
*
*
Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80074534e0, fffff88004484cf0, 0, d}
*************************************************************************
***
***
***
***
***
Your debugger is not using the correct symbols
***
***
***
***
In order for this command to work properly, your symbol path ***
***
must point to .pdb files that have full type information.
***
***
***
***
Certain .pdb files (such as the public OS symbols) do not
***
***
contain the required information. Contact the group that
***
***
provided you with these symbols if you need this command to
***
***
work.
***
***
***
***
Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT
***
***
***
*************************************************************************
*************************************************************************
***
***
***
***
***
Your debugger is not using the correct symbols
***
***
***
***
In order for this command to work properly, your symbol path ***
***
must point to .pdb files that have full type information.
***
***
***
***
Certain .pdb files (such as the public OS symbols) do not
***
***
contain the required information. Contact the group that
***
***
provided you with these symbols if you need this command to
***
***
work.
***
***
***

***
Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT
***
***
***
*************************************************************************
*************************************************************************
***
***
***
***
***
Your debugger is not using the correct symbols
***
***
***
***
In order for this command to work properly, your symbol path ***
***
must point to .pdb files that have full type information.
***
***
***
***
Certain .pdb files (such as the public OS symbols) do not
***
***
contain the required information. Contact the group that
***
***
provided you with these symbols if you need this command to
***
***
work.
***
***
***
***
Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT
***
***
***
*************************************************************************
*************************************************************************
***
***
***
***
***
Your debugger is not using the correct symbols
***
***
***
***
In order for this command to work properly, your symbol path ***
***
must point to .pdb files that have full type information.
***
***
***
***
Certain .pdb files (such as the public OS symbols) do not
***
***
contain the required information. Contact the group that
***
***
provided you with these symbols if you need this command to
***
***
work.
***
***
***
***
Type referenced: dxgkrnl!DXGADAPTER
***
***
***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sy
s
Probably caused by : atikmpag.sys ( atikmpag+acf0 )
Followup: MachineOwner
--------3: kd> !analyze -v
*******************************************************************************
*
*
*
Bugcheck Analysis
*
*
*
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80074534e0, Optional pointer to internal TDR recovery context (TDR_R
ECOVERY_CONTEXT).
Arg2: fffff88004484cf0, The pointer into responsible device driver module (e.g.
owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operat
ion.

Arg4: 000000000000000d, Optional internal context dependent data.

Debugging Details:
-----------------*************************************************************************
***
***
***
***
***
Your debugger is not using the correct symbols
***
***
***
***
In order for this command to work properly, your symbol path ***
***
must point to .pdb files that have full type information.
***
***
***
***
Certain .pdb files (such as the public OS symbols) do not
***
***
contain the required information. Contact the group that
***
***
provided you with these symbols if you need this command to
***
***
work.
***
***
***
***
Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT
***
***
***
*************************************************************************
*************************************************************************
***
***
***
***
***
Your debugger is not using the correct symbols
***
***
***
***
In order for this command to work properly, your symbol path ***
***
must point to .pdb files that have full type information.
***
***
***
***
Certain .pdb files (such as the public OS symbols) do not
***
***
contain the required information. Contact the group that
***
***
provided you with these symbols if you need this command to
***
***
work.
***
***
***
***
Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT
***
***
***
*************************************************************************
*************************************************************************
***
***
***
***
***
Your debugger is not using the correct symbols
***
***
***
***
In order for this command to work properly, your symbol path ***
***
must point to .pdb files that have full type information.
***
***
***
***
Certain .pdb files (such as the public OS symbols) do not
***
***
contain the required information. Contact the group that
***
***
provided you with these symbols if you need this command to
***
***
work.
***
***
***
***
Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT
***
***
***
*************************************************************************
*************************************************************************
***
***
***
***
***
Your debugger is not using the correct symbols
***
***
***
***
In order for this command to work properly, your symbol path ***
***
must point to .pdb files that have full type information.
***

***
***
***
Certain .pdb files (such as the public OS symbols) do not
***
***
contain the required information. Contact the group that
***
***
provided you with these symbols if you need this command to
***
***
work.
***
***
***
***
Type referenced: dxgkrnl!DXGADAPTER
***
***
***
*************************************************************************
FAULTING_IP:
atikmpag+acf0
fffff880`04484cf0 4055

push

rbp

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT fffffa80074534e0

*************************************************************************
***
***
***
***
***
Your debugger is not using the correct symbols
***
***
***
***
In order for this command to work properly, your symbol path ***
***
must point to .pdb files that have full type information.
***
***
***
***
Certain .pdb files (such as the public OS symbols) do not
***
***
contain the required information. Contact the group that
***
***
provided you with these symbols if you need this command to
***
***
work.
***
***
***
***
Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT
***
***
***
*************************************************************************
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_BETA2
BUGCHECK_STR: 0x116
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`05a44888 fffff880`05673054 : 00000000`00000116 fffffa80`074534e0 fffff8
80`04484cf0 00000000`00000000 : nt!KeBugCheckEx
fffff880`05a44890 fffff880`05672ddb : fffff880`04484cf0 fffffa80`074534e0 000000
00`00000000 fffffa80`089c9010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05a448d0 fffff880`05719f13 : fffffa80`074534e0 00000000`00000000 000000
00`00000000 fffffa80`089c9010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`05a44900 fffff880`05743d50 : fffffa80`00000000 00000000`0009da2d 000000
00`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05a449e0 fffff880`05742437 : 00000000`00000102 00000000`00000000 000000
00`0009da2d 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
fffff880`05a44a10 fffff880`057152d2 : ffffffff`ff676980 fffffa80`089c9010 000000
00`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`05a44ab0 fffff880`05741ff6 : 00000000`00000000 fffffa80`06fdfd50 000000
00`00000080 fffffa80`089c9010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05a44bc0 fffff800`03119ede : 00000000`fffffc32 fffffa80`08078b50 fffffa
80`066d6040 fffffa80`08078b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05a44c00 fffff800`02e6c906 : fffff800`02ff6e80 fffffa80`08078b50 fffff8
00`03004cc0 467a7339`75446231 : nt!PspSystemThreadStartup+0x5a

fffff880`05a44c40 00000000`00000000 : 00000000`00000000 00000000`00000000 000000

00`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmpag+acf0
fffff880`04484cf0 4055

push

FAULTING_SOURCE_CODE:

rbp

FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: atikmpag+acf0
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5154e9d9
FAILURE_BUCKET_ID: X64_0x116_atikmpag+acf0
BUCKET_ID: X64_0x116_atikmpag+acf0
Followup: MachineOwner
---------