Hirdetés

  2. Fórumok
  3. OS, alkalmazások
  4. Kék halál (BSOD)

Új hozzászólás Aktív témák

  • #3986 Colos1 őstag Colos1 #3985
    Új Válasz #3986
    Új hozzászólás
    Összes hozzászólása itt Válaszok az összes hozzászólására itt Válaszok erre a hozzászólásra
    Privát üzenet küldése

    Colos1

    őstag

    válasz Colos1 #3985 üzenetére

    Itt egy rendes WinDBG elemzés, végre sikerült a qrva Symbol path -ot beállítanom. :)

    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 10240 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 10240.16515.amd64fre.th1.150916-2039
    Machine Name:
    Kernel base = 0xfffff802`ce60b000 PsLoadedModuleList = 0xfffff802`ce930010
    Debug session time: Mon Oct 12 19:18:24.539 2015 (UTC + 2:00)
    System Uptime: 0 days 2:50:07.224
    Loading Kernel Symbols

    Loading User Symbols
    Loading unloaded module list
    .............
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1E, {ffffffffc0000005, fffff8000673aef5, 0, ffffffffffffffff}

    *** WARNING: Unable to verify timestamp for e1i63x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1i63x64.sys
    Probably caused by : e1i63x64.sys ( e1i63x64+14966 )

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

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

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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: fffff8000673aef5, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception

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

    DUMP_FILE_ATTRIBUTES: 0x8
    Kernel Generated Triage Dump

    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPagedPoolEnd
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
    ffffffffffffffff

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - A 0x%p c men tal lhat utas t s a 0x%p mem riac mre hivatkozott. A mem riater leten nem v gezhet

    FAULTING_IP:
    ndis!ndisMTopReceiveNetBufferLists+21e15
    fffff800`0673aef5 488b4718 mov rax,qword ptr [rdi+18h]

    EXCEPTION_PARAMETER2: ffffffffffffffff
    BUGCHECK_STR: 0x1E_c0000005_R
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    PROCESS_NAME: aida64.exe
    CURRENT_IRQL: 2
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    DPC_STACK_BASE: FFFFF802CF931FB0
    TRAP_FRAME: ffffe000fe912460 -- (.trap 0xffffe000fe912460)
    Unable to read trap frame at ffffe000`fe912460
    LAST_CONTROL_TRANSFER: from fffff802ce7fc9d6 to fffff802ce759240
    STACK_TEXT:
    fffff802`cf9303d8 fffff802`ce7fc9d6 : 00000000`0000001e ffffffff`c0000005 fffff800`0673aef5 00000000`00000000 : nt!KeBugCheckEx
    fffff802`cf9303e0 fffff802`ce75f27d : fffff802`ce982000 fffff802`ce60b000 0004c41c`00852000 00000000`00000000 : nt!KiFatalExceptionHandler+0x22
    fffff802`cf930420 fffff802`ce67f050 : 00000000`00000000 fffff802`ce985a00 fffff802`cf931378 00000000`00000000 : nt!RtlpExecuteHandlerForException+0xd
    fffff802`cf930450 fffff802`ce67bc78 : fffff802`cf931378 fffff802`cf931090 fffff802`cf931378 00000000`00000001 : nt!RtlDispatchException+0x4e8
    fffff802`cf930b60 fffff802`ce763c82 : 00000000`00000000 fffff800`08352904 ffffe000`fe912460 00000000`00000000 : nt!KiDispatchException+0x144
    fffff802`cf931240 fffff802`ce76217e : 00000000`00000000 ffffe000`00000001 ffffe000`fe013560 fffff802`cf931670 : nt!KiExceptionDispatch+0xc2
    fffff802`cf931420 fffff800`0673aef5 : 00000000`00000001 fffff800`06cd501f 00000000`00000001 00000000`00000801 : nt!KiGeneralProtectionFault+0xfe
    fffff802`cf9315b0 fffff800`0671cc33 : ffffe000`fc0aa1a0 ffffe000`00000000 fffff800`067190e0 00000000`00000000 : ndis!ndisMTopReceiveNetBufferLists+0x21e15
    fffff802`cf9316b0 fffff800`06712929 : ffffe000`fc0aa102 fffff802`cf931800 00000000`00000801 00000000`00000000 : ndis!ndisCallReceiveHandler+0x43
    fffff802`cf931700 fffff800`0a5d4966 : 00000000`00000000 00000000`00000000 ffffe000`ff07de80 ffffe000`ff1edfa0 : ndis!NdisMIndicateReceiveNetBufferLists+0x479
    fffff802`cf931870 00000000`00000000 : 00000000`00000000 ffffe000`ff07de80 ffffe000`ff1edfa0 00000000`00000801 : e1i63x64+0x14966

    STACK_COMMAND: kb
    FOLLOWUP_IP:
    e1i63x64+14966
    fffff800`0a5d4966 ?? ???
    SYMBOL_STACK_INDEX: a
    SYMBOL_NAME: e1i63x64+14966
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: e1i63x64
    IMAGE_NAME: e1i63x64.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 55146b19
    FAILURE_BUCKET_ID: 0x1E_c0000005_R_e1i63x64+14966
    BUCKET_ID: 0x1E_c0000005_R_e1i63x64+14966
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_e1i63x64+14966
    FAILURE_ID_HASH: {63ac5d0e-3281-5fba-7212-ad9a85d4e50b}
    Followup: MachineOwner
    ---------

Új hozzászólás Aktív témák