BSOD using VIMEO?

qnqtknguyen · Mar 29, 2015

Hello,

I got a BSOD twice recently. I'm not sure if it had to do with VIMEO because I was on that website, and there was some error message about the ATI card.

I've attached the minidump.

Thanks for your help.

koolkat77 · Mar 31, 2015

Your ATI graphics driver need to be updated.

Also use this for reference :ar: http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

Code:

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


Loading Dump File [C:\Users\YUSSI\Downloads\Compressed\QUANG-PC-Sun_03_29_2015_144923_63\032915-24991-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
Machine Name:
Kernel base = 0xfffff800`03c54000 PsLoadedModuleList = 0xfffff800`03e98890
Debug session time: Sun Mar 29 11:04:24.194 2015 (UTC + 6:00)
System Uptime: 1 days 20:04:15.708
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8007558360, fffff880048e47f8, 0, 2}

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+127f8 )

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: fffffa8007558360, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880048e47f8, 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: 
atikmdag+127f8
fffff880`048e47f8 48895c2408      mov     qword ptr [rsp+8],rbx

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.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`067e4308 fffff880`04f46134 : 00000000`00000116 fffffa80`07558360 fffff880`048e47f8 00000000`00000000 : nt!KeBugCheckEx
fffff880`067e4310 fffff880`04f45e3e : fffff880`048e47f8 fffffa80`07558360 fffffa80`071f36c0 fffffa80`05087410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`067e4350 fffff880`0480ff13 : fffffa80`07558360 00000000`00000000 fffffa80`071f36c0 fffffa80`05087410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`067e4380 fffff880`0483ded6 : fffffa80`ffffffff 00000000`009b2e5d fffff880`067e44d0 00000000`00000001 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`067e4460 fffff880`04823ce9 : fffffa80`065de000 ffffffff`feced300 00000000`00000001 fffff880`067e47d8 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`067e44a0 fffff880`04826be7 : 00000000`00020052 00000000`00000000 fffffa80`060afae0 fffff8a0`0012b740 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`067e45a0 fffff880`048252d8 : fffff8a0`0012b740 00000000`00000000 fffffa80`065de000 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7
fffff880`067e45e0 fffff880`0482522e : 00000000`00000000 00000000`00000001 fffffa80`065de000 fffff880`04823b56 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+0x34
fffff880`067e4770 fffff880`0482e77e : fffffa80`065e7d50 00000000`00000001 00000000`00000001 fffff800`03cce0f2 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegment+0x13e
fffff880`067e47e0 fffff880`0482e527 : fffff8a0`0012b740 00000000`00001000 fffffa80`065e7d50 fffff8a0`0012b740 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapApertureRange+0x7a
fffff880`067e4830 fffff880`0482decb : fffff8a0`0012b740 fffffa80`065dec80 00000000`00000000 fffffa80`065dec80 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapTemporaryResource+0x9b
fffff880`067e4890 fffff880`048218a4 : fffffa80`065de000 fffffa80`065de000 fffffa80`065dec80 fffffa80`065de000 : dxgmms1!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource+0xcf
fffff880`067e48d0 fffff880`0481e257 : 00000000`c0000001 00000000`00000000 00000000`00000006 fffffa80`065de000 : dxgmms1!VIDMM_GLOBAL::EvictTemporaryAllocations+0xbc
fffff880`067e4910 fffff880`048387d9 : 00000000`00000000 fffff8a0`00130980 fffffa80`00000001 fffffa80`07639af0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x69f
fffff880`067e4ae0 fffff880`04838514 : fffff880`009f3ec0 fffff880`04837f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`067e4cd0 fffff880`04838012 : 00000000`00000000 fffffa80`071f36c0 00000000`00000080 fffffa80`05087410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`067e4d00 fffff800`03f67b8a : 00000000`fffffc32 fffffa80`06292b50 fffffa80`03cce040 fffffa80`06292b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`067e4d40 fffff800`03cba8e6 : fffff880`009ef180 fffffa80`06292b50 fffff880`009f9f40 52545356`412c3078 : nt!PspSystemThreadStartup+0x5a
fffff880`067e4d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmdag+127f8
fffff880`048e47f8 48895c2408      mov     qword ptr [rsp+8],rbx

SYMBOL_NAME:  atikmdag+127f8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a8a1a8b

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmdag.sys

FAILURE_ID_HASH:  {7527b2fa-489f-c504-9452-1a10bd154401}

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

1: kd> lmvm atikmdag
start             end                 module name
fffff880`048d2000 fffff880`04ee9000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Tue Aug 18 09:05:47 2009 (4A8A1A8B)
    CheckSum:         005CE06B
    ImageSize:        00617000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

BSOD using VIMEO?

qnqtknguyen

New member

My Computer

koolkat77

New member

My Computer

Similar threads