Imagem congelando e travando.

[Jonathan M. A.]

Boa tarde amigos, logo de antemão aviso que sou leigo em qualquer assunto relacionado a informatica, porém aprendo rápido e tenho força de vontade. Dito isso vamos ao assunto referente a criação do tópico.

Meu computador era antigo demais e resolvi inovar, comprei todas as peças necessárias pela internet (não acho necessário fazer propaganda do site), tudo chegou em estado normal, sem nenhum amassado, nem nada. Ok, desmontei meu computador antigo e montei o computador novo, me desmagnetizei como alguns fóruns recomendam e montei o computador.

Configurações:

Processador intel core i5 3570 3.40;

16GB de memória single channel 8gb ddr3 individual corsair;

HD 500GB seagate barracuda 7200 rpm;

Placa mãe intel BOXDZ77SL50K, suporta até i7 com espaço para 32GB de ram;

Placa de vídeo EVGA Nvidia GeForce 650 Ti, memória de 1GB GDDR5 128 Bit, PCI-Express 3.0 16x;

Fonte cooler master GX 650w;

O problema:

Montado o computador, instalado o sistema operacional (windows 8 crackeado) e todos drivers instalados, o computador congela a imagem nos jogos, seja League of Legends, seja Medieval Warfare, seja Call of Duty Black Ops 2.

O que eu já tentei:

Quando fui pesquisar nos fóruns a respeito vi uma série de programas pra me ajudar diagnosticar o problema, então baixei o programa: MEMTEST (para testar a memória ram), o programa WHOCRASHED pra ver qual outra parte consta o problema.

Diagnostico:

O programa WHOCRASHED alega o seguinte erro:

10 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 314.22 , NVIDIA Corporation)

Como eu já imaginava por ser problema apenas nos vídeos, o problema é na placa de vídeo. Constatado esse erro, eu tentei fazer as seguintes operações: Desinstalar todas os drivers instalados da placa de vídeo, baixar no site da NVIDIA outros drivers recomendados, usei o programa DRIVER SWEEPER para limpar qualquer vestígio dos drivers antigos pra não existir conflito. Baixei também o programa SLIMDRIVERS pra atualizar qualquer outro drive que estivesse ausente. Feito tudo isso, o problema continua.

Perguntas:

Pode esse problema ocorrer por ser windows 8 crackeado?

Pode o problema ser em função de ter ligado a placa na saída PCI Express e não na SLI?

Pode o problema ser pelo fato da primeira vez que instalei o driver de vídeo, ter utilizado o do CD que veio junto com a placa e após ler nas letras miúdas que ele é pra win 7, vista e xp apenas e terem ficados vestígios impossíveis de tirar, causando o conflito?

Ou por fim o problema está realmente na placa de vídeo?

Agradecimentos:

Galera, é meu primeiro tópico no fórum, realmente preciso de ajuda de vocês. Sou grato desde já.

att. Jonathan M. A.

OBS: Se tiver postado no lugar errado, por favor algum moderador fazer a correção e me alertar.

Lista de erros:

On Sat 18/05/2013 05:02:49 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051813-18218-01.dmp

This was probably caused by the following module: ndu.sys (Ndu+0x510E)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88008BE110E, 0xFFFFF880086C24D8, 0xFFFFF880086C1D10)

Error: KMODE_EXCEPTION_NOT_HANDLED

file path: C:\Windows\system32\drivers\ndu.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Windows Network Data Usage Monitoring Driver

Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Sat 18/05/2013 05:02:49 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: aswtdi.sys (aswTdi+0x11A8)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88008BE110E, 0xFFFFF880086C24D8, 0xFFFFF880086C1D10)

Error: KMODE_EXCEPTION_NOT_HANDLED

file path: C:\Windows\system32\drivers\aswtdi.sys

product: avast! Antivirus

company: AVAST Software

description: avast! TDI Filter Driver

Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswtdi.sys (avast! TDI Filter Driver, AVAST Software).

Google query: AVAST Software KMODE_EXCEPTION_NOT_HANDLED

On Sat 18/05/2013 01:04:17 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051813-22546-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80185CC0DB5, 0x0, 0xFFFFFFFFFFFFFFFF)

Error: KMODE_EXCEPTION_NOT_HANDLED

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Fri 17/05/2013 21:15:08 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051713-19375-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)

Bugcheck code: 0x1 (0x77172AD2, 0x0, 0x80000000, 0xFFFFF880099ACB80)

Error: APC_INDEX_MISMATCH

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that there has been a mismatch in the APC state index.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 15/05/2013 03:32:34 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051513-13703-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801766CC0F9, 0xFFFFF88007E29E30, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 12/05/2013 21:30:10 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051213-9343-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8024B4FB9F5, 0xFFFFF88009283F60, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 12/05/2013 18:11:23 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051213-10421-01.dmp

This was probably caused by the following module: Unknown (0xFFFFF88003826309)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88003826309, 0xFFFFF8800098A4E8, 0xFFFFF88000989D20)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error.

Google query: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

On Sun 12/05/2013 06:26:24 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051213-12250-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)

Bugcheck code: 0x139 (0x3, 0xFFFFF88003FF1590, 0xFFFFF88003FF14E8, 0x0)

Error: KERNEL_SECURITY_CHECK_FAILURE

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: The kernel has detected the corruption of a critical data structure.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 12/05/2013 06:02:46 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051213-14171-01.dmp

This was probably caused by the following module: nvlddmkm.sys (0xFFFFF880045F5398)

Bugcheck code: 0xD1 (0x12C0000012C, 0x6, 0x0, 0xFFFFF880045F5398)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\nvlddmkm.sys

product: NVIDIA Windows Kernel Mode Driver, Version 314.22

company: NVIDIA Corporation

description: NVIDIA Windows Kernel Mode Driver, Version 314.22

Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 314.22 , NVIDIA Corporation).

Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Sun 12/05/2013 01:21:07 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051113-13703-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)

Bugcheck code: 0x19 (0xE, 0xFFFFFA800D1BCCF0, 0xE9F86F3838582136, 0xE8F86F3838582136)

Error: BAD_POOL_HEADER

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a pool header is corrupt.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[Jonathan M. A.]

Up. Preciso de ajuda.