locked
pantallazos azules RRS feed

  • Pregunta

  • Buenas tardes, mi equipo se reinicia de vez en cuando es algo aleatorio, ya he instalado el debug y he analizado el dump pero no entiendo donde puede estar el error os dejo el pantallazo para que le echeis un vistazo:

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


    Loading Dump File [C:\WINDOWS\MEMORY.DMP]
    Kernel Complete Dump File: Full address space is 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:
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    *********************************************************************
    * 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 read PsLoadedModuleList
    KdDebuggerDataBlock not available!
    KdDebuggerData.KernBase < SystemRangeStart
    Windows XP Kernel Version 2600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x00000000 PsLoadedModuleList = 0x8055d720
    Debug session time: Mon Sep 14 15:28:52.883 2009 (GMT+2)
    System Uptime: 0 days 0:27:23.385
    *********************************************************************
    * 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 read PsLoadedModuleList
    KdDebuggerDataBlock not available!
    KdDebuggerData.KernBase < SystemRangeStart
    Loading Kernel Symbols
    Unable to read PsLoadedModuleList
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    CS descriptor lookup failed
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {e8, 2, 1, 806e7a16}

    ***** Debugger could not find nt in module list, module list might be corrupt.
    ***** Followup with Debugger team

    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    Probably caused by : Unknown_Image

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

    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    ?: kd> !analyce -v
    No export analyce found
    ?: kd> !analyxe -v
    No export analyxe found
    ?: kd> !analyze -v
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 000000e8, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 806e7a16, address which referenced memory

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

    ***** Debugger could not find nt in module list, module list might be corrupt.
    ***** Followup with Debugger team

    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002

    WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get MmPageSize (0x0) - probably bad symbols
     000000e8

    CURRENT_IRQL:  2

    FAULTING_IP:
    +ffffffff806e7a16
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    806e7a16 ??               ???

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0xA

    STACK_TEXT: 


    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME:  Unknown_Module

    IMAGE_NAME:  Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    STACK_COMMAND:  kb

    BUCKET_ID:  CORRUPT_MODULELIST

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




    Gracias y un saludo
    lunes, 14 de septiembre de 2009 13:39

Respuestas

  • **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************

    Al parecer ese volcado de memoria está corrupto. Prueba a analizar otros volcados de memoria, si es que el problema se reproduce nuevamente.
    Microsoft MVP Windows Desktop Experience
    martes, 15 de septiembre de 2009 13:58

Todas las respuestas

  • Cual es mensaje de error que te sale en el Blue Screen, en caso que se reinicie automaticamente y no podes ver el error, realiza la siguiente:

    Boton derecho sobre mi pc - Opciones Avanzadas - Inicio y recuperacion - destilda el reiniciar automaticamente.

    Saludos.
    Adrian Rodriguez -
    lunes, 14 de septiembre de 2009 15:03
  • Hola, el mensaje de error pone lo de IRQL_NOT_LESS_OR_EQUAL
    Y mas abajo pone: STOP 0x0000000A (0x000000E8, 0x00000002, 0x00000001, 0x806E7A16)
    Si necesitas algo mas, avisa. Gracias
    lunes, 14 de septiembre de 2009 18:59
  • Es necesario que configures antes los símbolos de depuración en Windbg. Echa un vistazo a la sección ¿Cómo configurar la información referente a los símbolos de depuración en Windbg? de este artículo mío: http://msmvps.com/blogs/dmartin/archive/2009/04/04/tutorial-sobre-windbg-parte-i.aspx

    Microsoft MVP Windows Desktop Experience
    martes, 15 de septiembre de 2009 10:17
  • Ya lo he hecho, y al pasar el Windbg esto es lo que ha salido:


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


    Loading Dump File [C:\WINDOWS\MEMORY.DMP]
    Kernel Complete Dump File: Full address space is available

    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    Unable to read PsLoadedModuleList
    KdDebuggerDataBlock not available!
    KdDebuggerData.KernBase < SystemRangeStart
    Windows XP Kernel Version 2600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x00000000 PsLoadedModuleList = 0x8055d720
    Debug session time: Tue Sep 15 11:20:11.359 2009 (GMT+2)
    System Uptime: 0 days 0:00:36.110
    Unable to read PsLoadedModuleList
    KdDebuggerDataBlock not available!
    KdDebuggerData.KernBase < SystemRangeStart
    Loading Kernel Symbols
    Unable to read PsLoadedModuleList
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    CS descriptor lookup failed
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {e8, 2, 1, 806e7a16}

    ***** Debugger could not find nt in module list, module list might be corrupt.
    ***** Followup with Debugger team

    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    Probably caused by : Unknown_Image

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

    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    martes, 15 de septiembre de 2009 10:53
  • **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************

    Al parecer ese volcado de memoria está corrupto. Prueba a analizar otros volcados de memoria, si es que el problema se reproduce nuevamente.
    Microsoft MVP Windows Desktop Experience
    martes, 15 de septiembre de 2009 13:58
  • El problema sigue, en este rato han aparecido dos pantallazos azules, uno de ellos me daba como error lo siguiente:

    Multiple_Irp_Complete_Request

    Stop 0x00000044

    Y el siguiente pantallazo seguia siendo el de siempre.

    He probado a pasar el Windbg otra vez, pero no me funciona, le doy a analizar y no sale nada...
    martes, 15 de septiembre de 2009 14:14
  • He pasado el Windbg y esto es lo que ha salido:


    Loading Dump File [C:\WINDOWS\MEMORY.DMP]
    Kernel Complete Dump File: Full address space is available

    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Unable to read KLDR_DATA_TABLE_ENTRY at 8a58b3a0 - NTSTATUS 0xC0000147

    "nt" was not found in the image list.
    Debugger will attempt to load "nt" at given base 00000000.

    Please provide the full image name, including the extension (i.e. kernel32.dll)
    for more reliable results.Base address and size overrides can be given as
    .reload <image.ext>=<base>,<size>.
    Unable to add module at 00000000
    WARNING: .reload failed, module list may be incomplete
    Debugger can not determine kernel base address
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp3_gdr.090206-1234
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Wed Sep 16 20:55:12.390 2009 (GMT+2)
    System Uptime: 0 days 0:43:41.143
    Unable to read KLDR_DATA_TABLE_ENTRY at 8a58b3a0 - NTSTATUS 0xC0000147

    "nt" was not found in the image list.
    Debugger will attempt to load "nt" at given base 00000000.

    Please provide the full image name, including the extension (i.e. kernel32.dll)
    for more reliable results.Base address and size overrides can be given as
    .reload <image.ext>=<base>,<size>.
    Unable to add module at 00000000
    WARNING: .reload failed, module list may be incomplete
    Debugger can not determine kernel base address
    Loading Kernel Symbols
    Unable to read KLDR_DATA_TABLE_ENTRY at 8a58b3a0 - NTSTATUS 0xC0000147

    WARNING: .reload failed, module list may be incomplete
    Unable to read KLDR_DATA_TABLE_ENTRY at 8a58b3a0 - NTSTATUS 0xC0000147
    Unable to read KLDR_DATA_TABLE_ENTRY at 8a58b3a0 - NTSTATUS 0xC0000147
    Unable to read KLDR_DATA_TABLE_ENTRY at 8a58b3a0 - NTSTATUS 0xC0000147
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 44, {89614008, d64, 0, 0}

    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

    Unable to read KLDR_DATA_TABLE_ENTRY at 8a58b3a0 - NTSTATUS 0xC0000147
    Unable to read KLDR_DATA_TABLE_ENTRY at 8a58b3a0 - NTSTATUS 0xC0000147
    Unable to read KLDR_DATA_TABLE_ENTRY at 8a58b3a0 - NTSTATUS 0xC0000147
    Unable to read KLDR_DATA_TABLE_ENTRY at 8a58b3a0 - NTSTATUS 0xC0000147
    Unable to read KLDR_DATA_TABLE_ENTRY at 8a58b3a0 - NTSTATUS 0xC0000147
    Unable to read KLDR_DATA_TABLE_ENTRY at 8a58b3a0 - NTSTATUS 0xC0000147
    Unable to read KLDR_DATA_TABLE_ENTRY at 8a58b3a0 - NTSTATUS 0xC0000147
    Unable to read KLDR_DATA_TABLE_ENTRY at 8a58b3a0 - NTSTATUS 0xC0000147

    .....(ESO SE REPITE MUCHAS VECES)

    GetContextState failed, 0xD0000147
    Unable to read selector for PCR for processor 1
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    Followup: MachineOwner


    Siguen apareciendo los pantallazos. Gracias
    miércoles, 16 de septiembre de 2009 20:00
  • Hola wikkimen,

    Teniendo en cuenta que los errores son aleatorios, podrías realizar un diagnóstico de las memorias: http://www.memtest.org/#downiso

    Si el problema no está ahí, habría que ver el resto del hardware, para descartar que le problema venga por ese lado.

    Saludos!
    miércoles, 16 de septiembre de 2009 20:42
  • He pasado el Memtest y no ha dado error.
    Como puedo comprobar el resto del hardware???

    Gracias!
    miércoles, 16 de septiembre de 2009 21:46
  • Por el tipo de problema que te da que es aleatorio, yo tambien pienso que se la Memoria, seria bueno que probaras con otras, te lo sugiero ya que yo he tenido ese problema y aparentemente todo estaba bien, si tenes mas de un modulo de memoria proba uno por uno para hacer mas exaco el diagnostico
    sábado, 19 de septiembre de 2009 18:24
  • De la memoria no creo que sea, porque me probaron con otra y no se daba el pantallazo, ademas ayer me salio un error nuevo:

    BUGCODE_USB_DRIVER

    Y buscando por ahi, he leido que puede ser del modem, ya que otras personas con mi mismo modem, tenian ese problema...Ademas solo se da en mi casa, si pruebo el ordenador en otra casa, con o sin Internet, pero con distinto modem, no se da el pantallazo...por eso, excluyendo, creo que pueda ser debido a eso...

    En ese caso, como se soluciona, ya que el modem es algo de lo que no puedo prescindir...

    Gracias
    lunes, 21 de septiembre de 2009 18:19
  • Hola, parece que lo he solucionado. Como yo decia, debia ser del modem, he cambiado la conexion al router via usb, por la conexion con un cable RJ45. Lleva desde el viernes asi, y no ha habido pantallazos (cosa que ocurria a diario), por lo que parece que lo he solucionado.

    Gracias a todos los que me habeis intentado ayudar.

    Un saludo
    martes, 29 de septiembre de 2009 10:39