Tela azul equanto jogo BF4

SaharanPain · 5 de novembro de 2013

então, jogo LoL (League of Legends) há um bom tempo e nunca tive problemas com ele. Só que aí comprei o Battlefield 4. Começo a jogar com o jogo limpo, sem problemas de FPS ou similares, com ótima qualidade. O problema é que depois de uns 5 minutos jogando, o jogo trava e aparece a clássica tela azul.

o erro que aparece é DPC_WATCHDOG_VIOLATION e pelo o que pesquisei, já vi gente falar que é até uma tal de tela azul da morte do windows.

baixei o slimdrivers, mandei rodar, baixei todos os drivers. entrei no site do meu HD, baixei um programa da Seagate e mandei dar vistoria total de funcionamento do HD, mandei corrigir tudo e o erro continua aparecendo.

não acho que seja problema de superaquecimento porque 1º: acontece em muito pouco tempo; 2º: deixo o pc ligado dias e jogo LoL (já aconteceu de jogar mais de 8 horas em um dia) sempre nele sem dar um erro

Minha fonte é de 850W, placa de vídeo Gigagbyte HD7970 de 3gb, 384bits com 3 ventiladores, processador i7 quarta geração 3,4gh, 16gb de RAM e 2 tb de HD

btw, hoje (alguns dias depois do erro no bf4) deu um erro que era Whea uncorrectable error também... por favor, ajudem

relatório do whocrashed

Crash dumps are enabled on your computer.

On Sun 10/11/2013 00:11:34 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\110913-21250-01.dmp

This was probably caused by the following module: hal.dll (hal+0x35CDF)

Bugcheck code: 0x124 (0x0, 0xFFFFE00004FD7028, 0xBE000000, 0x100110A)

Error: WHEA_UNCORRECTABLE_ERROR

file path: C:\WINDOWS\system32\hal.dll

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Hardware Abstraction Layer DLL

Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.

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 Sun 10/11/2013 00:11:34 GMT your computer crashed

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

This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0xCF)

Bugcheck code: 0x124 (0x0, 0xFFFFE00004FD7028, 0xBE000000, 0x100110A)

Error: WHEA_UNCORRECTABLE_ERROR

file path: C:\WINDOWS\system32\hal.dll

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Hardware Abstraction Layer DLL

Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.

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 Wed 06/11/2013 16:23:06 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\110613-36453-01.dmp

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

Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)

Error: DPC_WATCHDOG_VIOLATION

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

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.

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

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

acreditam ser um problema no windows, driver ou de mal funcionamento das peças do computador? mandei rodar o SeaTools para Windows mais uma vez para ver se era problema no HD e não recebi nenhuma resposta do programa, então não acho que seja problema nele