Notebook desligando sozinho

[*Barao* 0]

Pessoal sou membro novo, e vi que vocês resolveram vários problemas a respeito de pc desligando sozinho.

 

Tem um notebook que do nada resolveu desligar sozinho.

 

Vi alguns posts e baixei um software sugerido por vocês que faz analisis do ocorrido veja o relatório abaixo:

System Information (local) computer name: CORTONEZI-PC

windows version: Windows 7 Service Pack 1, 6.1, build: 7601

windows dir: C:\Windows

CPU: GenuineIntel Intel® Core™ i7 CPU Q 740 @ 1.73GHz Intel586, level: 6

8 logical processors, active mask: 255

RAM: 4284334080 total

VM: 2147352576, free: 1886855168

 

 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 17/12/2012 13:26:58 GMT your computer crashed

crash dump file: C:\Windows\Minidump\121712-30576-01.dmp

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

Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80003697F74)

Error: IRQL_NOT_LESS_OR_EQUAL

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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

On Mon 17/12/2012 13:26:58 GMT your computer crashed

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

This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)

Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80003697F74)

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.

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 31/10/2012 13:46:32 GMT your computer crashed

crash dump file: C:\Windows\Minidump\103112-31059-01.dmp

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

Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80003694F74)

Error: IRQL_NOT_LESS_OR_EQUAL

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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

On Tue 30/10/2012 20:00:52 GMT your computer crashed

crash dump file: C:\Windows\Minidump\103012-31839-01.dmp

This was probably caused by the following module: fltmgr.sys (fltmgr+0x1777)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001201777, 0xFFFFF8800B3498F0, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

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 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 Sat 28/07/2012 16:37:03 GMT your computer crashed

crash dump file: C:\Windows\Minidump\072812-22791-01.dmp

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

Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFF8A01D5D6010)

Error: BAD_POOL_CALLER

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 current thread is making a bad pool request.

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 15/04/2012 01:53:08 GMT your computer crashed

crash dump file: C:\Windows\Minidump\041412-23883-01.dmp

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

Bugcheck code: 0xA (0xFFFFF683FF6FD218, 0x0, 0x0, 0xFFFFF8000368064B)

Error: IRQL_NOT_LESS_OR_EQUAL

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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

On Sun 20/11/2011 20:11:41 GMT your computer crashed

crash dump file: C:\Windows\Minidump\112011-21434-01.dmp

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

Bugcheck code: 0x4E (0x99, 0x85D95, 0x0, 0x95595)

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 Thu 20/10/2011 20:54:54 GMT your computer crashed

crash dump file: C:\Windows\Minidump\102011-22276-01.dmp

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

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000380BA9B, 0xFFFFF8800AAAC010, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

On Wed 24/08/2011 21:15:29 GMT your computer crashed

crash dump file: C:\Windows\Minidump\082411-24679-01.dmp

This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)

Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800AC6F3B8, 0xFFFFF8800AC6EC10, 0xFFFFF80003808A9B)

Error: NTFS_FILE_SYSTEM

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 a problem occurred in the NTFS file system.

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 02/05/2011 00:46:15 GMT your computer crashed

crash dump file: C:\Windows\Minidump\050111-21138-01.dmp

This was probably caused by the following module: dfsc.sys (dfsc+0xBFFE)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880041E4FFE, 0xFFFFF8800728E8D0, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

file path: C:\Windows\system32\drivers\dfsc.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: DFS Namespace Client Driver

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 Tue 01/03/2011 00:09:23 GMT your computer crashed

crash dump file: C:\Windows\Minidump\022811-37705-01.dmp

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

Bugcheck code: 0xC2 (0x7, 0x1097, 0x0, 0xFFFFF8A0004BD010)

Error: BAD_POOL_CALLER

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 current thread is making a bad pool request.

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.

 

 

Conclusion

11 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.

 

 

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 actually 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.

 

 

 

Se puderem dar uma ajudinha.

 

Abraços,

[Edvan 30]

O relatório mostra que:

 

arquivo de despejo: C: \ Windows \ memory.dmp, isso provavelmente foi causado pelo módulo seguinte: ntkrnlmp.exe (nt! KeBugCheckEx 0 x0) Bugcheck código: 0xA (0x0, 0x2, 0x0, 0xFFFFF80003697F74) Erro: IRQL_NOT_LESS_OR_EQUAL

 

Descrição verificação de erros: Isso indica que o Microsoft Windows ou um driver de modo kernel acessada memória paginada em DISPATCH_LEVEL ou acima.

 

Este parece ser um bug de driver típico de software e não é susceptível de ser causada por um problema de hardware.

 

O acidente ocorreu no kernel do Windows. Possivelmente este problema é causado por um outro condutor que não podem ser identificadas neste momento.

 

 

P>S: A dica que dou é você rever quais softwares ou drives de terceiros foram instalados recentemente no seu notebook, tentar desinstalar, em ultimo caso fazer um recover para as configurações de fabrica.

[*Barao* 0]

O relatório mostra que:

 

arquivo de despejo: C: \ Windows \ memory.dmp, isso provavelmente foi causado pelo módulo seguinte: ntkrnlmp.exe (nt! KeBugCheckEx 0 x0) Bugcheck código: 0xA (0x0, 0x2, 0x0, 0xFFFFF80003697F74) Erro: IRQL_NOT_LESS_OR_EQUAL

 

Descrição verificação de erros: Isso indica que o Microsoft Windows ou um driver de modo kernel acessada memória paginada em DISPATCH_LEVEL ou acima.

 

Este parece ser um bug de driver típico de software e não é susceptível de ser causada por um problema de hardware.

 

O acidente ocorreu no kernel do Windows. Possivelmente este problema é causado por um outro condutor que não podem ser identificadas neste momento.

 

 

P>S: A dica que dou é você rever quais softwares ou drives de terceiros foram instalados recentemente no seu notebook, tentar desinstalar, em ultimo caso fazer um recover para as configurações de fabrica.

 

Ok. Vou fazer um limpeza aqui, na pior das hipóteses vou restaurar o sistema. Tenho um backup recente.

 

Grato,