• Registrarse
  • Iniciar sesión


  • Resultados 1 al 8 de 8

    Pantalla Azul windows 7

    Resumen del tema: Pantalla Azul windows 7 - Que tal :D tengo problema con una laptop El problema es que me sale la clasica pantalla azul cada vez que instalo o remuevo algun programa como el Norton que era el antivirus que traia ...

    1. #1
      Usuario Avatar de Rohs0385
      Registrado
      feb 2010
      Ubicación
      Mexico
      Mensajes
      5

      Pantalla Azul windows 7

      Que tal :D

      tengo problema con una laptop

      El problema es que me sale la clasica pantalla azul cada vez que instalo o remuevo algun programa como el Norton que era el antivirus que traia por default.

      Tengo que entrar como modo seguro y hacer el "recovery" para poder entrar en modo normal.

      aqui esta el analisis del debug de windows
      Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
      Copyright (c) Microsoft Corporation. All rights reserved.


      Loading Dump File [C:\Windows\Minidump\022310-22620-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\ntoskrnl.exe, Win32 error 0n2
      *** WARNING: Unable to verify timestamp for ntoskrnl.exe
      *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
      Windows 7 Kernel Version 7600 UP Free x64
      Product: WinNt, suite: TerminalServer SingleUserTS Personal
      Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
      Machine Name:
      Kernel base = 0xfffff800`02a66000 PsLoadedModuleList = 0xfffff800`02ca3e50
      Debug session time: Tue Feb 23 19:02:58.059 2010 (GMT-8)
      System Uptime: 0 days 0:22:05.010
      *********************************************************************
      * 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\ntoskrnl.exe, Win32 error 0n2
      *** WARNING: Unable to verify timestamp for ntoskrnl.exe
      *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
      Loading Kernel Symbols
      ...............................................................
      ................................................................
      .................................
      Loading User Symbols
      Loading unloaded module list
      .....
      *******************************************************************************
      * *
      * Bugcheck Analysis *
      * *
      *******************************************************************************

      Use !analyze -v to get detailed debugging information.

      BugCheck D1, {10, 2, 0, fffff8800146a5d6}

      ***** 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 ***
      *** ***
      *************************************************************************
      *** WARNING: Unable to verify timestamp for ndis.sys
      *** ERROR: Module load completed but symbols could not be loaded for ndis.sys
      *************************************************************************
      *** ***
      *** ***
      *** 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 ***
      *** ***
      *************************************************************************
      *********************************************************************
      * 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+ *
      *********************************************************************
      *********************************************************************
      * 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+ *
      *********************************************************************
      Probably caused by : ndis.sys ( ndis+2e5d6 )

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

      kd> !analyze -v
      *******************************************************************************
      * *
      * Bugcheck Analysis *
      * *
      *******************************************************************************

      DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
      An attempt was made to access a pageable (or completely invalid) address at an
      interrupt request level (IRQL) that is too high. This is usually
      caused by drivers using improper addresses.
      If kernel debugger is available get stack backtrace.
      Arguments:
      Arg1: 0000000000000010, memory referenced
      Arg2: 0000000000000002, IRQL
      Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
      Arg4: fffff8800146a5d6, address which referenced memory

      Debugging Details:
      ------------------

      ***** 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 ***
      *** ***
      *************************************************************************
      *********************************************************************
      * 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+ *
      *********************************************************************
      *********************************************************************
      * 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+ *
      *********************************************************************

      ADDITIONAL_DEBUG_TEXT:
      Use '!findthebuild' command to search for the target build information.
      If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

      MODULE_NAME: ndis

      FAULTING_MODULE: fffff80002a66000 nt

      DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc184

      READ_ADDRESS: unable to get nt!MmSpecialPoolStart
      unable to get nt!MmSpecialPoolEnd
      unable to get nt!MmPoolCodeStart
      unable to get nt!MmPoolCodeEnd
      0000000000000010

      CURRENT_IRQL: 0

      FAULTING_IP:
      ndis+2e5d6
      fffff880`0146a5d6 488b5310 mov rdx,qword ptr [rbx+10h]

      CUSTOMER_CRASH_COUNT: 1

      DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

      BUGCHECK_STR: 0xD1

      LAST_CONTROL_TRANSFER: from fffff80002ad7469 to fffff80002ad7f00

      STACK_TEXT:
      fffff880`02f31748 fffff800`02ad7469 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt+0x71f00
      fffff880`02f31750 00000000`0000000a : 00000000`00000010 00000000`00000002 00000000`00000000 fffff880`0146a5d6 : nt+0x71469
      fffff880`02f31758 00000000`00000010 : 00000000`00000002 00000000`00000000 fffff880`0146a5d6 fffff780`c0000488 : 0xa
      fffff880`02f31760 00000000`00000002 : 00000000`00000000 fffff880`0146a5d6 fffff780`c0000488 00000000`00000000 : 0x10
      fffff880`02f31768 00000000`00000000 : fffff880`0146a5d6 fffff780`c0000488 00000000`00000000 00000000`00000000 : 0x2


      STACK_COMMAND: .bugcheck ; kb

      FOLLOWUP_IP:
      ndis+2e5d6
      fffff880`0146a5d6 488b5310 mov rdx,qword ptr [rbx+10h]

      SYMBOL_NAME: ndis+2e5d6

      FOLLOWUP_NAME: MachineOwner

      IMAGE_NAME: ndis.sys

      BUCKET_ID: WRONG_SYMBOLS

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

      quisiera saber como eliminar esto.
      Muchas gracias

    2. #2
      Ex-Colaborador Avatar de Zackrated
      Registrado
      ago 2009
      Ubicación
      León, México
      Mensajes
      7.947

      Re: Pantalla Azul windows 7

      Hola Rohs0385

      Ya me tocó ver un problema similar al tuyo.

      El problema es el controlador de red, vamos a comprobarlo.

      Realiza lo siguiente:

      Equipo>Propiedades>Administrador de Dispositivos

      Da click en el signo más (+) en adaptadores de red y deshabilita

      Si te conectas por WiFi, desactiva la tarjeta de red inalámbrica
      Si te conectas por Cable, desactiva la tarjeta de red.

      Click derecho>Deshabilitar.

      NO te conectas a internet.

      Ahora trata de producir el pantallazo desinstalando el Norton u otro programa que te da problemas.

      Nos comentas.

      Un saludo

      * Síguenos en nuestro Twitter y hazte nuestro amigo en Facebook.
      * Infórmate de las ultimas amenazas de la red desde: InfoSpyware Blog
      * No se resuelven dudas por Privados ni por E-mail, ya que para eso esta el foro.

    3. #3
      Usuario Avatar de Rohs0385
      Registrado
      feb 2010
      Ubicación
      Mexico
      Mensajes
      5

      Re: Pantalla Azul windows 7

      Buen dia

      En Efecto el problema es con el controlador de red

      pude instalar y desinstalar programas con las tarjetas de red deshabilitadas, aunque caso curioso es que aveces sin estar conectado a internet no me dejaba ni instalar ni desinstalar nada.
      otro detalle que vi cuando estaba deshabilitando las tarjetas de red es que la que me esta dando problemas es una tarjeta que se llama Microsoft virtual WiFi miniport adapter desconosco de que sea......
      al habilitarla salio el pantallazo azul de nueva cuenta.

      Gracias.

    4. #4
      Ex-Colaborador Avatar de Zackrated
      Registrado
      ago 2009
      Ubicación
      León, México
      Mensajes
      7.947

      Re: Pantalla Azul windows 7

      Hola Rohs0385

      La solución está en instalar un controlador más reciente.

      Proporcioname la marca y modelo de tu PC y te ayudo a buscarlo.

      Un saludo

      * Síguenos en nuestro Twitter y hazte nuestro amigo en Facebook.
      * Infórmate de las ultimas amenazas de la red desde: InfoSpyware Blog
      * No se resuelven dudas por Privados ni por E-mail, ya que para eso esta el foro.

    5. #5
      Usuario Avatar de Rohs0385
      Registrado
      feb 2010
      Ubicación
      Mexico
      Mensajes
      5

      Re: Pantalla Azul windows 7

      La laptop es emachines y el modelo E627 si necesitas mayor informacion te paso el analisis del Everest

      Gracias

    6. #6
      Ex-Colaborador Avatar de Zackrated
      Registrado
      ago 2009
      Ubicación
      León, México
      Mensajes
      7.947

      Re: Pantalla Azul windows 7

      Hola

      Los drivers los encuentras aquí eMachines Support: Drivers and Downloads

      Selecciona Notebook>E Series>E627

      Ahi aparecerán los drivers. Hay varios para tus tarjetas de red.

      Pega una captura de pantalla de Administrador de Dispositivos

      Equipo>Propiedades>Administrador de Dispositivos

      Da click en en mas (+) en Adaptadores de red.
      Toma la captura y la pegas en tu próxima respuesta.

      ¿Cómo subir imágenes al Foro? *TUTORIAL*

      * Síguenos en nuestro Twitter y hazte nuestro amigo en Facebook.
      * Infórmate de las ultimas amenazas de la red desde: InfoSpyware Blog
      * No se resuelven dudas por Privados ni por E-mail, ya que para eso esta el foro.

    7. #7
      Usuario Avatar de Rohs0385
      Registrado
      feb 2010
      Ubicación
      Mexico
      Mensajes
      5

      Re: Pantalla Azul windows 7

      Ahi esta la imagen



      Al parecer no esta el driver mas qu este
      Lan Atheros LAN Driver 1.0.0.19 4.4 MB 2009/08/04

      lo descargue, instale y no paso nada sigue el mismo problema

    8. #8
      Ex-Colaborador Avatar de Zackrated
      Registrado
      ago 2009
      Ubicación
      León, México
      Mensajes
      7.947

      Re: Pantalla Azul windows 7

      Hola

      ¿Cuando instalaste el controlador que te descargaste desde Emachines, desinstalaste el anterior antes de instalar el nuevo.?

      Un saludo

      * Síguenos en nuestro Twitter y hazte nuestro amigo en Facebook.
      * Infórmate de las ultimas amenazas de la red desde: InfoSpyware Blog
      * No se resuelven dudas por Privados ni por E-mail, ya que para eso esta el foro.