locked
BlueScreen RRS feed

  • Pregunta

  • Me sale pantallazo azul, lo he analizado con Debugging Tools y este es el resultado si alguien me pudiera indicar cual es el problema se lo agradeceria.

    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {0, 2, 0, 86374110}

    Probably caused by : ntkrnlmp.exe ( nt!KiTrap0E+2cf )

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

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

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

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from 829b5700
    Unable to read MiSystemVaType memory at 829950c0
     00000000

    CURRENT_IRQL:  2

    FAULTING_IP:
    +64232faf03c1d7a4
    86374110 8b00            mov     eax,dword ptr [eax]

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    PROCESS_NAME:  rundll32.exe

    TRAP_FRAME:  a89bba20 -- (.trap 0xffffffffa89bba20)
    ErrCode = 00000000
    eax=00000000 ebx=859f34a8 ecx=a89bba90 edx=00000000 esi=00000000 edi=859f348c
    eip=86374110 esp=a89bba94 ebp=859f34c4 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    86374110 8b00            mov     eax,dword ptr [eax]  ds:0023:00000000=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 86374110 to 8288eb7b

    STACK_TEXT: 
    a89bba20 86374110 badb0d00 00000000 a7a73f08 nt!KiTrap0E+0x2cf
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    a89bbb14 82a8290c b0258d80 00000ce0 a89bbb64 0x86374110
    a89bbb3c 82a76e10 b0258d80 00000ce0 8298e2c4 nt!PsCallImageNotifyRoutines+0x62
    a89bbbe8 82a8a9d1 c53cdb70 99b6ac28 a89bbce4 nt!MiMapViewOfImageSection+0x7ac
    a89bbc58 82ab8f28 99b6ac28 a89bbce4 00000000 nt!MiMapViewOfSection+0x22e
    a89bbc88 82a8c45e a0d71e00 99b6ac28 a89bbce4 nt!MmMapViewOfSection+0x2a
    a89bbd04 8288b79a 00000204 ffffffff 000fce5c nt!NtMapViewOfSection+0x204
    a89bbd04 777164f4 00000204 ffffffff 000fce5c nt!KiFastCallEntry+0x12a
    000fd224 00000000 00000000 00000000 00000000 0x777164f4


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!KiTrap0E+2cf
    8288eb7b 833d20fe9a8200  cmp     dword ptr [nt!KiFreezeFlag (829afe20)],0

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!KiTrap0E+2cf

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3f9b

    FAILURE_BUCKET_ID:  0xD1_nt!KiTrap0E+2cf

    BUCKET_ID:  0xD1_nt!KiTrap0E+2cf

    Followup: MachineOwner


    domingo, 24 de octubre de 2010 15:18

Respuestas

  • Revisate si es problema de driver... otras veces el mismo error hace referencia a problemas de hardware: Memoria, disco mal conectado... o la CPU haciendo algun falso positivo... Cualquier duda estamos por aqui...

     

    Saludos

     

    • Marcado como respuesta Ismael Borche martes, 9 de noviembre de 2010 14:55
    domingo, 24 de octubre de 2010 17:17

Todas las respuestas

  • Un error DRIVER_IRQL_NOT_LESS_OR_EQUAL, como su nombre indica, casi siempre está causado por un controlador mal diseñado. ¿Has instalado/actualizado recientemente algún controlador hardware de tu equipo?

    Ejecuta en Windbg

    .trap 0xffffffffa89bba20

    kb

    Y deja la salida del comando por aquí.


    Microsoft MVP Windows Desktop Experience

    http://www.wintecnico.com

    domingo, 24 de octubre de 2010 15:56
  • 0: kd> Kb
    ChildEBP RetAddr  Args to Child             
    a89bba20 86374110 badb0d00 00000000 a7a73f08 nt!KiTrap0E+0x2cf
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    a89bbb14 82a8290c b0258d80 00000ce0 a89bbb64 0x86374110
    a89bbb3c 82a76e10 b0258d80 00000ce0 8298e2c4 nt!PsCallImageNotifyRoutines+0x62
    a89bbbe8 82a8a9d1 c53cdb70 99b6ac28 a89bbce4 nt!MiMapViewOfImageSection+0x7ac
    a89bbc58 82ab8f28 99b6ac28 a89bbce4 00000000 nt!MiMapViewOfSection+0x22e
    a89bbc88 82a8c45e a0d71e00 99b6ac28 a89bbce4 nt!MmMapViewOfSection+0x2a
    a89bbd04 8288b79a 00000204 ffffffff 000fce5c nt!NtMapViewOfSection+0x204
    a89bbd04 777164f4 00000204 ffffffff 000fce5c nt!KiFastCallEntry+0x12a
    000fd224 00000000 00000000 00000000 00000000 0x777164f4
    domingo, 24 de octubre de 2010 16:13
  • 0: kd> .trap 0xffffffffa89bba20
    ErrCode = 00000000
    eax=00000000 ebx=859f34a8 ecx=a89bba90 edx=00000000 esi=00000000 edi=859f348c
    eip=86374110 esp=a89bba94 ebp=859f34c4 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    86374110 8b00            mov     eax,dword ptr [eax]  ds:0023:00000000=????????
    domingo, 24 de octubre de 2010 16:14
  • No se si es esto lo que me pides, no tengo mucha practica en esto.

    Gracias.

    0: kd> kd.trap 0xffffffffa89bba20
    *** WARNING: Unable to verify timestamp for volmgrx.sys
    *** ERROR: Module load completed but symbols could not be loaded for volmgrx.sys
    *** WARNING: Unable to verify timestamp for aliide.sys
    *** ERROR: Module load completed but symbols could not be loaded for aliide.sys
    *** WARNING: Unable to verify timestamp for m5287.sys
    *** ERROR: Module load completed but symbols could not be loaded for m5287.sys
    *** WARNING: Unable to verify timestamp for amdxata.sys
    *** ERROR: Module load completed but symbols could not be loaded for amdxata.sys
    *** WARNING: Unable to verify timestamp for msrpc.sys
    *** ERROR: Module load completed but symbols could not be loaded for msrpc.sys
    *** WARNING: Unable to verify timestamp for Fs_Rec.sys
    *** ERROR: Module load completed but symbols could not be loaded for Fs_Rec.sys
    *** WARNING: Unable to verify timestamp for ksecpkg.sys
    *** ERROR: Module load completed but symbols could not be loaded for ksecpkg.sys
    *** WARNING: Unable to verify timestamp for vmstorfl.sys
    *** ERROR: Module load completed but symbols could not be loaded for vmstorfl.sys
    *** WARNING: Unable to verify timestamp for spldr.sys
    *** ERROR: Module load completed but symbols could not be loaded for spldr.sys
    *** WARNING: Unable to verify timestamp for hotcore3.sys
    *** ERROR: Module load completed but symbols could not be loaded for hotcore3.sys
    *** WARNING: Unable to verify timestamp for fvevol.sys
    *** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
    *** WARNING: Unable to verify timestamp for epfwwfpr.sys
    *** ERROR: Module load completed but symbols could not be loaded for epfwwfpr.sys
    *** WARNING: Unable to verify timestamp for Null.SYS
    *** ERROR: Module load completed but symbols could not be loaded for Null.SYS
    *** WARNING: Unable to verify timestamp for ehdrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for ehdrv.sys
    *** WARNING: Unable to verify timestamp for Msfs.SYS
    *** ERROR: Module load completed but symbols could not be loaded for Msfs.SYS
    *** WARNING: Unable to verify timestamp for intelppm.sys
    *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
    *** WARNING: Unable to verify timestamp for dump_m5287.sys
    *** ERROR: Module load completed but symbols could not be loaded for dump_m5287.sys
    *** WARNING: Unable to verify timestamp for eamon.sys
    *** ERROR: Module load completed but symbols could not be loaded for eamon.sys
    *** WARNING: Unable to verify timestamp for irda.sys
    *** ERROR: Module load completed but symbols could not be loaded for irda.sys
    *** WARNING: Unable to verify timestamp for parvdm.sys
    *** ERROR: Module load completed but symbols could not be loaded for parvdm.sys
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    *** WARNING: Unable to verify timestamp for Rtnicxp.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rtnicxp.sys
    *** WARNING: Unable to verify timestamp for ULILAN32.SYS
    *** ERROR: Module load completed but symbols could not be loaded for ULILAN32.SYS
    *** WARNING: Unable to verify timestamp for drmk.sys
    *** ERROR: Module load completed but symbols could not be loaded for drmk.sys
    *** WARNING: Unable to verify timestamp for ks.sys
    *** ERROR: Module load completed but symbols could not be loaded for ks.sys
    *** WARNING: Unable to verify timestamp for irsir.sys
    *** ERROR: Module load completed but symbols could not be loaded for irsir.sys
    *** WARNING: Unable to verify timestamp for irenum.sys
    *** ERROR: Module load completed but symbols could not be loaded for irenum.sys
    *** WARNING: Unable to verify timestamp for fdc.sys
    *** ERROR: Module load completed but symbols could not be loaded for fdc.sys
    *** WARNING: Unable to verify timestamp for vncmirror.sys
    *** ERROR: Module load completed but symbols could not be loaded for vncmirror.sys
    *** WARNING: Unable to verify timestamp for flpydisk.sys
    *** ERROR: Module load completed but symbols could not be loaded for flpydisk.sys
    *** WARNING: Unable to verify timestamp for WP800IO.sys
    *** ERROR: Module load completed but symbols could not be loaded for WP800IO.sys
    *** WARNING: Unable to verify timestamp for RTKVAC.SYS
    *** ERROR: Module load completed but symbols could not be loaded for RTKVAC.SYS
    *** WARNING: Unable to verify timestamp for TSDDD.dll
    *** ERROR: Module load completed but symbols could not be loaded for TSDDD.dll
    *** WARNING: Unable to verify timestamp for cdd.dll
    *** ERROR: Module load completed but symbols could not be loaded for cdd.dll
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    *** WARNING: Unable to verify timestamp for peauth.sys
    *** ERROR: Module load completed but symbols could not be loaded for peauth.sys
    *** WARNING: Unable to verify timestamp for secdrv.SYS
    *** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
    *** WARNING: Unable to verify timestamp for FsUsbExDisk.SYS
    *** ERROR: Module load completed but symbols could not be loaded for FsUsbExDisk.SYS
    *** WARNING: Unable to verify timestamp for dgderdrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for dgderdrv.sys
    Requested number of stack frames (0xffffffff86374110) is too large! The maximum number is 0xffff.
             ^ Range error in 'kd.trap 0xffffffffa89bba20'

    domingo, 24 de octubre de 2010 16:53
  • Revisate si es problema de driver... otras veces el mismo error hace referencia a problemas de hardware: Memoria, disco mal conectado... o la CPU haciendo algun falso positivo... Cualquier duda estamos por aqui...

     

    Saludos

     

    • Marcado como respuesta Ismael Borche martes, 9 de noviembre de 2010 14:55
    domingo, 24 de octubre de 2010 17:17
  • Hola

    Hay algún avanzo en la solucion de este problema?

    Saludo

    Ismael Borche
    viernes, 5 de noviembre de 2010 17:45