Me ha salido de nuevo un pantallazo azul

Estado
Cerrado para nuevas respuestas.
Sistema Operativo
Windows 7

win_xp

Nuevo Miembro
Hacia un tiempo que no salian pantallazos azules, pero en estos últimos días han salido 3 o 4 pantallazos azules
aquí reporte de whocrashed:
Código:
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.
On Sun 09/11/2014 13:53:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110914-24180-01.dmp
This was probably caused by the following module: athrx.sys (athrx+0x22780)
Bugcheck code: 0:)1 (0xFFFFF8004CCA0F50, 0x2, 0x1, 0xFFFFF8800185C8AB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\athrx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
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: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Sun 09/11/2014 13:53:39 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5C8AB)
Bugcheck code: 0:)1 (0xFFFFF8004CCA0F50, 0x2, 0x1, 0xFFFFF8800185C8AB)
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.

  Conclusion
2 crash dumps have been found and analyzed. A third party driver has 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:
athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

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

que es? se puede solucionar?
 

jbex

El que peca y reza empata
Administrador
Descarga el driver para tu controlador Atheros Extensible Wireless LAN device driver https://www.atheros.cz/ según señala es tu problema.
Un saludo
 

win_xp

Nuevo Miembro
Me puedes buscar el link de descarga para mi marca y modelo de equipo, es: Acer ASPIRE 5733Z
 

jbex

El que peca y reza empata
Administrador
Descarga este programa Auto-detect my Serial Number http://support.acer.com/serialharvest/SerialNumber/SystemInformationSetup.msi lo ejecutas y el te mostrara cual es tu Serial Number, con el podrás usar el buscador Search by Serial Number para descargarte los drivers adecuados , ya que como veras no hay un solo modelo http://www.acer.com.au/ac/en/AU/content/drivers

Un saludo
 

win_xp

Nuevo Miembro
Me ha salido otro pantallazo azul, reporte whocrashed:
Código:
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.
On Wed 12/11/2014 13:26:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111214-23852-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFFA830560C5F0, 0x2, 0x1, 0xFFFFF80002CF9BEE)
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 12/11/2014 13:26:28 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 (0xFFFFFA830560C5F0, 0x2, 0x1, 0xFFFFF80002CF9BEE)
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.

  Conclusion
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

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

win_xp

Nuevo Miembro
otro pantallazo azul:
Código:
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.
On Thu 13/11/2014 8:03:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111314-43617-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x689A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001AC889A, 0xFFFFF880039FA918, 0xFFFFF880039FA170)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
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 Thu 13/11/2014 8:03:47 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x689A)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF88001AC889A, 0xFFFFF880039FA918, 0xFFFFF880039FA170)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 12/11/2014 13:26:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111214-23852-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFFA830560C5F0, 0x2, 0x1, 0xFFFFF80002CF9BEE)
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.

  Conclusion
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

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

win_xp

Nuevo Miembro
Pasa algo, cuando enciendo el el ordenador, entre que pasa la BIOS sale lo de presionar F2 y iniciando Windows 7 en ese transcurso me ha salido varias veces pantallazo azul y luego se reinicia y me sale un fondo negro y dice algo así: puede que archivos estén dañado y dice mas cosas que no recuerdo..., vosotros que entendéis, lo debéis saber lo que sale?, y reparar inicio o iniciar Windows normalmente

PD: si queréis hago una foto con el móvil (cuando me vuelva a salir) de lo que me sale el portátil y lo nseño aquí
 

lorshaft92

El Jedi Exiliado
Super Moderador
Hola WinXp, restaura la computadora a como vino de fabrica, salvando antes tus datos personales, si tras ello siguen apareciendo pantallazos azules estando el sistema fresco, llévala a un técnico para que la revise, ya se te a recomendado en varias oportunidades que lo hicieras, los pantallazos que posee tu computadora son recurrentes y no todos son el mismo error, por ende debe haber un problema mas allá del propio sistema operativo, programas y drivers.

Si quieres pon la imagen.

Saludos ;)
 

win_xp

Nuevo Miembro
En cuanto me salga, haré una foto con el móvil y subiré la imagen

una cosa, que puede pasar si me van saliendo pantallazos azules y reiniciando y me suele salir lo de Windows no se cerro correctamente la ultima vez

iniciar Windows normalmente, etc

se puede dañar algo? es súper importante que lleve a un técnico que me trate de arreglar el ordenador y no me salgan mas pantallazos azules?
 

win_xp

Nuevo Miembro
Pero una cosa lorshaft92, hay veces que no me salen pantallazos azules durante varios días que enciendo el ordenador 2 semanas o así o a veces todos los días salen pantallazos azules, mi pregunta es si llevo el portátil a un técnico y lo enciende unas cuantas veces el ordenador y no le sale pantallazos azules, dirá que mi ordenador no tiene problemas y me lo devolverá... porque puede estar 2 semanas o 1 mes en no salirme pantallazos azules... me entiendes?
 

Kbite

Aprender y compartir
Administrador
Hola win_xp.

Creo que hace meses que andas con el problema de los pantallazos azules, y te dejo las dos opciones que tienes.

La primera que debes intentar es hacer una reinstalación a su estado de fábrica de ese portátil con la herramienta "eRecovery Management" de la que ya hemos hablado largo y tendido. Si no se repite el problema ya sabrás que la causa era el sistema operativo

La segunda, si la primera no es efectiva para evitar los pantallazos, ya deberís pensar en que la causa sea de hardware, y esto solo lo puede verificar un servicio técnico, y estando el sistema operativo recién instalado no deben de presentarse problemas para los técnicos que deban verificarlo, tan solo es darles la misma información que nos das a nosotros, ellos saben lo que deben hacer.

Date cuenta de que aquí no podemos estar pendientes continuamente y por tiempo indefinido de tus pantallazos cuando por tu parte no haces nada para evitarlos, y esto desanima a los que queremos ayudarte.

Saludos, Kbite
 

win_xp

Nuevo Miembro
Y cuanto cuesta € llevarlo a un tecnico? tu Kbite que eres de barcelona si no me equivoco? o eso dice tu perfil, cuando crees que me puedo costar llevarlo a un tecnico?
 

Kbite

Aprender y compartir
Administrador
Hola win_xp.

Sí, soy de Barcelona, pero no por esto te puedo decir lo que te puede costar una reparación, tan solo el técnico, después de hacer un diagnóstico del problema, te puede facilitar un presupuesto que variará según sea la reparación a realizar, no es lo mismo cambiar una tarjeta Ram, que es algo muy sencillo, que tener que abrir el portatil y cambiar algún componente de hardware como tarjeta gráfica, de red, ventiladores, etc. Lo indicado es pedir un presupuesto antes de que de realice la reparación y conocer el gasto que debes realizar.

Saludos, Kbite
 

win_xp

Nuevo Miembro
Vale. Y eso que ya he comentado en un mensaje anterior, que lleve el portátil a un técnico me lo mire y no sale pantallazos azules en unos cuantos días, dirá no hay problema esta todo bien... pero luego vuelve a salir pantallazos azules
 

Kbite

Aprender y compartir
Administrador
Lo normal es que las reparaciones tengan un periodo de garantía, y en caso de reproducirse el problema hacerla valer, esto es algo que debes concretar antes de la reparación.

Saludos, Kbite
 
Estado
Cerrado para nuevas respuestas.
Arriba Pie