locked
Windows 7 se reinicia esporadicamente. RRS feed

  • Pregunta

  • Buenas desde hace un tiempo mi Computadora se reinicia mucho dándome pantallazos azules y quisiera saber el motivo.

    Mi Pc es un Intel Quadcore con 4gb y Windows 7 HOME 64BITS sp1

    Les dejo un registr


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


    Loading Dump File [C:\Windows\Minidump\042714-23150-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 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 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Machine Name:
    Kernel base = 0xfffff800`03061000 PsLoadedModuleList = 0xfffff800`032a46d0
    Debug session time: Sun Apr 27 11:26:01.722 2014 (GMT+2)
    System Uptime: 0 days 0:07:07.485
    *********************************************************************
    * 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 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
    Missing image name, possible paged-out or corrupt data.
    Loading unloaded module list
    .Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    ....Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    ...Missing image name, possible paged-out or corrupt data.
    ...Missing image name, possible paged-out or corrupt data.
    ..Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    .
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7E, {ffffffffc0000005, fffff800030f0eb7, fffff880040b42b8, fffff880040b3b10}

    ***** 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 : Unknown_Module_fffffa80`037223a0 ( Unknown_Module_fffffa80`037223a0>+15f5238 )

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

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

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800030f0eb7, The address that the exception occurred at
    Arg3: fffff880040b42b8, Exception Record Address
    Arg4: fffff880040b3b10, Context Record Address

    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.

    FAULTING_MODULE: fffff80003061000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.

    FAULTING_IP:
    nt+8feb7
    fffff800`030f0eb7 0fb7790a        movzx   edi,word ptr [rcx+0Ah]

    EXCEPTION_RECORD:  fffff880040b42b8 -- (.exr 0xfffff880040b42b8)
    Cannot read Exception record @ fffff880040b42b8

    CONTEXT:  fffff880040b3b10 -- (.cxr 0xfffff880040b3b10)
    Unable to read context, Win32 error 0n30

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x7E

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff800030df709 to fffff88002c649c2

    STACK_TEXT: 
    fffff800`00b9cc98 fffff800`030df709 : 00000000`0022c506 fffffa80`04d175d8 fffff800`0325fcc0 00000000`00000001 : 0xfffff880`02c649c2
    fffff800`00b9cca0 00000000`0022c506 : fffffa80`04d175d8 fffff800`0325fcc0 00000000`00000001 fffff800`03251e80 : nt+0x7e709
    fffff800`00b9cca8 fffffa80`04d175d8 : fffff800`0325fcc0 00000000`00000001 fffff800`03251e80 fffff800`030e13c7 : <Unloaded_Unknown_Module_00000000`00000001>+0x22c505
    fffff800`00b9ccb0 fffff800`0325fcc0 : 00000000`00000001 fffff800`03251e80 fffff800`030e13c7 00000000`3a1b5c13 : <Unloaded_Unknown_Module_fffffa80`037223a0>+0x15f5238
    fffff800`00b9ccb8 00000000`00000001 : fffff800`03251e80 fffff800`030e13c7 00000000`3a1b5c13 00000000`00006b0a : nt+0x1fecc0
    fffff800`00b9ccc0 fffff800`03251e80 : fffff800`030e13c7 00000000`3a1b5c13 00000000`00006b0a 00000000`3a1b5c13 : <Unloaded_Unknown_Module_00000000`00000001>
    fffff800`00b9ccc8 fffff800`030e13c7 : 00000000`3a1b5c13 00000000`00006b0a 00000000`3a1b5c13 00000000`0000000a : nt+0x1f0e80
    fffff800`00b9ccd0 00000000`3a1b5c13 : 00000000`00006b0a 00000000`3a1b5c13 00000000`0000000a fffffa80`04d17540 : nt+0x803c7
    fffff800`00b9ccd8 00000000`00006b0a : 00000000`3a1b5c13 00000000`0000000a fffffa80`04d17540 400000c2`400000c1 : <Unloaded_Unknown_Module_00000000`00000001>+0x3a1b5c12
    fffff800`00b9cce0 00000000`3a1b5c13 : 00000000`0000000a fffffa80`04d17540 400000c2`400000c1 0000000a`400000c3 : <Unloaded_Unknown_Module_00000000`00000001>+0x6b09
    fffff800`00b9cce8 00000000`0000000a : fffffa80`04d17540 400000c2`400000c1 0000000a`400000c3 00000000`33a78bae : <Unloaded_Unknown_Module_00000000`00000001>+0x3a1b5c12
    fffff800`00b9ccf0 fffffa80`04d17540 : 400000c2`400000c1 0000000a`400000c3 00000000`33a78bae fffff800`00b96080 : <Unloaded_Unknown_Module_00000000`00000001>+0x9
    fffff800`00b9ccf8 400000c2`400000c1 : 0000000a`400000c3 00000000`33a78bae fffff800`00b96080 fffffa80`0366b9e0 : <Unloaded_Unknown_Module_fffffa80`037223a0>+0x15f51a0
    fffff800`00b9cd00 0000000a`400000c3 : 00000000`33a78bae fffff800`00b96080 fffffa80`0366b9e0 00000000`00000000 : 0x400000c2`400000c1
    fffff800`00b9cd08 00000000`33a78bae : fffff800`00b96080 fffffa80`0366b9e0 00000000`00000000 000000e8`250c01fd : 0xa`400000c3
    fffff800`00b9cd10 fffff800`00b96080 : fffffa80`0366b9e0 00000000`00000000 000000e8`250c01fd 000000e8`250c0cd8 : <Unloaded_Unknown_Module_00000000`00000001>+0x33a78bad
    fffff800`00b9cd18 fffffa80`0366b9e0 : 00000000`00000000 000000e8`250c01fd 000000e8`250c0cd8 fffff800`00b96080 : 0xfffff800`00b96080
    fffff800`00b9cd20 00000000`00000000 : 000000e8`250c01fd 000000e8`250c0cd8 fffff800`00b96080 fffff800`00b96080 : 0xfffffa80`0366b9e0


    FOLLOWUP_IP:
    Unknown_Module_fffffa80`037223a0>+15f5238
    fffffa80`04d175d8 ??              ???

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  Unknown_Module_fffffa80`037223a0>+15f5238

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Unknown_Module_fffffa80`037223a0

    IMAGE_NAME:  Unknown_Module_fffffa80`037223a0

    STACK_COMMAND:  .cxr 0xfffff880040b3b10 ; kb

    BUCKET_ID:  WRONG_SYMBOLS

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

    o analazido con el Windbg.

    domingo, 27 de abril de 2014 10:18

Respuestas

  • Para obtener información más significativa hay que configurar correctamente el acceso al servidor de símbolos de depuración de Microsoft, poniendo la siguiente línea en menú File, Symbol File Path:

    srv*c:\símbolos*http://msdl.microsoft.com/download/symbols

    No puede haber espacios o líneas en blanco dentro del cuadro de edición. La carpeta Símbolos, que servirá como almacén, debe estar creada de antemano en C:\.


    No puedo garantizar a priori que mis respuestas sean exactas y acordes a los problemas descritos, pero por lo menos yo no las voy marcando como propuestas o definitivas sin saber si han sido útiles o no. Sobre todo no me gusta que lo hagan los moderadores. Tampoco vinculado a Microsoft.

    • Propuesto como respuesta Uriel Almendra lunes, 28 de abril de 2014 14:17
    • Marcado como respuesta Uriel Almendra viernes, 2 de mayo de 2014 15:59
    domingo, 27 de abril de 2014 15:52

Todas las respuestas

  • Para obtener información más significativa hay que configurar correctamente el acceso al servidor de símbolos de depuración de Microsoft, poniendo la siguiente línea en menú File, Symbol File Path:

    srv*c:\símbolos*http://msdl.microsoft.com/download/symbols

    No puede haber espacios o líneas en blanco dentro del cuadro de edición. La carpeta Símbolos, que servirá como almacén, debe estar creada de antemano en C:\.


    No puedo garantizar a priori que mis respuestas sean exactas y acordes a los problemas descritos, pero por lo menos yo no las voy marcando como propuestas o definitivas sin saber si han sido útiles o no. Sobre todo no me gusta que lo hagan los moderadores. Tampoco vinculado a Microsoft.

    • Propuesto como respuesta Uriel Almendra lunes, 28 de abril de 2014 14:17
    • Marcado como respuesta Uriel Almendra viernes, 2 de mayo de 2014 15:59
    domingo, 27 de abril de 2014 15:52

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


    Loading Dump File [C:\Windows\Minidump\042714-23150-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*c:\símbolos*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Machine Name:
    Kernel base = 0xfffff800`03061000 PsLoadedModuleList = 0xfffff800`032a46d0
    Debug session time: Sun Apr 27 11:26:01.722 2014 (GMT+2)
    System Uptime: 0 days 0:07:07.485
    Loading Kernel Symbols
    .............................................
    Loading User Symbols
    Missing image name, possible paged-out or corrupt data.
    Loading unloaded module list
    .Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    ....Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    ...Missing image name, possible paged-out or corrupt data.
    ...Missing image name, possible paged-out or corrupt data.
    ..Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    .
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7E, {ffffffffc0000005, fffff800030f0eb7, fffff880040b42b8, fffff880040b3b10}

    Probably caused by : ntkrnlmp.exe ( nt!IoFreeMdl+7 )

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

    lunes, 28 de abril de 2014 16:41
  • ¿Y el !analyze -v?

    No puedo garantizar a priori que mis respuestas sean exactas y acordes a los problemas descritos, pero por lo menos yo no las voy marcando como propuestas o definitivas sin saber si han sido útiles o no. Sobre todo no me gusta que lo hagan los moderadores. Tampoco vinculado a Microsoft.

    lunes, 28 de abril de 2014 16:53
  • A VER SI AHORA!
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\042714-23150-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 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 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Machine Name:
    Kernel base = 0xfffff800`03061000 PsLoadedModuleList = 0xfffff800`032a46d0
    Debug session time: Sun Apr 27 10:26:01.722 2014 (GMT+1)
    System Uptime: 0 days 0:07:07.485
    *********************************************************************
    * 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 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
    Missing image name, possible paged-out or corrupt data.
    Loading unloaded module list
    .Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    ....Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    ...Missing image name, possible paged-out or corrupt data.
    ...Missing image name, possible paged-out or corrupt data.
    ..Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    .Missing image name, possible paged-out or corrupt data.
    .
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7E, {ffffffffc0000005, fffff800030f0eb7, fffff880040b42b8, fffff880040b3b10}

    ***** 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 : Unknown_Module_fffffa80`037223a0 ( Unknown_Module_fffffa80`037223a0>+15f5238 )

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

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

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800030f0eb7, The address that the exception occurred at
    Arg3: fffff880040b42b8, Exception Record Address
    Arg4: fffff880040b3b10, Context Record Address

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

    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.

    FAULTING_MODULE: fffff80003061000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.

    FAULTING_IP:
    nt+8feb7
    fffff800`030f0eb7 0fb7790a        movzx   edi,word ptr [rcx+0Ah]

    EXCEPTION_RECORD:  fffff880040b42b8 -- (.exr 0xfffff880040b42b8)
    Cannot read Exception record @ fffff880040b42b8

    CONTEXT:  fffff880040b3b10 -- (.cxr 0xfffff880040b3b10)
    Unable to read context, Win32 error 0n30

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x7E

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff800030df709 to fffff88002c649c2

    STACK_TEXT: 
    fffff800`00b9cc98 fffff800`030df709 : 00000000`0022c506 fffffa80`04d175d8 fffff800`0325fcc0 00000000`00000001 : 0xfffff880`02c649c2
    fffff800`00b9cca0 00000000`0022c506 : fffffa80`04d175d8 fffff800`0325fcc0 00000000`00000001 fffff800`03251e80 : nt+0x7e709
    fffff800`00b9cca8 fffffa80`04d175d8 : fffff800`0325fcc0 00000000`00000001 fffff800`03251e80 fffff800`030e13c7 : <Unloaded_Unknown_Module_00000000`00000001>+0x22c505
    fffff800`00b9ccb0 fffff800`0325fcc0 : 00000000`00000001 fffff800`03251e80 fffff800`030e13c7 00000000`3a1b5c13 : <Unloaded_Unknown_Module_fffffa80`037223a0>+0x15f5238
    fffff800`00b9ccb8 00000000`00000001 : fffff800`03251e80 fffff800`030e13c7 00000000`3a1b5c13 00000000`00006b0a : nt+0x1fecc0
    fffff800`00b9ccc0 fffff800`03251e80 : fffff800`030e13c7 00000000`3a1b5c13 00000000`00006b0a 00000000`3a1b5c13 : <Unloaded_Unknown_Module_00000000`00000001>
    fffff800`00b9ccc8 fffff800`030e13c7 : 00000000`3a1b5c13 00000000`00006b0a 00000000`3a1b5c13 00000000`0000000a : nt+0x1f0e80
    fffff800`00b9ccd0 00000000`3a1b5c13 : 00000000`00006b0a 00000000`3a1b5c13 00000000`0000000a fffffa80`04d17540 : nt+0x803c7
    fffff800`00b9ccd8 00000000`00006b0a : 00000000`3a1b5c13 00000000`0000000a fffffa80`04d17540 400000c2`400000c1 : <Unloaded_Unknown_Module_00000000`00000001>+0x3a1b5c12
    fffff800`00b9cce0 00000000`3a1b5c13 : 00000000`0000000a fffffa80`04d17540 400000c2`400000c1 0000000a`400000c3 : <Unloaded_Unknown_Module_00000000`00000001>+0x6b09
    fffff800`00b9cce8 00000000`0000000a : fffffa80`04d17540 400000c2`400000c1 0000000a`400000c3 00000000`33a78bae : <Unloaded_Unknown_Module_00000000`00000001>+0x3a1b5c12
    fffff800`00b9ccf0 fffffa80`04d17540 : 400000c2`400000c1 0000000a`400000c3 00000000`33a78bae fffff800`00b96080 : <Unloaded_Unknown_Module_00000000`00000001>+0x9
    fffff800`00b9ccf8 400000c2`400000c1 : 0000000a`400000c3 00000000`33a78bae fffff800`00b96080 fffffa80`0366b9e0 : <Unloaded_Unknown_Module_fffffa80`037223a0>+0x15f51a0
    fffff800`00b9cd00 0000000a`400000c3 : 00000000`33a78bae fffff800`00b96080 fffffa80`0366b9e0 00000000`00000000 : 0x400000c2`400000c1
    fffff800`00b9cd08 00000000`33a78bae : fffff800`00b96080 fffffa80`0366b9e0 00000000`00000000 000000e8`250c01fd : 0xa`400000c3
    fffff800`00b9cd10 fffff800`00b96080 : fffffa80`0366b9e0 00000000`00000000 000000e8`250c01fd 000000e8`250c0cd8 : <Unloaded_Unknown_Module_00000000`00000001>+0x33a78bad
    fffff800`00b9cd18 fffffa80`0366b9e0 : 00000000`00000000 000000e8`250c01fd 000000e8`250c0cd8 fffff800`00b96080 : 0xfffff800`00b96080
    fffff800`00b9cd20 00000000`00000000 : 000000e8`250c01fd 000000e8`250c0cd8 fffff800`00b96080 fffff800`00b96080 : 0xfffffa80`0366b9e0


    FOLLOWUP_IP:
    Unknown_Module_fffffa80`037223a0>+15f5238
    fffffa80`04d175d8 ??              ???

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  Unknown_Module_fffffa80`037223a0>+15f5238

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Unknown_Module_fffffa80`037223a0

    IMAGE_NAME:  Unknown_Module_fffffa80`037223a0

    STACK_COMMAND:  .cxr 0xfffff880040b3b10 ; kb

    BUCKET_ID:  WRONG_SYMBOLS

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

    lunes, 28 de abril de 2014 19:06