Tela azul constante mesmo depois de formatar

[saymynamevqv]

Meu pc vem dandos mtos problemas de tela azul, ja formatei, testei ram e nada.

 

Minha config: Asus M4A78LT-M
AMD Phenom II X4 965
AMD Radeon HD XFX 7870
Realtek RTL8168D/8111D PCI-E Gigabit Ethernet Adapter
8GB DDR3 1333MHz

 

Log de erros:

On Fri 06/10/2017 05:15:32 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x02ED1950)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
Google query: KMODE_EXCEPTION_NOT_HANDLED



On Fri 06/10/2017 05:04:54 your computer crashed
crash dump file: C:\Windows\Minidump\100617-25381-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000000.sys (Unloaded_Unknown_Module_00000000`00000000+0xA)
Bugcheck code: 0xA (0xFFFFFB80084062B8, 0x2, 0x0, 0xFFFFF80002EDA682)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
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: unknown_module_00000000`00000000.sys .
Google query: unknown_module_00000000`00000000.sys IRQL_NOT_LESS_OR_EQUAL



On Sun 01/10/2017 13:20:18 your computer crashed
crash dump file: C:\Windows\Minidump\100117-25615-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0x50 (0xFFFFFA800B834000, 0x0, 0xFFFFF80002EB0B3E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Sat 23/09/2017 10:21:58 your computer crashed
crash dump file: C:\Windows\Minidump\092317-28906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0x50 (0xFFFFFA800D670000, 0x0, 0xFFFFF80002F2622E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.
 

Parece que nao é hardware, o que devo fazer?

[Kleber Peters]

Caramba, quanta coisa. Aparentemente é um problema de driver e a primeira mensagem indica algo relacionado às USB 3.0. 

 

Qual a versão do Windows? Se for 8.1 ou 10, veja este artigo com instruções de como resolver. 

[saymynamevqv]

10 horas atrás, Kleber Peters disse:

Caramba, quanta coisa. Aparentemente é um problema de driver e a primeira mensagem indica algo relacionado às USB 3.0. 

 

Qual a versão do Windows? Se for 8.1 ou 10, veja este artigo com instruções de como resolver. 

Sim HAUAHUAUHA, as vezes to no YouTube e da BSOD, ou acabei de ligar o pc, bem zoado. Voltei pra Windows 7, no 10 tava dando erro parecido, por isso voltei. Tenho todas as atualizações do Windows instaladas, e esse erro de USB 3.0, não tem nem USB 3.0 nessa placa-mãe, será que é esse o problema?