Colocar Resposta 
 
Avaliação do Tópico:
  • 0 votos - 0 Média
  • 1
  • 2
  • 3
  • 4
  • 5
BSOD
08-06-2014, 14:01
Mensagem: #1
BSOD
Boa tarde,

Nos últimos dias tenho tido constantemente um BSOD e depois de ler um pouco na net ao desinstalar os drivers da placa gráfica consigo usar o PC sem ele dar erro. Mas sempre que inicio o PC depois de desinstalar o driver ele automaticamente instala um e ao reiniciar o PC volto a ter o erro e só consigo usar de novo o PC se entrar em modo de segurança e desinstalar de novo o driver. Já testei com o driver que instala automaticamente e com um sacado do site da AMD. Aqui fica o log do debug:

Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\060814-30638-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0325d000 PsLoadedModuleList = 0xfffff800`034a0890
Debug session time: Sun Jun 8 12:32:55.524 2014 (GMT+1)
System Uptime: 0 days 0:00:54.617
Loading Kernel 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, {fffffa8009ba53a0, fffff88000c06c58, 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+6c58 )

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

6: 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 real bugcheck).
Arguments:
Arg1: fffffa8009ba53a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88000c06c58, 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+6c58
fffff880`00c06c58 ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

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


CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x117

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`063ce400 fffff880`04c5b737 : fffffa80`09ba53a0 102906c9`a00038bf 00000000`00000000 fffffa80`089bbd01 : watchdog!WdDbgReportRecreate+0xa3
fffff880`063ce920 fffff880`04c5c1b5 : fffff8a0`0335cffc fffff8a0`0302d9a0 fffff8a0`0320496a 00000000`00158692 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`063ce970 fffff880`04c5ce22 : fffffa80`09ba53a0 fffffa80`09ba53a0 fffffa80`05561d50 fffffa80`089bb410 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d
fffff880`063cea10 fffff880`03048f13 : fffffa80`09ba53a0 00000000`00000000 fffffa80`05561d50 fffffa80`089bb410 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`063cea40 fffff880`03072cf1 : 00000000`ffffffff 00000000`00000bf3 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`063ceb20 fffff880`03071437 : 00000000`00000102 00000000`00000000 00000000`00000bf3 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`063ceb50 fffff880`030442d2 : ffffffff`ffb3b4c0 fffffa80`089bb410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`063cebf0 fffff880`03070ff6 : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0956ac58 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`063ced00 fffff800`0356e73a : 00000000`019310ae fffffa80`095b2a00 fffffa80`054ef5f0 fffffa80`095b2a00 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`063ced40 fffff800`032c38e6 : fffff880`009e9180 fffffa80`095b2a00 fffff880`009f40c0 fffff880`03972701 : nt!PspSystemThreadStartup+0x5a
fffff880`063ced80 00000000`00000000 : fffff880`063cf000 fffff880`063c9000 fffff880`063cdee0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+6c58
fffff880`00c06c58 ?? ???

SYMBOL_NAME: atikmpag+6c58

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c2010ba

FAILURE_BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys

Followup: MachineOwner

Alguém pode ajudar?
Procurar todas as mensagens deste utilizador
Citar esta mensagem numa resposta
Colocar Resposta 


Mensagem neste Tópico
BSOD - Im_Dangerous - 08-06-2014 14:01
RE: BSOD - Armandoamp - 02-08-2014, 12:34

Saltar Fórum:


Utilizadores a ver este tópico: 1 Visitante(s)