Tela azul o que fazer? whocrashed

[LuizHLS]

Estou com problema de tela azul de 10 em 10 minutos, mas quando não exijo muito do pc ela não acontece ou acontece com menos frequência por exemplo ao escutar rádios ou somente textos ou fotos online. Já utilizei 2 programas para atualizar drivers o SlimDrivers e o Driver Booster 3. O erro ocorre mesmo no modo de segurança. Aparece vários erros menores também: fechando o navegador, dizendo q a área de trabalho parou de funcionar ou tal aplicativo parou de puncionar.

Aqui esta o resultado do WhoCrashed:

 

System Information (local)

Computer name: USUARIO-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: G31T-M7, MEOO
CPU: GenuineIntel Pentium® Dual-Core CPU E5200 @ 2.50GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3479429120 bytes total


 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 17/11/2015 01:48:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111615-19016-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x4ABD)
Bugcheck code: 0xD1 (0xFFFFFFFF83C9E18F, 0x2, 0x0, 0xFFFFFFFF83C9E18F)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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 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 Tue 17/11/2015 01:48:39 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KeRaiseIrqlToSynchLevel+0x8F)
Bugcheck code: 0xD1 (0xFFFFFFFF83C9E18F, 0x2, 0x0, 0xFFFFFFFF83C9E18F)
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.
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: hal.sys .
Google query: hal.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 17/11/2015 01:45:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111615-17955-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x9E410)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF830F2410, 0xFFFFFFFFB7FD5B7C, 0xFFFFFFFFB7FD5760)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 17/11/2015 01:21:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111615-21044-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5F88D)
Bugcheck code: 0x50 (0xFFFFFFFFFD02B030, 0x1, 0x80149, 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 Tue 17/11/2015 01:16:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111615-20638-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD31E0)
Bugcheck code: 0x4E (0x99, 0xB4256, 0x1, 0x1)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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.



On Mon 16/11/2015 22:00:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111615-19671-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x2C6E)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF8C7A8C6E, 0xFFFFFFFF978B7B4C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Gerenciador de Filtro do Filesystem Microsoft
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 Mon 16/11/2015 21:17:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111615-23197-01.dmp
This was probably caused by the following module: igdkmd32.sys (igdkmd32+0xF8A8)
Bugcheck code: 0xA (0xFFFFFFFF80006A00, 0xFF, 0x1, 0xFFFFFFFF830A7C5B)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\igdkmd32.sys
product: Intel Graphics Accelerator Drivers for Windows Vista®
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
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: igdkmd32.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation IRQL_NOT_LESS_OR_EQUAL



On Mon 16/11/2015 21:15:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111615-19624-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD31E0)
Bugcheck code: 0x4E (0x2, 0x15096, 0xCF69F, 0x2C00)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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.



On Mon 16/11/2015 20:38:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111615-18907-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x359C6)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82B31EB2, 0xFFFFFFFFB7C319B8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 Mon 16/11/2015 20:12:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111615-19250-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x71CA)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF80E1EB00, 0xFFFFFFFF80E1E6E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Tempo de Execução da Estrutura de Driver em Modo Kernel
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.



 

Conclusion

51 crash dumps have been found and analyzed. Only 10 are included in this report. 4 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:

bhbase.sys (Baidu Antivirus Hook Base, Baidu, Inc.)
igdkmd32.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)
hal.sys
l26.sys  

[César Platz]

Baidu??? extirpa isso do seu pc!!!

Quando esse problema começou a acontecer?

Tente fazer backup de suas informaçoes e formatar o pc via cd do windows ou pendrive bootável. Pode também é fazer um pendrive bootável de algum linux e roda-lo em modo live para ver se continua a apresentar algum tipo de problema.

OBS: faça o pendrive bootável em outro pc, pois pelo que ví nas informações, está dizendo que o problema está sendo causado por um software, assim pode ser que seja algum vírus. Quanto ao backup e formatação, sugiro fazer via linux live caso seja possível.