locked
Blue Screen en WinVista Home Basic RRS feed

  • Pregunta

  • Hola..
    Tengo el sgte problema, mi Pc empezo hace un mes aprox a producir el error blue screen. Hice un analisis con el debugging y me arrojo lo sgte:
    --------------------------------------------------------------------------------------------------------------------------------------------------------------------

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


    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
    Kernel base = 0x81e1e000 PsLoadedModuleList = 0x81f35c70
    Debug session time: Wed Sep 24 21:35:10.809 2008 (GMT-4)
    System Uptime: 0 days 0:14:09.374
    Loading Kernel Symbols
    ................................................................................................................................................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 7ffdf00c).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1A, {3452, 1d56000, c080613c, 475bec24}

    Page 56746 not present in the dump file. Type ".hh dbgerr004" for details
    Page 56c46 not present in the dump file. Type ".hh dbgerr004" for details
    PEB is paged out (Peb.Ldr = 7ffdf00c).  Type ".hh dbgerr001" for details
    PEB is paged out (Peb.Ldr = 7ffdf00c).  Type ".hh dbgerr001" for details
    Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+2fb )

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

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

    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 00003452, The subtype of the bugcheck.
    Arg2: 01d56000
    Arg3: c080613c
    Arg4: 475bec24

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

    Page 56746 not present in the dump file. Type ".hh dbgerr004" for details
    Page 56c46 not present in the dump file. Type ".hh dbgerr004" for details
    PEB is paged out (Peb.Ldr = 7ffdf00c).  Type ".hh dbgerr001" for details
    PEB is paged out (Peb.Ldr = 7ffdf00c).  Type ".hh dbgerr001" for details

    BUGCHECK_STR:  0x1a_3452

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  EDICT.EXE

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 81ebdf4e to 81ebf7a4

    STACK_TEXT: 
    a5f59c4c 81ebdf4e 870a8170 00000000 00000000 nt!MiDeleteAddressesInWorkingSet+0x2fb
    a5f59c78 8202d08a d262239f 86eda928 c0000005 nt!MmCleanProcessAddressSpace+0x13a
    a5f59cdc 82003331 00000000 842e95e0 842e9601 nt!PspExitThread+0x65d
    a5f59cf4 81e60130 86eda928 a5f59d20 a5f59d2c nt!PsExitSpecialApc+0x22
    a5f59d4c 81e75b26 00000001 00000000 a5f59d64 nt!KiDeliverApc+0x1dc
    a5f59d4c 77029a94 00000001 00000000 a5f59d64 nt!KiServiceExit+0x56
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    02e3ecd4 00000000 00000000 00000000 00000000 0x77029a94


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!MiDeleteAddressesInWorkingSet+2fb
    81ebf7a4 6a00            push    0

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!MiDeleteAddressesInWorkingSet+2fb

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4812bd71

    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  0x1a_3452_nt!MiDeleteAddressesInWorkingSet+2fb

    BUCKET_ID:  0x1a_3452_nt!MiDeleteAddressesInWorkingSet+2fb

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

    Otra cosa, cuando empezo con los errores me empezo a mostrar que tenia una RAM de 4GB, siendo que yo tengo 2.

    Agradeceria su ayuda

    Rodrigo



    jueves, 25 de septiembre de 2008 2:21

Respuestas

  • ¿tienes mas dump para poder analizar?.

     

    El casque que nos has dejado ha sido en el proceso EDICT.EXE el cual pertenece al software de le Enciclopedia Encarta. Pero por otra parte comentas lo de la memoria, y eso es preocupante ya que un error hardware en ese sentido explicaria casques totalmente diferentes en procesos que no tienen nada que ver y de ahí mi comentario de si tenias mas casques.

     

    Comentame, ya que puede ser un problema serio de hardware.

     

    Un saludo,

    jueves, 25 de septiembre de 2008 5:30