Pedro Ivo Barbosa

@rodrigo.dcvieira Já. @leklek01 Todos os jogos que crashavam são da steam. Os jogos que não crashavam não eram da steam. [email protected] montei. Ja fiz, mas auto-detectar o driver é uma péssima ideia. Nossa, ficou horrivel, mas nao consigo consertar. (A formatação do texto) o que eu ja fiz: Atualizei a BIOS e corrigiu um monte de tela azul relacionada a driver. Restaram os relacionados à memory dump. Identifiquei dois pentes de RAM bichados e tirei do sistema, as telas azul de memory dump e write on readonly files pararam. Agora to com erro em dxmms2.sys (direct x) e BAD POOL HEADER (ntoskrnl.exe) e (dxgkrnl.sys)

Oi, gente. Meu nome é Pedro e recentemente adquiri um computador novo, como eu estava com um orçamento apertado e os componentes AMD estavam com uma ótima promoção, adquiri-os. Pois bem, agora, não consigo rodar jogos que deveriam ser moleza, pois fico tomando tela azul. Dead Space 1 me dá tela azul logo no diálogo inicial, CS:GO me dá tela azul depois de alguns rounds e FEAR a tela azul é instantanea quase. Mas todas as telas azuis seguem um padrão: Só acontecem em jogos da Steam. Overwatch, League of Legends, World of Warcraft, RuneScape, Diablo 3 não me dão tela azul. Segue meu setup: CPU: AMD FX-8350 Vishera 4.2GHz MB: ASUS M5A78L-M/USB3 RAM: 4x4GB 1333MHz DDR3 da Corsair GPU: Power Color Radeon R7 370 4GB GDDR5 PSU: de 600W da Corsair HDD: WD Blue 1TB 7200RPM E se isso importar: Tem um Razer Lycosa e um DeathAdder ligados no PC via-USB, com o driver da razer instalados. Também tem um fone B&W P7 conectado. O sistema operacional é um Windows 10 64bit e no background tem o Kaspersky rodando. O que eu já fiz, baseado nos erros e padrões: - Cleaninstall no Driver da placa de vídeo (WHQL mais recente). - Desativar o controle de programas exercido pelo Kaspersky - Desativar o Kaspersky - Update da BIOS Como complemento, também rodei o WhoCrashed, mas ele me aponta que quem tá crashando é o Kaspersky e o Driver da Placa de Vídeo. Obrigado a todos. Segue o que o WhoCrashed me retorna. Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Tue 22/11/2016 18:22:50 your computer crashed crash dump file: C:\Windows\Minidump\112216-25531-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x6BB173) Bugcheck code: 0x124 (0x0, 0xFFFFB88E94EE7038, 0x0, 0x0) Error: WHEA_UNCORRECTABLE_ERROR file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System 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 also be caused because of overheating (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. On Tue 22/11/2016 17:16:28 your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: Unknown (0xFFFFF800FA521834) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800FA521834, 0xFFFFD18060275D40, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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. A third party driver was identified as the probable root cause of this system error. Google query: SYSTEM_SERVICE_EXCEPTION On Tue 22/11/2016 17:14:15 your computer crashed crash dump file: C:\Windows\Minidump\112216-25203-01.dmp This was probably caused by the following module: Unknown () Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0) Error: CUSTOM_ERROR A third party driver was identified as the probable root cause of this system error. Google query: CUSTOM_ERROR On Tue 22/11/2016 16:45:38 your computer crashed crash dump file: C:\Windows\Minidump\112216-30000-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802F027B9CC, 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 Wed 16/11/2016 08:15:50 your computer crashed crash dump file: C:\Windows\Minidump\111616-19171-01.dmp This was probably caused by the following module: ndis.sys (ndis+0x4FAA) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8005D3D4FAA, 0x0, 0xFFFFFFFFFFFFFFFF) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\drivers\ndis.sys product: Sistema Operacional Microsoft® Windows® company: Microsoft Corporation description: NDIS (Especificação de Interface de Driver de Rede) 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. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 21 crash dumps have been found and analyzed. Only 5 are included in this report. 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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.) klif.sys (Core System Interceptors [fre_win8_x64], AO Kaspersky Lab) If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.