Black & Freeze Screen after PC started

angryfly · 05 Nov 2012

Since two months ago, I started getting black and frozen screen for no reason. Sometimes it would automatically recover itself and give a message "Display Driver AMD Stopped Responding Has Successfully Recovered" but other times, it would need a reset.

The last few days I was getting blue screen error message, see below.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: 897ED510
BCP2: 98D7460E
BCP3: 00000000
BCP4: 00000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Kindly advise what is wrong? Many thanks in advance.

Arc · 05 Nov 2012

Welcome aboard, angryfly.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {897ed510, 98d7460e, 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+760e )

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: 897ed510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 98d7460e, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+760e
98d7460e 8bff            mov     edi,edi

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
90ac35f0 9a9c607b 00000116 897ed510 98d7460e nt!KeBugCheckEx+0x1e
90ac3614 9a9ba937 98d7460e 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
90ac3638 98c0692c 00000000 00000000 90ac36f8 dxgkrnl!TdrIsRecoveryRequired+0xb8
90ac36b0 98c2dc1d fffffcfb 00002155 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
90ac36dc 98c205ed 874bf008 90ac36f8 00000102 dxgmms1!VidSchWaitForCompletionEvent+0x16f
90ac3758 98c21a74 890bd6a0 00000000 884f6000 dxgmms1!VIDMM_DMA_POOL::WaitDmaBufferNotBusy+0x91
90ac3780 98c150c8 884f6124 00000000 884f6000 dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x17c
90ac386c 98c15af4 884f6224 00000000 00000001 dxgmms1!VIDMM_GLOBAL::FlushPagingBufferInternal+0x3c6
90ac38ac 98c19acd 00000000 00000000 90ac38d4 dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+0x23e
90ac39f4 98c1bc76 00000000 00000001 00000003 dxgmms1!VIDMM_GLOBAL::MapVideoApertureSegmentInternal+0x11b
90ac3a34 98c2a0d2 ac692458 00000003 000006ec dxgmms1!VIDMM_GLOBAL::MapVideoApertureSegment+0xf8
90ac3a64 98c298f0 ac692458 000006ec 00000082 dxgmms1!VIDMM_APERTURE_SEGMENT::MapApertureRange+0x2c
90ac3a94 98c18edb ac692458 00000000 87f12870 dxgmms1!VIDMM_APERTURE_SEGMENT::CommitResource+0xe8
90ac3ac0 98c1a8b4 8a2c2800 00000003 87f0e2f0 dxgmms1!VIDMM_GLOBAL::PageInAllocations+0x8f
90ac3bb8 98c31850 90cb3380 00000000 87f12870 dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x95e
90ac3d18 98c32141 86c9ac78 85ff73b8 90ac3d3c dxgmms1!VidSchiSubmitRenderCommand+0x1c0
90ac3d28 98c323de 86c9ac78 8304abb9 874bf008 dxgmms1!VidSchiSubmitQueueCommand+0x61
90ac3d3c 98c32485 874bf008 00000000 890af538 dxgmms1!VidSchiRun_PriorityTable+0x24
90ac3d50 8321e07a 874bf008 b82f5d4f 00000000 dxgmms1!VidSchiWorkerThread+0x7f
90ac3d90 830c4819 98c32406 874bf008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+760e
98d7460e 8bff            mov     edi,edi

SYMBOL_NAME:  atikmpag+760e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5064f96a

FAILURE_BUCKET_ID:  0x116_IMAGE_atikmpag.sys

BUCKET_ID:  0x116_IMAGE_atikmpag.sys

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

2: kd> lmvm atikmpag
start    end        module name
98d6d000 98dcb000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Sep 28 06:42:10 2012 (5064F96A)
    CheckSum:         000648A6
    ImageSize:        0005E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Follow the guide STOP 0x116: VIDEO_TDR_ERROR troubleshooting step by step. If there is any question, ask us.