Problemas com hardware de vídeo?

C.R.E.A.M. · 3 de agosto de 2016

Boa Noite

Quando liguei o PC esta noite ele tava com a seguinte notificação.

Depois disso cliquei em procurar soluções para esses problemas e apareceu isso.

Devo me preocupar com esses dois erros? Se sim, qual a maneira para resolver?

Grato

Hqxriven · 3 de agosto de 2016

Se quiser eu posso tentar dar uma olhada pra saber o que ocasionou isso aí.

Os arquivos geralmente ficam em C:\Windows\Minidump poste em algum lugar o arquivo que vou analisar o registro.

C.R.E.A.M. · 4 de agosto de 2016

@Hqxriven

Obrigado pela ajuda.

Entrei nessa pasta e esta totalmente vazia. O que mais preciso fazer para fornecer esses dados?

Grato

Hqxriven · 4 de agosto de 2016

Vazia? Vish.

Algum programa de limpeza passou por aí ou pode estar em outro diretório.

Se não for muito incômodo poderia executar o o Everything (programa para localizar arquivos) https://www.voidtools.com/Everything-1.3.4.686.x86.Multilingual.zip e ver se o arquivo está escondido em algum local?

C.R.E.A.M. · 4 de agosto de 2016

@Hqxriven Vou fazer esse procedimento agora, já posto resultados.

Eu abri o programa e pediu para abrir como adm, eu tenho que instalar ele ou só extrair e abrir? E quais arquivos eu devo procurar ali na procura?

Hqxriven · 4 de agosto de 2016

O que coloquei acima é portátil. Só abrir.

Digita .dmp e veja arquivos que terminam com essa extensão.

C.R.E.A.M. · 4 de agosto de 2016

@Hqxriven Resultado da pesquisa

Hqxriven · 4 de agosto de 2016

Os dois com WD na pasta C:\Windows\LivekernelReports\WatchDOG

C.R.E.A.M. · 5 de agosto de 2016

http://www.mirrorcreator.com/files/1LOALL4C/

http://www.mirrorcreator.com/files/1CIDGGYG/

@Hqxriven

Esses?

Hqxriven · 5 de agosto de 2016

baixando! Já volto!

1349.dmp

Loading Dump File [D:\Downloads\Downloads\WD-20160511-1349.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*D:\Symbols*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.23418.amd64fre.win7sp1_ldr.160408-2045
Machine Name:
Kernel base = 0xfffff800`02e17000 PsLoadedModuleList = 0xfffff800`03059730
Debug session time: Wed May 11 13:49:59.284 2016 (UTC - 3:00)
System Uptime: 0 days 0:01:47.502
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
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa8009b29150, fffff880040f1cac, 0, 0}

*** 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+ccac )

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

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: fffffa8009b29150, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880040f1cac, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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

FAULTING_IP:
atikmpag+ccac
fffff880`040f1cac ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

BUGCHECK_STR: 0x117

PROCESS_NAME: System

CURRENT_IRQL: 0

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

STACK_TEXT:
fffff880`052e22c0 fffff880`03c847e7 : fffffa80`09b29150 102906c9`a00038bf 00000000`00000000 fffffa80`08739901 : watchdog!WdDbgReportRecreate+0xa3
fffff880`052e27e0 fffff880`03c85265 : fffff8a0`0cd7effc fffff8a0`0c223ce0 fffff8a0`0cc27c03 00000000`001573f9 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`052e2830 fffff880`03c85ed2 : fffffa80`09b29150 fffffa80`09b29150 fffffa80`0689c450 fffffa80`08739010 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d
fffff880`052e28d0 fffff880`03d2dfbf : fffffa80`09b29150 00000000`00000000 fffffa80`0689c450 fffffa80`08739010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`052e2900 fffff880`03d57d09 : 00000000`ffffffff 00000000`00001a4b 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`052e29e0 fffff880`03d5644f : 00000000`00000102 00000000`00000007 00000000`00001a4b 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`052e2a10 fffff880`03d292e6 : ffffffff`ff676980 fffffa80`08739010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`052e2ab0 fffff880`03d5600e : 00000000`00000000 fffffa80`087ce510 00000000`00000080 fffffa80`08739010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`052e2bc0 fffff800`0311ebc6 : 00000000`0288e530 fffffa80`087bf060 fffffa80`066d0b10 fffffa80`087bf060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`052e2c00 fffff800`02e786a6 : fffff880`009ef180 fffffa80`087bf060 fffff880`009f9f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`052e2c40 00000000`00000000 : fffff880`052e3000 fffff880`052dd000 fffff880`052e1440 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+ccac
fffff880`040f1cac ?? ???

SYMBOL_NAME: atikmpag+ccac

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 55c01884

FAILURE_BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x117_image_atikmpag.sys

FAILURE_ID_HASH: {fa4b6286-8c4a-e9c2-c89f-5612619e000e}

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

1546.dmp

Loading Dump File [D:\Downloads\Downloads\WD-20160521-1546.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*D:\Symbols*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.23418.amd64fre.win7sp1_ldr.160408-2045
Machine Name:
Kernel base = 0xfffff800`02e60000 PsLoadedModuleList = 0xfffff800`030a2730
Debug session time: Sat May 21 15:46:37.191 2016 (UTC - 3:00)
System Uptime: 0 days 0:01:19.409
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
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa80088b44e0, fffff88003ee3cac, 0, 0}

Unable to load image 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+ccac )

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

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: fffffa80088b44e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003ee3cac, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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

FAULTING_IP:
atikmpag+ccac
fffff880`03ee3cac ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

BUGCHECK_STR: 0x117

PROCESS_NAME: System

CURRENT_IRQL: 0

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

STACK_TEXT:
fffff880`052e8190 fffff880`042967e7 : fffffa80`088b44e0 fffff8a0`0ca825de fffff8a0`0cb3d035 fffff880`04296529 : watchdog!WdDbgReportRecreate+0xa3
fffff880`052e86b0 fffff880`04297265 : fffff8a0`0cbd9ffc fffff8a0`01a5b640 fffff8a0`0ca825de 00000000`00157a1e : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`052e8700 fffff880`04297ed2 : fffffa80`088b44e0 fffffa80`088b44e0 fffffa80`0a290590 fffffa80`085f5010 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d
fffff880`052e87a0 fffff880`0433ffbf : fffffa80`088b44e0 00000000`00000000 fffffa80`0a290590 fffffa80`085f5010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`052e87d0 fffff880`0436deee : 00000000`ffffffff 00000000`000012f1 fffff880`052e8930 fffffa80`085f5010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`052e88b0 fffff880`04369843 : fffffa80`085f5010 ffffffff`feced300 00000000`00000002 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`052e88f0 fffff880`043681b7 : fffffa80`085f5010 00000000`00000002 fffff880`04367f54 00000000`00000000 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`052e89e0 fffff880`04368492 : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`052e8a10 fffff880`0433b2e6 : ffffffff`ff676980 fffffa80`085f5010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`052e8ab0 fffff880`0436800e : 00000000`00000000 fffffa80`0a4ab950 00000000`00000080 fffffa80`085f5010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`052e8bc0 fffff800`03167bc6 : 00000000`02243319 fffffa80`08131060 fffffa80`066d0b10 fffffa80`08131060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`052e8c00 fffff800`02ec16a6 : fffff800`0304ee80 fffffa80`08131060 fffff800`0305ccc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`052e8c40 00000000`00000000 : fffff880`052e9000 fffff880`052e3000 fffff880`052e7310 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+ccac
fffff880`03ee3cac ?? ???

SYMBOL_NAME: atikmpag+ccac

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 55c01884

FAILURE_BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x117_image_atikmpag.sys

FAILURE_ID_HASH: {fa4b6286-8c4a-e9c2-c89f-5612619e000e}

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

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: fffffa80088b44e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003ee3cac, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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

FAULTING_IP:
atikmpag+ccac
fffff880`03ee3cac ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

BUGCHECK_STR: 0x117

PROCESS_NAME: System

CURRENT_IRQL: 0

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

STACK_TEXT:
fffff880`052e8190 fffff880`042967e7 : fffffa80`088b44e0 fffff8a0`0ca825de fffff8a0`0cb3d035 fffff880`04296529 : watchdog!WdDbgReportRecreate+0xa3
fffff880`052e86b0 fffff880`04297265 : fffff8a0`0cbd9ffc fffff8a0`01a5b640 fffff8a0`0ca825de 00000000`00157a1e : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`052e8700 fffff880`04297ed2 : fffffa80`088b44e0 fffffa80`088b44e0 fffffa80`0a290590 fffffa80`085f5010 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d
fffff880`052e87a0 fffff880`0433ffbf : fffffa80`088b44e0 00000000`00000000 fffffa80`0a290590 fffffa80`085f5010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`052e87d0 fffff880`0436deee : 00000000`ffffffff 00000000`000012f1 fffff880`052e8930 fffffa80`085f5010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`052e88b0 fffff880`04369843 : fffffa80`085f5010 ffffffff`feced300 00000000`00000002 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`052e88f0 fffff880`043681b7 : fffffa80`085f5010 00000000`00000002 fffff880`04367f54 00000000`00000000 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`052e89e0 fffff880`04368492 : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`052e8a10 fffff880`0433b2e6 : ffffffff`ff676980 fffffa80`085f5010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`052e8ab0 fffff880`0436800e : 00000000`00000000 fffffa80`0a4ab950 00000000`00000080 fffffa80`085f5010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`052e8bc0 fffff800`03167bc6 : 00000000`02243319 fffffa80`08131060 fffffa80`066d0b10 fffffa80`08131060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`052e8c00 fffff800`02ec16a6 : fffff800`0304ee80 fffffa80`08131060 fffff800`0305ccc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`052e8c40 00000000`00000000 : fffff880`052e9000 fffff880`052e3000 fffff880`052e7310 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+ccac
fffff880`03ee3cac ?? ???

SYMBOL_NAME: atikmpag+ccac

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 55c01884

FAILURE_BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x117_image_atikmpag.sys

FAILURE_ID_HASH: {fa4b6286-8c4a-e9c2-c89f-5612619e000e}

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

Bem o seu caso é TDR e não há aparentemente nem programa atrapalhando. Por enquanto e como tem posts recentes no fórum da amd sobre isso recomendo dar uma olhadinha e se achar necessário aumentar o delay para o driver ter mais tempo pra parar nesses casos.

https://community.amd.com/thread/180166

Abraços!