BSOD Display Driver Problem

Welcome to the forum,

I'm no expert but what you can try while you wait for one is updating your display driver as it is what is being named as probably caused by,

Driver Reference Table - atikmpag.sys

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\Derek\AppData\Local\Temp\Temp1_Seven Forums (2).zip\Seven Forums\081812-31933-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 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0304a000 PsLoadedModuleList = 0xfffff800`0328e670
Debug session time: Sat Aug 18 09:03:06.965 2012 (UTC - 7:00)
System Uptime: 0 days 0:26:16.619
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8004af1010, fffff88004441ebc, ffffffffc0000001, 3}
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
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : atikmpag.sys ( atikmpag+6ebc )
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: fffffa8004af1010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004441ebc, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.
Debugging Details:
------------------
 
FAULTING_IP: 
atikmpag+6ebc
fffff880`04441ebc 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`023fe718 fffff880`02ef9000 : 00000000`00000116 fffffa80`04af1010 fffff880`04441ebc ffffffff`c0000001 : nt!KeBugCheckEx
fffff880`023fe720 fffff880`02ecc569 : fffff880`04441ebc fffffa80`05f23000 00000000`00000000 fffffa80`05455010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`023fe760 fffff880`02ef8dad : fffffa80`04af1010 fffffa80`04af1010 fffffa80`04af1010 fffffa80`05455010 : dxgkrnl!DXGADAPTER::PrepareToReset+0x109
fffff880`023fe7a0 fffff880`02f9ff07 : fffffa80`04af1010 00000000`00000000 fffffa80`043f34f0 fffffa80`05455010 : dxgkrnl!TdrIsRecoveryRequired+0x245
fffff880`023fe7d0 fffff880`02fcdd5a : fffff8a0`ffffffff 00000000`000186dd fffff880`023fe930 fffffa80`05455010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`023fe8b0 fffff880`02fc9ca5 : fffffa80`033d2000 ffffffff`feced300 fffffa80`0675ec00 fffffa80`06e30c68 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`023fe8f0 fffff880`02fc9e5d : fffffa80`033d2000 fffffa80`05455010 00000000`59585000 00000000`00000000 : dxgmms1!VidSchiWaitForCompletePreemption+0x7d
fffff880`023fe9e0 fffff880`02fc8d3c : 00000000`0000001f 00000000`00020c76 fffffa80`0675ec00 fffffa80`05455010 : dxgmms1!VidSchiSendToExecutionQueueWithWait+0x171
fffff880`023feae0 fffff880`02fc8398 : fffff880`03167f00 fffff880`02fc7d00 fffffa80`00000000 fffffa80`000036e0 : dxgmms1!VidSchiSubmitRenderCommand+0x920
fffff880`023fecd0 fffff880`02fc7e96 : 00000000`00000000 fffffa80`043f34f0 00000000`00000080 fffffa80`05455010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`023fed00 fffff800`0335fe6a : 00000000`0268cee4 fffffa80`05d9bb50 fffffa80`033c8ae0 fffffa80`05d9bb50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`023fed40 fffff800`030b9ec6 : fffff880`03163180 fffffa80`05d9bb50 fffff880`0316df80 3078302c`3078302c : nt!PspSystemThreadStartup+0x5a
fffff880`023fed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
atikmpag+6ebc
fffff880`04441ebc 4883ec28        sub     rsp,28h
SYMBOL_NAME:  atikmpag+6ebc
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4cc990cb
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
---------

Try updating your driver here,

AMD Support & Drivers

I'm no expert but it seems like you could turn your computer off with the on/off button w/o using the start menu.

that being said, i had a similar problem when latest version of GeForce was dl'ed

tried everything and couldn't fix it until finally i read a post that said:

turn off automatic windows update

restart computer and tap F8 until you get the options for system start up, scroll down to last known good configuration and restart computer.

this fixed my problem, until i updated my flash player, which appears to have automatically updated my display driver again, so I had to do it over again

something about this latest driver screwed me up

Hope this helps

Thanks for the tips. The on/off button does not work when this problem happens, but I will try the other solutions that were mentioned. Thanks again.

I updated my driver, but I still have this problem. Can anyone tell me how to disable the BIOS cache and shadowing? That is what my blue screen asks me to do.