locked
Pantallazos azules, No se analizar los archivos dmp. RRS feed

  • Pregunta

  • Hace un mes me compre ordenador, y pronto empezaron a aparecer pantallazos azules, no se que es lo que falla, si son drivers o si es el hardware, el caso es que salta igual si estoy jugando a juegos que exigen bastante al ordenador, como si simplemente estoy viendo alguna serie en internet. he probado a descargar el programa, WinDbg, pero no se cual es la causa, ademas que no siempre dicen lo mismo los pantallazos; 

    - SYSTEM SERVICE EXCEPTION

    -IRQL NOT LESS OR EQUAL

    -BAD POOL CALLER

    -PAGE FAULT IN NONPAGED AREA

    Os dejo un par de ellos analizados con el Windbg, No se mucho de esto, y me estoy volviendo loco de investigar. 

    Gracias por la atención. 

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

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {100fda9d0, 2, 1, fffff8000328a2c3}

    Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+2b3 )

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

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: 0000000100fda9d0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff8000328a2c3, address which referenced memory

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


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bf100
    GetUlongFromAddress: unable to read from fffff800034bf1c0
     0000000100fda9d0 Nonpaged pool

    CURRENT_IRQL:  2

    FAULTING_IP: 
    nt!KiTimerWaitTest+2b3
    fffff800`0328a2c3 48894108        mov     qword ptr [rcx+8],rax

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  System

    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

    DPC_STACK_BASE:  FFFFF80004816FB0

    TRAP_FRAME:  fffff80004810290 -- (.trap 0xfffff80004810290)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff88002fda948 rbx=0000000000000000 rcx=0000000100fda9c8
    rdx=fffff88002fda948 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8000328a2c3 rsp=fffff80004810420 rbp=0000000100fda9c8
     r8=fffff80003404001  r9=0000000000000003 r10=000000000000008c
    r11=fffffa8009874030 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe cy
    nt!KiTimerWaitTest+0x2b3:
    fffff800`0328a2c3 48894108        mov     qword ptr [rcx+8],rax ds:00000001`00fda9d0=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff800032811e9 to fffff80003281c40

    STACK_TEXT:  
    fffff800`04810148 fffff800`032811e9 : 00000000`0000000a 00000001`00fda9d0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff800`04810150 fffff800`0327fe60 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`02fda950 : nt!KiBugCheckDispatch+0x69
    fffff800`04810290 fffff800`0328a2c3 : fffffa80`08638000 fffffa80`08638000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
    fffff800`04810420 fffff800`0328cfad : fffff880`02fda948 00000000`00000000 00000000`00000001 fffff800`04810750 : nt!KiTimerWaitTest+0x2b3
    fffff800`048104a0 fffff800`0328ceee : 0000000f`f3ac0f68 fffff800`04810b18 00000000`0006b38c fffff800`03405408 : nt!KiProcessExpiredTimerList+0x6d
    fffff800`04810af0 fffff800`0328ccd7 : 00000006`1b4351c2 00000006`0006b38c 00000006`1b435124 00000000`0000008c : nt!KiTimerExpiration+0x1be
    fffff800`04810b90 fffff800`0327994a : fffff800`03401e80 fffff800`0340fcc0 00000000`00000000 fffff880`04998b24 : nt!KiRetireDpcList+0x277
    fffff800`04810c40 00000000`00000000 : fffff800`04811000 fffff800`0480b000 fffff800`04810c00 00000000`00000000 : nt!KiIdleLoop+0x5a


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    nt!KiTimerWaitTest+2b3
    fffff800`0328a2c3 48894108        mov     qword ptr [rcx+8],rax

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  nt!KiTimerWaitTest+2b3

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  5625815c

    IMAGE_VERSION:  6.1.7601.19045

    FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+2b3

    BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+2b3

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_0xa_nt!kitimerwaittest+2b3

    FAILURE_ID_HASH:  {4252e690-1bfd-086c-e216-7d9e8df452b8}

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

     Y este es otro de los muchos que saltan:

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

    Use !analyze -v to get detailed debugging information.

    BugCheck C2, {7, 109b, c05000b, fffffa80096030c0}

    GetPointerFromAddress: unable to read from fffff800034cf100
    GetUlongFromAddress: unable to read from fffff800034cf1c0
    Probably caused by : Npfs.SYS ( Npfs!NpRemoveDataQueueEntry+a5 )

    Followup: MachineOwner

    ---------

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

    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 0000000000000007, Attempt to free pool which was already freed
    Arg2: 000000000000109b, (reserved)
    Arg3: 000000000c05000b, Memory contents of the pool block
    Arg4: fffffa80096030c0, Address of the block of pool being deallocated

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


    POOL_ADDRESS:  fffffa80096030c0 Nonpaged pool

    FREED_POOL_TAG:  NpFr

    BUGCHECK_STR:  0xc2_7_NpFr

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  chrome.exe

    CURRENT_IRQL:  0

    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

    LAST_CONTROL_TRANSFER:  from fffff800033c8bf9 to fffff80003291c40

    STACK_TEXT:  
    fffff880`060cf6c8 fffff800`033c8bf9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`0c05000b : nt!KeBugCheckEx
    fffff880`060cf6d0 fffff880`0183dfbd : fffff880`060cf8e0 00000000`a0000003 fffffa80`067a5010 fffff800`03294b27 : nt!ExFreePool+0xcb1
    fffff880`060cf780 fffff880`01840f9e : fffff880`060cf8f0 00000000`00000001 fffff880`060cf880 fffff8a0`0bd09010 : Npfs!NpRemoveDataQueueEntry+0xa5
    fffff880`060cf7c0 fffff880`01840d32 : fffff880`060cf880 fffff8a0`0bd09060 00000000`00000001 00000000`00000000 : Npfs!NpReadDataQueue+0x20e
    fffff880`060cf830 fffff880`01840ab5 : fffffa80`06b61fb0 fffffa80`094c3ba0 00000000`00000000 fffffa80`06b61ee0 : Npfs!NpCommonRead+0x18e
    fffff880`060cf8b0 fffff800`0359df3b : 00000000`00000000 fffffa80`094c3ba0 00000000`00000000 fffffa80`06b61ee0 : Npfs!NpFsdRead+0x51
    fffff880`060cf910 fffff800`0357d703 : fffffa80`094c3ba0 fffffa80`094c3ba0 fffffa80`094c3ba0 fffff800`03411e80 : nt!IopSynchronousServiceTail+0xfb
    fffff880`060cf980 fffff800`03290ed3 : fffff880`049d0201 00000000`00000d54 00000000`00000001 00000000`0ebaf13c : nt!NtReadFile+0x631
    fffff880`060cfa70 00000000`74bc2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`06c7ec28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74bc2e09


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    Npfs!NpRemoveDataQueueEntry+a5
    fffff880`0183dfbd 4584ed          test    r13b,r13b

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  Npfs!NpRemoveDataQueueEntry+a5

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Npfs

    IMAGE_NAME:  Npfs.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc114

    IMAGE_VERSION:  6.1.7600.16385

    FAILURE_BUCKET_ID:  X64_0xc2_7_NpFr_Npfs!NpRemoveDataQueueEntry+a5

    BUCKET_ID:  X64_0xc2_7_NpFr_Npfs!NpRemoveDataQueueEntry+a5

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_0xc2_7_npfr_npfs!npremovedataqueueentry+a5

    FAILURE_ID_HASH:  {5840d08d-f0bd-1ee8-664c-df826809f997}

    Followup: MachineOwner
    ------

    Si bien esto no sirve para analizarlo, agradeceria que me guieis un poco para dar con la causa.

    Un saludo

    viernes, 20 de noviembre de 2015 18:12