Tela azul em jogos

Toufz · 23 de maio de 2016

Bem, sempre que utilizo jogos como: The room, Payday: Heists, Portal 2, etc. meu computador dá tela azul.

Então, utilizei o WhoCrashed para verificar os possível erros.

Especificações do computador:

Spoiler

Computer name: SPACE
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., C8HM70-I/HDMI
CPU: Genuine Intel Intel(R) Celeron(R) CPU 847 @ 1.10GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 8256831488 bytes total

Report:

Spoiler

Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 22/05/2016 22:41:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052216-21031-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!WPP_RECORDER_SF_D+0x91)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF96027644E9D, 0xFFFFD00020EEAF80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver de Kernel de Win32k Base
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 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 22/05/2016 22:41:38 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!WPP_RECORDER_SF_D+0x91)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF96027644E9D, 0xFFFFD00020EEAF80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver de Kernel de Win32k Base
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 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 Fri 15/04/2016 16:05:10 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041516-21578-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0xFFFFF802F5D41E70, 0xEFFFF802F5D3FFE0, 0xFFFFF802F3FC7BCD)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 14/04/2016 21:13:55 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041416-44187-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!DxgkUnlock+0x5)
Bugcheck code: 0xBE (0xFFFFF801AB2BCF14, 0x533B121, 0xFFFFD00020E24CA0, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 02/04/2016 18:48:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040216-21875-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!DirtyPageRoutine+0x3F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF801A76CAF5F, 0xFFFFD0015C311F98, 0xFFFFD0015C3117B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver do Sistema de Arquivos NT
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.
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 27/03/2016 20:12:06 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032716-18421-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpTimerClockInterrupt+0x56)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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 27/03/2016 17:39:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032716-19859-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VIDMM_GLOBAL::IsAllocationInUse+0xF)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80138030DF7, 0xFFFFD000A46FAE30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 27/03/2016 16:42:23 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032716-18281-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xD1 (0x800, 0xFF, 0x0, 0x800)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
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 27/03/2016 16:22:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032716-18078-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VIDMM_PROCESS_HEAP::Free+0xA3)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8004F079582, 0xFFFFD001A4AC8C58, 0xFFFFD001A4AC8470)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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.
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 Fri 25/03/2016 17:02:16 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032516-21218-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!DxgkPresent+0x1292)
Bugcheck code: 0xA (0xFFFFFFFF, 0x2, 0x1, 0xFFFFF802EC8F1661)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.