TechSpot

ntkrnlmp.exe related BSOD

By dabookerman
Aug 16, 2006
  1. Hi, before i used to get ati related BSOD, but they seem to be gone now.
    Now im getting new BSODs:

    heres the dump i got today:

    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    *** WARNING: Unable to verify checksum for ntkrnlmp.exe
    Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 3790.srv03_sp1_rtm.050324-1447
    Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011ad0c0
    Debug session time: Wed Aug 16 15:27:20.796 2006 (GMT+1)
    System Uptime: 0 days 4:27:07.759
    *** WARNING: Unable to verify checksum for ntkrnlmp.exe
    Loading Kernel Symbols
    ...........................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .......
    *** WARNING: Unable to verify checksum for hal.dll
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9C, {4, fffff80000123bc0, b2000000, 70f0f}

    Unable to load image AmdK8.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for AmdK8.sys
    *** ERROR: Module load completed but symbols could not be loaded for AmdK8.sys
    Probably caused by : AmdK8.sys ( AmdK8+4081 )



    a few days ago i got this BSOD:

    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    *** WARNING: Unable to verify checksum for ntkrnlmp.exe
    Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 3790.srv03_sp1_rtm.050324-1447
    Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011ad0c0
    Debug session time: Tue Aug 15 12:52:02.984 2006 (GMT+1)
    System Uptime: 0 days 1:36:08.937
    *** WARNING: Unable to verify checksum for ntkrnlmp.exe
    Loading Kernel Symbols
    .........................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *** WARNING: Unable to verify checksum for hal.dll
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9C, {4, fffff80000123bc0, b2000000, 70f0f}

    Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+77 )

    Followup: MachineOwner




    Ive done the Windows Memory Diagnostics Tool test, and there were no errors. So i dont know what to do now, this is starting to happen more and more frequently at the most random times.


    edit: I did an analysis on the crash dump:

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

    MACHINE_CHECK_EXCEPTION (9c)
    A fatal Machine Check Exception has occurred.
    KeBugCheckEx parameters;
    x86 Processors
    If the processor has ONLY MCE feature available (For example Intel
    Pentium), the parameters are:
    1 - Low 32 bits of P5_MC_TYPE MSR
    2 - Address of MCA_EXCEPTION structure
    3 - High 32 bits of P5_MC_ADDR MSR
    4 - Low 32 bits of P5_MC_ADDR MSR
    If the processor also has MCA feature available (For example Intel
    Pentium Pro), the parameters are:
    1 - Bank number
    2 - Address of MCA_EXCEPTION structure
    3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
    4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
    1 - Bugcheck Type
    1 - MCA_ASSERT
    2 - MCA_GET_STATEINFO
    SAL returned an error for SAL_GET_STATEINFO while processing MCA.
    3 - MCA_CLEAR_STATEINFO
    SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
    4 - MCA_FATAL
    FW reported a fatal MCA.
    5 - MCA_NONFATAL
    SAL reported a recoverable MCA and we don't support currently
    support recovery or SAL generated an MCA and then couldn't
    produce an error record.
    0xB - INIT_ASSERT
    0xC - INIT_GET_STATEINFO
    SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
    0xD - INIT_CLEAR_STATEINFO
    SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
    0xE - INIT_FATAL
    Not used.
    2 - Address of log
    3 - Size of log
    4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors
    1 - Bank number
    2 - Address of MCA_EXCEPTION structure
    3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
    4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
    Arguments:
    Arg1: 0000000000000004
    Arg2: fffff80000123bc0
    Arg3: 00000000b2000000
    Arg4: 0000000000070f0f

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


    BUGCHECK_STR: 0x9C_AMD64_AuthenticAMD

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    CURRENT_IRQL: f

    LAST_CONTROL_TRANSFER: from fffff8000080ef6c to fffff800010501d0

    STACK_TEXT:
    fffff800`00123b88 fffff800`0080ef6c : 00000000`0000009c 00000000`00000004 fffff800`00123bc0 00000000`b2000000 : nt!KeBugCheckEx
    fffff800`00123b90 fffff800`0104f4f7 : 00000000`00000000 00000000`00000000 00000000`119cfd6c fffff800`00123ef0 : hal!HalHandleMcheck+0x12c
    fffff800`00123cf0 fffff800`0104f335 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x77
    fffff800`00123e70 fffff800`0081042a : fffff800`01281183 00000000`00000000 fffffadf`e7519190 00000000`119cf50c : nt!KiMcheckAbort+0xf5
    fffffadf`de99dc28 fffff800`01281183 : 00000000`00000000 fffffadf`e7519190 00000000`119cf50c 00000000`00000034 : hal!KeQueryPerformanceCounter+0x2a
    fffffadf`de99dc30 fffff800`0104fce2 : fffffadf`e775da10 00000000`11318c90 fffffadf`e775da10 00000000`00000000 : nt!NtQueryPerformanceCounter+0x81
    fffffadf`de99dc70 00000000`78b842d9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
    00000000`11a0f108 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x78b842d9


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KxMcheckAbort+77
    fffff800`0104f4f7 488d8c2400010000 lea rcx,[rsp+0x100]

    FAULTING_SOURCE_CODE:


    SYMBOL_STACK_INDEX: 2

    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: nt!KxMcheckAbort+77

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 42436123

    FAILURE_BUCKET_ID: X64_0x9C_AMD64_AuthenticAMD_nt!KxMcheckAbort+77

    BUCKET_ID: X64_0x9C_AMD64_AuthenticAMD_nt!KxMcheckAbort+77

    Followup: MachineOwner
    ---------
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...