Tela Azul

[Henrique11]

Segue o arquivo DUMP

https://rapidshare.com/files/1485805670/040412-21450-01.dmp

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Henrique\Documents\DUMP\040412-21450-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

Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330

Machine Name:

Kernel base = 0xfffff800`03214000 PsLoadedModuleList = 0xfffff800`03458650

Debug session time: Wed Apr 4 10:52:25.361 2012 (UTC - 3:00)

System Uptime: 0 days 0:28:25.298

Loading Kernel Symbols

...............................................................

................................................................

.................................

Loading User Symbols

Loading unloaded module list

.....

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800612f4e0, fffff8800ff30aa4, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Probably caused by : nvlddmkm.sys ( nvlddmkm+ca1aa4 )

Followup: MachineOwner

---------

7: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

VIDEO_TDR_FAILURE (116)

Attempt to reset the display driver and recover from timeout failed.

Arguments:

Arg1: fffffa800612f4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff8800ff30aa4, The pointer into responsible device driver module (e.g. owner tag).

Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.

Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:

------------------

FAULTING_IP:

nvlddmkm+ca1aa4

fffff880`0ff30aa4 4883ec28 sub rsp,28h

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:

fffff880`029d0b88 fffff880`042d1000 : 00000000`00000116 fffffa80`0612f4e0 fffff880`0ff30aa4 ffffffff`c000009a : nt!KeBugCheckEx

fffff880`029d0b90 fffff880`042a4867 : fffff880`0ff30aa4 fffffa80`08555000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec

fffff880`029d0bd0 fffff880`042d0e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`0612f4e0 fffff880`0439fdc0 : dxgkrnl!DXGADAPTER::Reset+0x2a3

fffff880`029d0c80 fffff880`0439fec1 : fffffa80`05acd010 00000000`00000080 00000000`00000000 fffffa80`0853b410 : dxgkrnl!TdrResetFromTimeout+0x23

fffff880`029d0d00 fffff800`0352af7a : 00000000`03ed3d1a fffffa80`081d9b60 fffffa80`04f05740 fffffa80`081d9b60 : dxgmms1!VidSchiWorkerThread+0x101

fffff880`029d0d40 fffff800`032819c6 : fffff800`03405e80 fffffa80`081d9b60 fffff800`03413cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a

fffff880`029d0d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:

nvlddmkm+ca1aa4

fffff880`0ff30aa4 4883ec28 sub rsp,28h

SYMBOL_NAME: nvlddmkm+ca1aa4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4f4e68c4

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner

-------------------------------------------------------------

Começou a dar tela azul em janeiro (programas como o FurMark, jogos como Starcraft 2, Fifa 12 faziam o PC travar) li que isso poderia ser ocasionado por memoria ram defeituosa; rodei o memtest86+, fazendo todos os testes 2 vezes sem apresentar nenhum problema; e poeira - um ano sem limpar o pc ... - apos a limpeza (pano e aspirador de pó) ficou um mês sem dar problema, porém agora o problema voltou. Novamente limpei o gabinete; nada abrasivo, somente pano; houve uma pequena diferença, antes da segunda limpeza era só jogar ou até mesmo executar o Windows Index Experience que travava, agora ele aguenta um pouco mais.