BSOD during video play on IE 10

imsnowman · 22 Jan 2015

I had not had any BSOD's since 5/19/2014. I recently got two, one on 1/11/2015 and one today. The only common thread I can find is I had several IE 10 tabs and windows open and one was playing a Vimeo or youtube video. I haven't changed any hardware in several months and no new programs that I know of. I've done a recent virus and malware scan using AVG Free 2015 and an up-to-date Spybot.
I've attached the zip file generated by dm log collector.
Any ideas?
Thanks.

Arc · 22 Jan 2015

Update the display driver. Download Drivers

Let us know the result after doing it.
___________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800dbb2260, fffff88004807bb8, 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+7bb8 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800dbb2260, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004807bb8, 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+7bb8
fffff880`04807bb8 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`0792c1c8 fffff880`064a1134 : 00000000`00000116 fffffa80`0dbb2260 fffff880`04807bb8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0792c1d0 fffff880`064a0e3e : fffff880`04807bb8 fffffa80`0dbb2260 fffffa80`0eac7950 fffffa80`0acf1010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0792c210 fffff880`06548f13 : fffffa80`0dbb2260 00000000`00000000 fffffa80`0eac7950 fffffa80`0acf1010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0792c240 fffff880`06576ed6 : fffffa80`ffffffff 00000000`000c42a5 fffff880`0792c390 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0792c320 fffff880`0655cce9 : fffffa80`0c0bf000 ffffffff`feced300 00000000`00000002 fffff880`0792c698 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`0792c360 fffff880`0655fbe7 : 00000000`00005fb1 00000000`00000000 00000000`00000040 fffff8a0`165478b0 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`0792c460 fffff880`0655e2d8 : fffff8a0`165478b0 00000000`00000000 fffffa80`0c0bf000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7
fffff880`0792c4a0 fffff880`0655e22e : 00000000`00000000 00000000`00000001 fffffa80`0c0bf000 fffff880`0655cb56 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+0x34
fffff880`0792c630 fffff880`0656777e : fffffa80`0bf62010 00000000`00000001 00000000`00000001 fffff800`030788f2 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegment+0x13e
fffff880`0792c6a0 fffff880`06567527 : fffff8a0`165478b0 00000000`00001000 fffffa80`0bf62010 fffff8a0`165478b0 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapApertureRange+0x7a
fffff880`0792c6f0 fffff880`06566ecb : fffff8a0`165478b0 fffffa80`0c0bfc80 00000000`00000000 fffffa80`0c0bfc80 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapTemporaryResource+0x9b
fffff880`0792c750 fffff880`0655a8a4 : fffffa80`0c0bf000 fffffa80`0c0bf000 fffffa80`0c0bfc80 fffffa80`0c0bf000 : dxgmms1!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource+0xcf
fffff880`0792c790 fffff880`06557257 : 00000000`00000000 00000000`00000000 00000000`00000027 fffffa80`0c0bf000 : dxgmms1!VIDMM_GLOBAL::EvictTemporaryAllocations+0xbc
fffff880`0792c7d0 fffff880`065717d9 : 00000000`00000000 fffff8a0`16917860 fffffa80`00000000 fffffa80`0ce99a10 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x69f
fffff880`0792c9a0 fffff880`06571514 : fffff880`0348e040 fffff880`06570f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0792cb90 fffff880`06571012 : 00000000`00000000 fffffa80`0b9c8010 00000000`00000080 fffffa80`0acf1010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0792cbc0 fffff800`0331f0ca : 00000000`fffffc32 fffffa80`0bfa4060 fffffa80`06cf2040 fffffa80`0bfa4060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0792cc00 fffff800`03073be6 : fffff880`03489180 fffffa80`0bfa4060 fffff880`034940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0792cc40 00000000`00000000 : fffff880`0792d000 fffff880`07927000 fffff880`0d1b3d40 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+7bb8
fffff880`04807bb8 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+7bb8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ea4ec26

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys

FAILURE_ID_HASH:  {83e844bc-fe68-2042-4230-7f5d3e90b48a}

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

0: kd> lmvm atikmpag
start             end                 module name
fffff880`04800000 fffff880`04851000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Mon Oct 24 10:10:06 2011 (4EA4EC26)
    CheckSum:         0005917F
    ImageSize:        00051000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

imsnowman · 22 Jan 2015

The AMD program said that my driver is up-to-date.

Arc · 23 Jan 2015

You sure? The driver dates October 2011.

imsnowman · 23 Jan 2015

Not sure where you got that date.
The program I downloaded with that link said it was up-to-date and device manager has a date of 11/20/2014 for AMD Radeon HD 6670.

imsnowman · 23 Jan 2015

Device manager also reports two instances of keyboard and mouse drivers even though I only have one of each operating. Does that mean anything?

Arc · 23 Jan 2015

imsnowman said:

Not sure where you got that date.

I have nothing but what you uploaded. Scroll down to teh bottom of the crash dump report posted in post #2.

Image name: atikmpag.sys
Timestamp: Mon Oct 24 10:10:06 2011 (4EA4EC26)

imsnowman · 23 Jan 2015

OK. I don't think the program I downloaded and ran to update the video driver looked at ATI drivers just AMD.
I just ran Device Manager and right clicked the AMD Radeon HD 6670 driver line and ran "Update Driver Software". It searched online and replaced the 11/20/2014 driver with one dated 4/25/2012 according to DM.
I searched for atikmpag.sys. It's in C:\Windows\System32\drivers and has a 4/26/2012 date modified date.
Device manager also reports two identical instances of keyboard and mouse drivers even though I only have one of each operating. Does that mean anything?
So what do you recommend I do now? Keep the new older driver? Uninstall one of the keyboard/mouse drivers?
Unfortunately (?) this doesn't happen often enough to be sure it's really fixed.
Thanks for you help!

Arc · 24 Jan 2015

Apparently, I will suggest you for now to use the computer normally. If it BSODs again, let us see the dumps. We will check the situation then again.

Will that be a bad plan?

BSOD during video play on IE 10

BSOD during video play on IE 10

Updated driver