Help understanding .dmp info after BSOD

Discussion in 'Windows 8' started by J3000, Oct 29, 2015.

  1. J3000

    J3000 MDL Novice

    Apr 10, 2011
    6
    0
    0
    Hi all,

    I hope Im posting this in the right section. I would need help to understand why my laptop crashed. I read the dmp file online and the data is:

    Crash Dump Analysis provided by OSR Open Systems Resources, Inc.
    Online Crash Dump Analysis Service
    See osronline.com for more information
    Windows 8 Kernel Version 10240 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 10240.16545.amd64fre.th1.150930-1750
    Machine Name:
    Kernel base = 0xfffff801`76807000 PsLoadedModuleList = 0xfffff801`76b2c070
    Debug session time: Thu Oct 29 02:27:16.600 2015 (UTC - 4:00)
    System Uptime: 0 days 9:16:46.309
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    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.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8007a9b3629, The address that the exception occurred at
    Arg3: ffffd0013ab57158, Exception Record Address
    Arg4: ffffd0013ab56970, Context Record Address

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

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    FAULTING_IP:
    BthA2DP!Avdtp_impl::ReleaseRemoveLock+9
    fffff800`7a9b3629 488b8978050000 mov rcx,qword ptr [rcx+578h]

    EXCEPTION_RECORD: ffffd0013ab57158 -- (.exr 0xffffd0013ab57158)
    ExceptionAddress: fffff8007a9b3629 (BthA2DP!Avdtp_impl::ReleaseRemoveLock+0x0000000000000009)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 0000000000000578
    Attempt to read from address 0000000000000578

    CONTEXT: ffffd0013ab56970 -- (.cxr 0xffffd0013ab56970)
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffff80176be0200 rsi=ffffe000d4245190 rdi=ffffe000e12562f0
    rip=fffff8007a9b3629 rsp=ffffd0013ab57390 rbp=ffffe000e12562f0
    r8=fffff80176be0200 r9=0000000000000000 r10=000000000000000f
    r11=fffff80176807000 r12=0000000000000000 r13=0000000000000008
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
    BthA2DP!Avdtp_impl::ReleaseRemoveLock+0x9:
    fffff800`7a9b3629 488b8978050000 mov rcx,qword ptr [rcx+578h] ds:002b:00000000`00000578=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: 0000000000000578

    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
    0000000000000578

    FOLLOWUP_IP:
    BthA2DP!Avdtp_impl::ReleaseRemoveLock+9
    fffff800`7a9b3629 488b8978050000 mov rcx,qword ptr [rcx+578h]

    BUGCHECK_STR: AV

    EXCEPTION_STR: 0x0

    LAST_CONTROL_TRANSFER: from fffff8007a9b30b8 to fffff8007a9b3629

    STACK_TEXT:
    ffffd001`3ab57390 fffff800`7a9b30b8 : 00000000`00000004 ffffe000`e12562f0 00000000`00000008 ffffd001`3ab57540 : BthA2DP!Avdtp_impl::ReleaseRemoveLock+0x9
    ffffd001`3ab573d0 fffff801`7692bf32 : ffffe000`e051bb00 ffffd001`3ab57550 00000000`00000004 ffffd001`3ab57558 : BthA2DP!Avdtp_impl::CallBTHD_Completion+0x78
    ffffd001`3ab57400 fffff801`7685399d : ffffe000`e12562f0 00000000`00000000 00000000`00000000 ffffe000`e125688b : nt!IopUnloadSafeCompletion+0x52
    ffffd001`3ab57430 fffff800`79c016f1 : ffffe000`e12562f0 00000000`00000008 ffffe000`d8edda80 00000000`00000000 : nt!IopfCompleteRequest+0x20d
    ffffd001`3ab574f0 fffff800`79c17f0b : ffffd001`3ab575b0 ffffd001`3ab575c0 ffffe000`d8edda80 fffff800`79c187f1 : bthport!BthCompleteRequestEx+0xa5
    ffffd001`3ab57540 fffff800`79c299f0 : ffffe000`e45c5010 00000000`00000000 00000000`00000000 ffffd001`3ab57630 : bthport!HCI_CompleteBrbIrps+0x5f
    ffffd001`3ab57580 fffff800`79c1a6f5 : ffffe000`d8edda80 ffffd001`3ab57600 ffffe000`e1047990 00000000`0000ffff : bthport!HCI_CxnEnterActiveModeCallback+0x190
    ffffd001`3ab57600 fffff800`79c38915 : ffffe000`d8ee2010 ffffe000`d4918600 00000000`00000014 00000000`00000000 : bthport!HCI_DoCmdCompletion+0x4fd
    ffffd001`3ab57720 fffff800`79cb567c : 00000000`00000000 ffffe000`d8ee2010 00000000`00000006 00000000`00000008 : bthport!HCI_ProcessAsynchronousEvent+0x8d
    ffffd001`3ab57770 fffff800`79cbc547 : ffffe000`e131a9c0 ffffd001`3ab578f0 ffffe000`d8ee2010 fffff800`79c97568 : bthport!HCI_ProcessEvent+0x68
    ffffd001`3ab577b0 fffff800`79c50715 : ffffe000`e131a9c0 ffffe000`d8ee2010 ffffe000`e131aa18 ffffe000`00000000 : bthport!HCI_ProcessBip+0x63
    ffffd001`3ab577f0 fffff801`768ed558 : ffffe000`d3d6b780 ffffe000`d8ebc800 ffffe000`d3d6b780 ffffd001`3776dbc0 : bthport!HCI_ThreadFunction+0x6a5
    ffffd001`3ab57c00 fffff801`7695a3c6 : ffffd001`37761180 ffffe000`d8ebc800 ffffd001`3776dbc0 480e688d`41d38b41 : nt!PspSystemThreadStartup+0x58
    ffffd001`3ab57c60 00000000`00000000 : ffffd001`3ab58000 ffffd001`3ab52000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: BthA2DP!Avdtp_impl::ReleaseRemoveLock+9

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: BthA2DP

    IMAGE_NAME: BthA2DP.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 559f3a4f

    STACK_COMMAND: .cxr 0xffffd0013ab56970 ; kb

    FAILURE_BUCKET_ID: X64_AV_BthA2DP!Avdtp_impl::ReleaseRemoveLock+9

    BUCKET_ID: X64_AV_BthA2DP!Avdtp_impl::ReleaseRemoveLock+9

    Followup: MachineOwner
     
  2. Aemsa

    Aemsa MDL Member

    Feb 17, 2014
    116
    24
    10
    IMAGE_NAME: BthA2DP.sys

    Bluetooth module is causing the bsod, see if vendor has newer drivers?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. pisthai

    pisthai Imperfect Human

    Jul 29, 2009
    6,638
    1,921
    210
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...