Pues eso, no paran de salirme los pantallazos.
Creo que me salen diferentes pantallazos por diferentes razones, pero voy a ir al último.
Me ha salido el solucionador de problemas de windows y esto es lo que me ha comentado.
Firma con problemas:
Nombre del evento de problema: BlueScreen
Versión del sistema operativo: 6.1.7601.2.1.0.256.1
Id. de configuración regional: 3082
Información adicional del problema:
BCCode: d1
BCP1: 00000000
BCP2: 00000002
BCP3: 00000000
BCP4: 890ACF82
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Archivos que ayudan a describir el problema:
C:\Windows\Minidump\072715-24398-01.dmp
C:\Users\Afisaw7\AppData\Local\Temp\WER-102711-0.sysdata.xml
Lea nuestra declaración de privacidad en línea:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0c0a
Si la declaración de privacidad en línea no está disponible, lea la declaración de privacidad sin conexión:
C:\Windows\system32\es-ES\erofflps.txt
Ayudenme, necesito solucionar los pantallazos para poder formatear tranquilo sabiendo que ya no estan.
Gracias ;)
Dura poco, por lo que mucho no puedo mirar, y encima no sale bien en la pantalla centrado, la imagen ''se sale de la pantalla''.
Intentare pillarlo igualmente, pero no creo que consiga ver mucho.
Envianos el DMP para que lo podamos analizar. Descativa el reinicio automatico así podrás leer detalladamente la pantalla azul
No sé que es el DMP.
Y como se desactiva el reinicio automático ?
Perdón por la ignorancia jaja
CitarY como se desactiva el reinicio automático ?
Pulsando F8
(http://ciberblog.files.wordpress.com/2010/08/f8.png)
Otra opción en windows 7 sería :
Windows 7, cuando este sistema operativo produce una falla lo primero que nos aparece en la pantalla es el mensaje con pantalla azul, en el cual podemos ver y obtener información acerca del problema y error que se produjo, pero en el actual Windows 7 esto no es posible ya que el sistema operativo se reinicia automáticamente y no deja tiempo siquiera a leer el mensaje, por lo cual vamos a recomendar y enseñar a desactivar el reinicio automático en caso de errores.
Para realizar esta desactivación realizamos los siguientes pasos:
Paso 1:
Hacemos clic en Inicio, luego vamos a Panel de Control, clic en Sistema y seguridad y por último clic en Sistema.
Paso 2:
Ya dentro de sistema, en la parte izquierda de la ventana, damos clic en donde dice Configuración avanzada del sistema.
Paso 3:
Ubicamos la pestaña Opciones avanzadas y dentro de Inicio y recuperación hacemos clic el botón de Configuración.
Paso 4:
En la nueva ventana que se nos abre de Inicio y recuperación, dentro del sector error del sistema desmarcamos Reiniciar automáticamente.
Paso 5:
Aceptamos, volvemos a aceptar nuevamente en la anterior ventana y listo, proceso concluido.
Ahora cada vez que tengamos un pantallazo azul de error no se reiniciara inmediatamente y podremos apuntar el código de error, como ver las referencias a esta falla que tuvo el sistema.
Gracias, ya he desactivado el reinicio automatico, ahora toca esperar a que le vuelva a pasar jaja.
Ya solo me queda saber que es DMP jaja
Busca en tu carpeta C:\Windows\Minidump, ahi estarán los ficheros DMP, un fichero por cada bluescreen que hayas tenido. Pasanos ese fichero por mediafire o mega y te lo analizaremos.
Un saludo
Llevaba ya un tiempo pasando esto jajaja.
Muchas gracias ;)
Cita de: Sevilla6 en 28 Julio 2015, 23:59 PM
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:
(http://i.imgur.com/Fc3A4kC.png)
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!
SAT...
Que te lo limpien...
Que te lo ensamblen...
Que le hagan un zerofill al HDD...
Que te metan el sistema, drivers, actualizaciones y seguridad...
Que no te cobren mucho (no sé man, véndete un poco por tu PC xDDD)...
Que te den la hoja de garantía de la reparación...
Buenas no he estado y por eso este tiempo jaja.
Me descargue un programa que me recomendaron ( no se quien fue ;D) slim driver, y bueno actualicé todos los drivers que me indicaban, que no eran pocos.
También tenía otro programa que me recomendaron tambien, drivertool kit, y me dice que tengo 18 driver por actualizar, pero si paso slim drivers me dice que ya todo está bien.
No he estado así que de momento no me ha dado tiempo de ningún pantallazo, pero a qué programa hago caso? jaja
Me acaba de volver un pantallazo.
0x0000007F
Alguien que me diga de que es ?
Seguramente acuda a esa pagina bastante, pero la verdad esque sigo sin saber muy bien que hacer, y nose si formatear el ordenador o si antes de formatear debería mirarle eso.
En casos como el tuyo YO desguazaría el PC, lo volvería a montar con los pertinentes cuidados, haría una instalación limpia, pondría drivers actualizados y sacrificaría un poquillo de peregil a no se qué santo.