TechSpot

BSOD / ntoskrnl.exe / BugCheck 9C

By vinaym
Sep 11, 2009
  1. Hi,
    Wonder if anyone can help with the below MiniDump my web server keeps doing. Ive used the Windows System Information to try to locate what IRQ#18 is but no joy.

    Here is the mini dump:
    oading Dump File [C:\adtws01_minidumps\Mini090209-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\WINDOWS\Symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
    Product: Server, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x80800000 PsLoadedModuleList = 0x808af9c8
    Debug session time: Wed Sep 2 10:05:32.302 2009 (GMT+1)
    System Uptime: 8 days 20:07:16.916
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    .....................................................
    Loading User Symbols
    Loading unloaded module list
    ..
    *** WARNING: Unable to verify timestamp for hal.dll
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9C, {0, 808a07a0, a2000000, 84010400}

    Probably caused by : ntoskrnl.exe ( nt!ObpTracePoolTagsBuffer+f0 )

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

    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: 00000000
    Arg2: 808a07a0
    Arg3: a2000000
    Arg4: 84010400

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

    NOTE: This is a hardware error. This error was reported by the CPU
    via Interrupt 18. This analysis will provide more information about
    the specific error. Please contact the manufacturer for additional
    information about this error and troubleshooting assistance.

    This error is documented in the following publication:

    - IA-32 Intel(r) Architecture Software Developer's Manual
    Volume 3: System Programming Guide

    Bit Mask:

    MA Model Specific MCA
    O ID Other Information Error Code Error Code
    VV SDP ___________|____________ _______|_______ _______|______
    AEUECRC| | | |
    LRCNVVC| | | |
    ^^^^^^^| | | |
    6 5 4 3 2 1
    3210987654321098765432109876543210987654321098765432109876543210
    ----------------------------------------------------------------
    1010000111111111111111111111111110000100000000010000010000000000


    VAL - MCi_STATUS register is valid
    Indicates that the information contained within the IA32_MCi_STATUS
    register is valid. When this flag is set, the processor follows the
    rules given for the OVER flag in the IA32_MCi_STATUS register when
    overwriting previously valid entries. The processor sets the VAL
    flag and software is responsible for clearing it.

    UC - Error Uncorrected
    Indicates that the processor did not or was not able to correct the
    error condition. When clear, this flag indicates that the processor
    was able to correct the error condition.

    INTTIMERERR - INTERNAL TIMER ERROR



    Concatenated Error Code:
    --------------------------
    _VAL_UC_INTTIMERERR

    This error code can be reported back to the manufacturer.
    They may be able to provide additional information based upon
    this error. All questions regarding STOP 0x9C should be
    directed to the hardware manufacturer.

    BUGCHECK_STR: 0x9C_GenuineIntel

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from 80a84154 to 8087c440

    STACK_TEXT:
    808a0770 80a84154 0000009c 00000000 808a07a0 nt!ObpTracePoolTagsBuffer+0xf0
    808a08a4 80a7b86f 80042000 00000000 00000000 hal!HalpPCISynchronizeOrionB0+0x10
    00000000 00000000 00000000 00000000 00000000 hal!HalpRealModeStart+0x451


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!ObpTracePoolTagsBuffer+f0
    8087c440 5d pop ebp

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!ObpTracePoolTagsBuffer+f0

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntoskrnl.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 45d6a0af

    FAILURE_BUCKET_ID: 0x9C_GenuineIntel_VRFK_nt!ObpTracePoolTagsBuffer+f0

    BUCKET_ID: 0x9C_GenuineIntel_VRFK_nt!ObpTracePoolTagsBuffer+f0

    Followup: MachineOwner


    ======================================
    Any help would be greatly appreciated.

    Thanks,
    Vinay
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    0x9C errors are very difficult to work with because they can be caused by virtually by any piece of hardware. I have yet to read a minidump that gives a specific cause such as memory, etc., only OS drivers that are too general to be of much help.

    0x0000009C: MACHINE_CHECK_EXCEPTION
    This is a hardware issue: an unrecoverable hardware error has occurred. The parameters have different meanings depending on what type of CPU you have but, while diagnostic, rarely lead to a clear solution. Most commonly it results from overheating, from failed hardware (RAM, CPU, hardware bus, power supply, etc.), or from pushing hardware beyond its capabilities (e.g., overclocking a CPU).

    Questions:

    1. Have you overclocked? If so ease back the timings, etc.

    2. Have you checked for heat issues?

    3. When do your BSODs occur?
     
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...