Acho que fui premiado...chegou na segunda, usei de noite e terça a mesma coisa mas sem praticamente alterar ele, seja instalação de programa ou colocar arquivos. Na terça começou dar tela azul diversos tipos de erros, cada vez se reiniciava e acontecia o mesmo em loop.
Tentei recuperar o sistema de fábrica mas deu mesmo erro durante o processo. Hoje instalei um Windows 8.1 que eu tinha para testar, o pro, deu a mesma coisa várias vezes até que agora se estabilizou até o momento. Antes não conseguia nem mexer no note...
Alguém já passou pelo mesmo seja com esse ou outro note ? Penso que memória ou HD defeituoso, não passei ainda o mentest86. Em anexo os últimos erros do Windows pego pelo programa WhoCrashed:
http://pt-br.tinypic.com/r/2up2q9f/8
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 26/08/2015 20:38:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082615-12421-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0x50 (0xFFFFE0001193B240, 0x1, 0xFFFFF801DFC507EE, 0x2)
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 Wed 26/08/2015 20:38:21 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module:
ntfs.sys (Ntfs+0xA624F)
Bugcheck code: 0x50 (0xFFFFE0001193B240, 0x1, 0xFFFFF801DFC507EE, 0x2)
Error:
PAGE_FAULT_IN_NONPAGED_AREA
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 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 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 Wed 26/08/2015 20:35:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082615-11671-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80287439884)
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 Wed 26/08/2015 20:33:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082615-18171-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 Wed 26/08/2015 20:21:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082615-15703-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0xA (0xFFFFFFFF8445114B, 0x2, 0x1, 0xFFFFF8015FEC4686)
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 Wed 26/08/2015 20:20:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082615-22125-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 Wed 26/08/2015 20:04:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082615-26484-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80129BEB996, 0xFFFFE00002661040, 0x1)
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 26/08/2015 20:02:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082615-28500-01.dmp
This was probably caused by the following module:
hal.dll (0xFFFFF8028368B000)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80283709E10, 0xFFFFF802839D4A80, 0xFFFFF8028368B000)
Error:
KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\hal.dll
product:
Microsoft® Windows® Operating System
company:
Microsoft Corporation
description: Hardware Abstraction Layer DLL
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.