Display Driver Stopped Responding

[MinisitePro]

Hello,

I keep getting a "display driver has stopped responding and has recovered" error message and then the system freezes every half hour/hour.

I ran the SF Diagnostic Tool in Admin mode but it wouldn't let me run minidump (even as Admin) - keep getting "Unhandled exception has occurred ..."

Anyway, I've attached the zip file.

Any help would be much appreciated.

- Dave

 

[writhziden]

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [K:\BSODDmpFiles\MinisitePro\Seven Forums\020112-62150-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`0305e670
Debug session time: Wed Feb  1 09:15:22.621 2012 (GMT-7)
System Uptime: 0 days 0:25:19.745
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800f919010, fffff880096073bc, 0, 2}

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+73bc )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800f919010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880096073bc, 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+73bc
fffff880`096073bc 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`02119758 fffff880`04eb9000 : 00000000`00000116 fffffa80`0f919010 fffff880`096073bc 00000000`00000000 : nt!KeBugCheckEx
fffff880`02119760 fffff880`04eb8d0a : fffff880`096073bc fffffa80`0f919010 fffffa80`0d2e8d50 fffffa80`0e681410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`021197a0 fffff880`04f5ff07 : fffffa80`0f919010 00000000`00000000 fffffa80`0d2e8d50 fffffa80`0e681410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`021197d0 fffff880`04f8dd5a : 00000000`ffffffff 00000000`00017969 fffff880`02119930 fffffa80`0e681410 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`021198b0 fffff880`04f896af : fffffa80`0e681410 ffffffff`feced300 00000000`00000000 fffffa80`11df0c80 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`021198f0 fffff880`04f88023 : fffffa80`0e681410 00000000`00000002 fffff880`02119a50 fffff880`02119a40 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`021199e0 fffff880`04f882fe : 00000000`00000000 00000000`00000002 00000003`00000380 fffffa80`0f651010 : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`02119a10 fffff880`04f5b2c6 : ffffffff`ff676980 fffffa80`0e681410 00000000`00000080 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`02119ab0 fffff880`04f87e7a : fffffa80`0d2e8d50 fffffa80`0d2e8d50 00000000`00000080 fffffa80`0e681410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02119bc0 fffff800`03130fee : 00000000`000000f0 fffffa80`0eb17b60 fffffa80`0cd4d9e0 fffff800`02e8d757 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02119c00 fffff800`02e875e6 : fffff800`0300be80 fffffa80`0eb17b60 fffff800`03019cc0 fffff880`01254a20 : nt!PspSystemThreadStartup+0x5a
fffff880`02119c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+73bc
fffff880`096073bc 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+73bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d409c8d

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

These are all stop 0x116 VIDEO_TDR_FAILURE conditions.

It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash. As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds. If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling.

The above quote was taken from http://www.sevenforums.com/crashes-debugging/25912-bsod.html#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html and proceed through each step. Let us know if you need further help.

 

[MinisitePro]

ok thanks. it's a brand new machine so it's definately not a dust problem.

 

[writhziden]

ok thanks. it's a brand new machine so it's definately not a dust problem.

Did you build it, or was it built for you? How old are the parts? The installation?

 

[MinisitePro]

i had a company put it together. They are going to send me a new graphics card to try.

 

[writhziden]

Alright, let us know how it goes.

 

[MinisitePro]

will do. thanks for your time

 

[writhziden]

You are welcome.

 

[ms8miranda]

Was this problem ever resolved? I am having this problem, too, as well as many others (as I found in searching for answers).

 

[writhziden]

I too would be interested in whether or not replacing your graphics card resolved the problem.

ms8miranda, you are welcome to follow this thread and see if the original poster responds. I would also suggest starting a new thread following the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html so you can get the dedicated help you need.

 

[ms8miranda]

I would also suggest starting a new thread following the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html so you can get the dedicated help you need

I followed instructions but when perfmon / report, I get window saying "The parameter is incorrect."

This exact same problem is happening to many, many people so I know there has to be one solution to address this problem....I just wonder if anyone has figured it out yet.

 

[writhziden]

The problem happens to multiple people with different software, different graphics cards, different motherboards, different CPUs, different memory modules, different power supplies... It probably does not have just one solution due to these and many other things.

The perfmon report is not incredibly important. We often do not get it from users running Safe Mode because they cannot get Windows to run normally.

 

[ms8miranda]

From what I've read in searching for the answer, we all have Windows 7, 64 bit.

The problem happens to multiple people with different software, different graphics cards, different motherboards, different CPUs, different memory modules, different power supplies... It probably does not have just one solution due to these and many other things.

The perfmon report is not incredibly important. We often do not get it from users running Safe Mode because they cannot get Windows to run normally.