Pantallazo azul (nwifi.sys) Tema Solucionado

Foro referente al sistema operativo Windows 7
astra3
Usuario linuxero
Usuario linuxero
Mensajes: 3
Registrado: 05 Nov 2013, 15:22
Agradecido : 2 veces
Contactar:

Pantallazo azul (nwifi.sys)

Mensajepor astra3 » 05 Nov 2013, 15:29

Buenas a todos desde hace un par de dias siempre que me dejo el ordenador encendido por algún motivo , cuando vengo de nuevo sale un pantallazo y según el el fallo viene de "nwifi.sys"
¿Me podrian ayudar porfavor?
Hace poco formatee todo porque los pantallazos no paraban de saltar y todo me ha ido muy bien hasta ahora...
-Le he pasado avast y no me indica ningun virus... vv
Muchas gracias por la ayuda:)
Dejo aqui el análisis del dump que hice con windbg:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Users\Isma\Desktop\110513-34086-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0x82e56000 PsLoadedModuleList = 0x82f9f4d0
Debug session time: Tue Nov 5 12:20:49.467 2013 (UTC + 1:00)
System Uptime: 0 days 4:11:31.230
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\DRIVERS\nwifi.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nwifi.sys
*** ERROR: Module load completed but symbols could not be loaded for nwifi.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {75747879, 2, 0, 8b879860}

*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
*** WARNING: Unable to verify timestamp for athrusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrusb.sys
*** WARNING: Unable to verify timestamp for Wdf01000.sys
*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : nwifi.sys ( nwifi+4860 )

Followup: MachineOwner
---------

Avatar de Usuario
pako
Usuario Bill Gates
Usuario Bill Gates
Mensajes: 3591
Registrado: 22 Ene 2008, 13:30
Ubicación: España
Agradecido : 50 veces
Agradecimiento recibido: 277 veces
Contactar:

Re: Pantallazo azul (nwifi.sys)

Mensajepor pako » 05 Nov 2013, 16:46

Hola,

Bienvenido al foro :welcome:

A priori parece que el controlador que usas no es el correcto, realiza los siguiente pasos:
Generar Informe WhoCrashed:
1º.- Descarga la versión gratuita de WhoCrashed (Download free home edition).
2º.- Sobre el ejecutable whocrashedSetup.exe, botón derecho del ratón y seleccionar ejecutar como administrador para instalarlo.
3º.- Pulsa sobre el botón Analyze.
4º.- Tras finalizar baja hasta Crash Dump Analysis.
5º.- Copia el contenido que hay dentro de Crash Dump Analysis y de Conclusion, después pégalo en el foro.

Imagen


Saludos
Si has encontrado aquí la ayuda que esperabas (o incluso si no ha sido así ;) ), ayúdanos a mantener el foro con un pequeño donativo.
¡Muchas gracias!

astra3
Usuario linuxero
Usuario linuxero
Mensajes: 3
Registrado: 05 Nov 2013, 15:22
Agradecido : 2 veces
Contactar:

Re: Pantallazo azul (nwifi.sys)

Mensajepor astra3 » 05 Nov 2013, 17:43

Muchisimas gracias por contestar , de verdad y por la ayuda... ;)

Aquí va lo que me dice el programa que me recomendaste:
Crash dump directory: D:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 05/11/2013 11:20:49 GMT your computer crashed
crash dump file: D:\Windows\Minidump\110513-34086-01.dmp
This was probably caused by the following module: athrusb.sys (athrusb+0xD0A4)
Bugcheck code: 0xD1 (0x75747879, 0x2, 0x0, 0xFFFFFFFF8B879860)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: D:\Windows\system32\drivers\athrusb.sys
product: Driver for Atheros Wireless USB 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: athrusb.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 29/10/2013 17:26:47 GMT your computer crashed
crash dump file: D:\Windows\Minidump\102913-30607-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x1ED9)
Bugcheck code: 0xFE (0x5, 0xFFFFFFFF8558E0E0, 0x10DE07FE, 0xFFFFFFFF87B361AC)
Error: BUGCODE_USB_DRIVER
file path: D:\Windows\system32\drivers\usbport.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador de puertos USB 1.1 y 2.0
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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.


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:

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

Avatar de Usuario
pako
Usuario Bill Gates
Usuario Bill Gates
Mensajes: 3591
Registrado: 22 Ene 2008, 13:30
Ubicación: España
Agradecido : 50 veces
Agradecimiento recibido: 277 veces
Contactar:

Re: Pantallazo azul (nwifi.sys)  Tema Solucionado

Mensajepor pako » 06 Nov 2013, 13:00

Hola,

Como has podido comprobar el log te muestra a que se debe tu error:
athrusb.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)

Y mas arriba:
product: Driver for Atheros Wireless USB Network Adapter

Tienes algún adaptador USB Wireless con el chip Atheros que te esta dando problemas.
Para asegurarte, puedes desconectar el USB Wireless, dejarlo encendido como dices y no te debería de salir ya el pantallazo azul.

Para solucionarlo, debes buscar marca y modelo de tu USB Wireless, ir a la pagina del fabricante y descargarte los últimos drivers para tu modelo.
Desinstalar los drivers que tienes actualmente para tu USB Wireless con su desinstalador y reiniciar si lo requiere.
Después instalar el driver que te bajaste y seguir los pasos que te indique el programa.

Las ultimas versiones de los drivers corrigen varios bugs y lo mas seguro que se solucione tu problema, en caso negativo tendrás que ir instalando versiones anteriores hasta dar con la que realmente te funcionaba, o en su defecto puedes instalar el driver con el CD de instalación que te vino con la USB Wireless, será bastante viejo pero no deberías de tener problemas con el.

Saludos
Si has encontrado aquí la ayuda que esperabas (o incluso si no ha sido así ;) ), ayúdanos a mantener el foro con un pequeño donativo.
¡Muchas gracias!

astra3
Usuario linuxero
Usuario linuxero
Mensajes: 3
Registrado: 05 Nov 2013, 15:22
Agradecido : 2 veces
Contactar:

Re: Pantallazo azul (nwifi.sys)

Mensajepor astra3 » 06 Nov 2013, 13:57

Muchisimas gracias a ver que tal ahora ^^


Volver a “Windows 7”

¿Quién está conectado?

Usuarios navegando por este Foro: Bing [Bot] y 6 invitados