Llevaba ya un tiempo pasando esto jajaja.
Muchas gracias
Bueno, tengo malas noticias. Según los reportes que nos has mandado, tu sistema operativo está bastante dañado. Tienes errores de todo tipo, desde fallo de L/E en memoria hasta drivers mal cargados/firmados. Te adjunto el reporte de 10 dmp analizados con WhoCrashed (está en inglés, usa un traductor si no lo entiendes):
On Tue 28/07/2015 15:44:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072815-20872-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0x17B2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF88C267B2, 0xFFFFFFFF985A98A8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
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.
Google query: Microsoft Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Tue 28/07/2015 14:52:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072815-21840-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDF3C8)
Bugcheck code: 0x4E (0x99, 0x207EE, 0x2, 0x5CCAC)
Error: PFN_LIST_CORRUPT
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 27/07/2015 17:45:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072715-24398-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x80F82)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFFFFF890ACF82)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador TCP/IP
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 Mon 27/07/2015 14:33:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072715-30076-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x25B420)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF830A5420, 0xFFFFFFFFB9158C44, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 Fri 10/07/2015 15:23:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071015-20280-01.dmp
This was probably caused by the following module: avipbb.sys (avipbb+0xAE08)
Bugcheck code: 0xFC (0xFFFFFFFF8CEC6CA8, 0x287C9963, 0xFFFFFFFF8CEC6B28, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug check description: This indicates that an attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
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: avipbb.sys .
Google query: avipbb.sys ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
On Fri 10/07/2015 15:16:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071015-19656-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x415CB)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFFFFF82EBD406)
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 Thu 09/07/2015 2:09:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070915-21746-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x415CB)
Bugcheck code: 0xA (0x741714C8, 0x2, 0x1, 0xFFFFFFFF82EC4EE6)
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 08/07/2015 15:27:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070815-22776-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x415CB)
Bugcheck code: 0xA (0x2D8BE0, 0x2, 0x0, 0xFFFFFFFF82EB3E73)
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 08/07/2015 15:17:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070815-27253-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x19FEC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82EE3C00, 0xFFFFFFFF807A5914, 0xFFFFFFFF807A54F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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.
On Wed 08/07/2015 14:31:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070815-22245-01.dmp
This was probably caused by the following module: sptd.sys (sptd+0x1863A)
Bugcheck code: 0xBE (0xFFFFFFFF82E78075, 0x2E78121, 0xFFFFFFFF8078AE84, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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: sptd.sys .
Google query: sptd.sys ATTEMPTED_WRITE_TO_READONLY_MEMORY
Conclusión: 20 crash dumps have been found and analyzed. Only 10 are included in this report. 3 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:
ataport.sys (ATAPI Driver Extension, Microsoft Corporation)
sptd.sys
avipbb.sys
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.
Te dejo otra foto con un resumen de los 10 dumps analizados:
Hay demasiados errores, te recomiendo que te plantees un format de tu Windows. Si quieres antes prueba de actualizar TODOS los drivers de tu equipo, asi como instalar TODOS los parches de Windows Update (incluso los opcionales).
Saludos!
Autor
En línea
