none
Blue Screen Error (Probably caused by : ntkrnlmp.exe) RRS feed

  • Question

  • Dear Microsoft team,

    I get a blue screen error 4 times. In last night, It has been repeated again on my Windows server 2008. I've checked windows updates and those updates has been successfully installed on my Server. Last update installed in the at 2015/07/03. And I change the configuration of Write debugging information. Now it's selected Small memory dump (256 KB).

    You can download the dump file (Please click the "Download the dump file")

    Download: https://onedrive.live.com/?id=33D5ED719C5EA63%21106&cid=033D5ED719C5EA63&group=0&parId=root&authkey=%21ABXMvI58vrrUdwg&o=OneUp

    When I analyze the mini dump file it shown as following information

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

    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041201, The subtype of the bugcheck.
    Arg2: fffff68000bc0000
    Arg3: 000000007f87312b
    Arg4: fffffa8068de6190

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


    BUGCHECK_STR:  0x1a_41201

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT_SERVER

    PROCESS_NAME:  java.exe

    CURRENT_IRQL:  0

    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

    LAST_CONTROL_TRANSFER:  from fffff800018dbdfe to fffff8000187fa40

    STACK_TEXT:  
    fffff880`0b397928 fffff800`018dbdfe : 00000000`0000001a 00000000`00041201 fffff680`00bc0000 00000000`7f87312b : nt!KeBugCheckEx
    fffff880`0b397930 fffff800`0189a234 : 00000000`00000080 fffff680`00ccfff8 00000001`78000000 00000000`00000080 : nt! ?? ::FNODOBFM::`string'+0x13702
    fffff880`0b397970 fffff800`01b7795a : 00000000`00000000 ffffffff`00000000 fffffa80`692ec060 00000000`00000004 : nt!MiCommitExistingVad+0x2c4
    fffff880`0b397a10 fffff800`0187ecd3 : ffffffff`ffffffff fffffa80`68f5d060 fffff880`00000000 00000000`0118f0e8 : nt!NtAllocateVirtualMemory+0x134a
    fffff880`0b397bb0 00000000`77cbdd5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0118f0c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cbdd5a


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+13702
    fffff800`018dbdfe cc              int     3

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+13702

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  5507a73c

    IMAGE_VERSION:  6.1.7601.18798

    FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13702

    BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13702

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_0x1a_41201_nt!_??_::fnodobfm::_string_+13702

    FAILURE_ID_HASH:  {33abc661-1365-aa2c-af0a-1cbd6aa986f2}

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

    Please see the following picture 

    Tuesday, July 21, 2015 3:19 AM