locked
problemas con pantalla azul Blue Screen RRS feed

  • Pregunta

  • Hola mi sistema operativo es Windows Vista y el pantallazo me ocurres desde hace una semana mas o memos que se instalaron algunas actualizaciones y comenzaron los problemas a continuación les indico lo que me dice el sistema de donde viene el problema:


    NOMBRE DEL EVENTO DE PROBLEMA BLUE SCREEN
    VERSION DEL SISTEMA OPERATIVO 6.0.6001.2.1.0.768.3
    ID DE CONFIGURACION REGIONAL 3082
    INFORMACION ADICONAL DEL PROBLEMA
    BCCODE:  1000008e
    BCP1   C0000005
    BCP2   8FAFC2B7
    BCP3   A7838AD4
    BCP4   00000000
    OS VERSION 6_0_6001
    SERVICE PACK 1_0
    PRODUCT     768_1
    DIAGNOCTICO (9f)

    archivos que ayudan a describir el problema
    C:\ WINDOWA\MINIDUMP\Mini061709-02.dmp
    C:\ Users\usuario\AppData\local\tem\WER-34023-0.SYSDATA.XML
    C:\ users\usuario\AppData\local\tem\WER9A7A.tmp.version.txt




    ACABA DE DAR OTRO PANTALLAZO Y AHORA INDICA OTROS REGISTROS DIFERENTE
    LOS REGISTRO DIFERENTES SON LOS SIGUIENTES
    BCP2   8F1022B7
    BCP3   9A6E7AD4

    C:\ Windows\minidump\mini062509-01.dmp
    C:\ Users\usuario\AppData\local\Tem\WER-24164-0.sysdata.xml
    C:\ Users\usuario\AppData\Local\Tem\WERA331.tmp.version.txt
    jueves, 25 de junio de 2009 10:22

Respuestas

  • Muchas gracias por todo. Me temia que era la única opción, solo le molesto por ultima vez lo que tenia entonces era un virus, por lo que he podido ver en internet pero bastante dañino por lo que veo
    Muchas gracias y hasta la proxima.

    Efectivamente, de los denominados RootKit. Recuerda que los antivirus no valen para nada, y que en una maquina solo hay algo que t eproteja y que nunca falla: las buenas practicas y el sentido comun.

    Un saludo,

    Untitled 1

    Jose Manuel Tella Llop news://jmtella.com

    jueves, 25 de junio de 2009 17:36

Todas las respuestas

  • Hola mi sistema operativo es Windows Vista y el pantallazo me ocurres desde hace una semana mas o memos que se instalaron algunas actualizaciones y comenzaron los problemas a continuación les indico lo que me dice el sistema de donde viene el problema:


    NOMBRE DEL EVENTO DE PROBLEMA BLUE SCREEN
    VERSION DEL SISTEMA OPERATIVO 6.0.6001.2.1.0.768.3
    ID DE CONFIGURACION REGIONAL 3082
    INFORMACION ADICONAL DEL PROBLEMA
    BCCODE:  1000008e
    BCP1   C0000005
    BCP2   8FAFC2B7
    BCP3   A7838AD4
    BCP4   00000000
    OS VERSION 6_0_6001
    SERVICE PACK 1_0
    PRODUCT     768_1
    DIAGNOCTICO (9f)

    archivos que ayudan a describir el problema
    C:\ WINDOWA\MINIDUMP\Mini061709-02.dmp
    C:\ Users\usuario\AppData\local\tem\WER-34023-0.SYSDATA.XML
    C:\ users\usuario\AppData\local\tem\WER9A7A.tmp.version.txt




    ACABA DE DAR OTRO PANTALLAZO Y AHORA INDICA OTROS REGISTROS DIFERENTE
    LOS REGISTRO DIFERENTES SON LOS SIGUIENTES
    BCP2   8F1022B7
    BCP3   9A6E7AD4

    C:\ Windows\minidump\mini062509-01.dmp
    C:\ Users\usuario\AppData\local\Tem\WER-24164-0.sysdata.xml
    C:\ Users\usuario\AppData\Local\Tem\WERA331.tmp.version.txt

    SE ME OLVIDO DECIR QUE NO ME DEJA INSTALAR NINGUN PROGRAMA, INTETE INSTALAR EL SERVI-PACK 2 PARA VISTA
    CREO UN PUNTO DE RESTAURACION Y AHORA TODO ES INUTIL, LA MEJOR SOLUCION SERIA FORMATEAR? O EXISTE OTRA QUE NO SEA TAN DRASTICA?
    jueves, 25 de junio de 2009 10:25
  • Primero lee esto y dejanos el dump de salida aqui para que lo veamos!!

    http://multingles.net/docs/jmt/bsod.htm

    Saludos!!
    jueves, 25 de junio de 2009 11:11
  • Carpeta de Minidump archivo mini062209-01.dmp
    descargado el programa Dump esto es lo que aparece:


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


    Loading Dump File [C:\Windows\Minidump\Mini062209-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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Machine Name:
    Kernel base = 0x8200a000 PsLoadedModuleList = 0x82121c70
    Debug session time: Mon Jun 22 17:24:33.948 2009 (GMT+2)
    System Uptime: 0 days 0:01:08.015
    *********************************************************************
    * 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
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {40000004, 1b, 1, 820c286c}

    ***** 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+                                    *
    *********************************************************************
    Probably caused by : ntkrnlpa.exe ( nt+b886c )

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

    SIGUIENTE ARCHIVO  062409-01.dmp

    este archivo dice que no se puede leer esta erroneo


    SIGUIENTE ARCHIVO 062509-01.dmp

    Loading Dump File [C:\Windows\Minidump\Mini062509-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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Machine Name:
    Kernel base = 0x8200f000 PsLoadedModuleList = 0x82126c70
    Debug session time: Thu Jun 25 12:08:48.552 2009 (GMT+2)
    System Uptime: 0 days 0:02:32.259
    *********************************************************************
    * 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\afd.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for afd.sys
    *** ERROR: Module load completed but symbols could not be loaded for afd.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 8f1022b7, 9a6e7ad4, 0}

    *** WARNING: Unable to verify timestamp for wfsintwq.sys
    *** ERROR: Module load completed but symbols could not be loaded for wfsintwq.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                                     ***
    ***                                                                   ***
    *************************************************************************
    *********************************************************************
    * 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 : wfsintwq.sys ( wfsintwq+15226 )

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


    EL ARCHIVO QUE NO SE PUEDE LEER , PARECE EL SIGUIENTE MENSAJE:


    COULD NOT CREATE PROCESS
    C:\Windows\minidump\mini062409-01.dmp
    Win32 error 0n193
    %1 no es una aplicación Win32 valida.



    Microsoft.(R) Windows Debugger Version 6.11.001.404x86
    Copyright (C) microsoft corporation. All rights reserved.
    Comandline: C:\Windows\Minidump\mini062409-01.dmp
    Cannot execute  C:\Windows \Minidump\mini062409-01.dmp, Win32 error 0n193
    %1 no es una aplicación Win32 valida.

    • Editado AnagoCha jueves, 25 de junio de 2009 17:15
    jueves, 25 de junio de 2009 16:56
  • No estan cargados los simbolos. Rewvisa lo que pongo en mi articulo de la configuracion y ademñas debes estar conectado a internet. La primera vez baja los simbolos y tardará un rato.

    En cualquier caso no es necesario que hagas nada ya que aun así de dice que el causantes del casque es el: Wfsintwq.sys.

    Preginta en Google por´él, y vas a alucinar... Lo siento, toca formatear y la proxima vez ser mas cuidaoso con lo que se hace...


    Un saludo,

    Jose Manuel Tella Llop news://jmtella.com

    jueves, 25 de junio de 2009 17:11
  • Muchas gracias por todo. Me temia que era la única opción, solo le molesto por ultima vez lo que tenia entonces era un virus, por lo que he podido ver en internet pero bastante dañino por lo que veo
    Muchas gracias y hasta la proxima.
    jueves, 25 de junio de 2009 17:23
  • Muchas gracias por todo. Me temia que era la única opción, solo le molesto por ultima vez lo que tenia entonces era un virus, por lo que he podido ver en internet pero bastante dañino por lo que veo
    Muchas gracias y hasta la proxima.

    Efectivamente, de los denominados RootKit. Recuerda que los antivirus no valen para nada, y que en una maquina solo hay algo que t eproteja y que nunca falla: las buenas practicas y el sentido comun.

    Un saludo,

    Untitled 1

    Jose Manuel Tella Llop news://jmtella.com

    jueves, 25 de junio de 2009 17:36