TechSpot

Please indentify the fault from attached minidump result

By APPI_0
Jul 12, 2006
  1. Hi Everybody,
    I'm attaching a minidump result after debugging it using windbg. i want to know what's wrong and where is the fault.I appreciate if you could explain me what is wrong and how you find it from log.I appreciate your help.Awaiting fro your quick reply.

    regards
    REDDY
     
  2. fastco

    fastco TS Booster Posts: 1,122

    Could you zip up the actual minidump and attach it? Thanks..
     
  3. APPI_0

    APPI_0 TS Rookie Topic Starter

    minidump you requested

    Hi, thanks for the reply please find the minidump you requested.

    regards
    REDDY
     
  4. Tedster

    Tedster Techspot old timer..... Posts: 6,000   +15

    Microsoft (R) Windows Debugger Version 6.6.0003.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Documents and Settings\Theodore DiVito\Desktop\Mini071206-01\Mini071206-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
    Debug session time: Wed Jul 12 04:13:23.953 2006 (GMT-5)
    System Uptime: 0 days 0:36:49.555
    Loading Kernel Symbols
    .........................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .............
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9C, {0, 8054d370, cc0003ff, 20040135}

    Probably caused by : ntoskrnl.exe ( nt!KdPitchDebugger+ef4 )

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

    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: 8054d370
    Arg3: cc0003ff
    Arg4: 20040135

    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
    ----------------------------------------------------------------
    1100110000000000000000111111111100100000000001000000000100110101


    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.

    OVER - Error Overflow
    Indicates that a machine check error occurred while the results of a
    previous error were still in the error-reporting register bank (that
    is, the VAL bit was already set in the IA32_MCi_STATUS register).
    the processor sets the OVER flag and software is responsible for
    clearing it. Enabled errors are written over disabled errors, and
    uncorrected errors are written over corrected errors. Uncorrected
    errors are not written over previous valid uncorrected errors.

    MISCV - IA32_MCi_MISC Register Valid
    Indicates that the IA32_MCi_MISC register contains additional
    information regarding the error. When clear, this flag indicates
    that the IA32_MCi_MISC register is either not implemented or does
    not contain additional information regarding the error.

    ADDRV - IA32_MCi_ADDR register valid
    Indicates that the IA32_MCi_ADDR register contains the address where
    the error occurred.

    MEMHIRERR - Memory Hierarchy Error {TT}CACHE{LL}_{RRRR}_ERR
    These errors match the format 0000 0001 RRRR TTLL



    Concatenated Error Code:
    --------------------------
    _VAL_OVER_MISCV_ADDRV_MEMHIRERR_35

    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_IA32_GenuineIntel

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    LAST_CONTROL_TRANSFER: from 806f18df to 8053331e

    SYMBOL_ON_RAW_STACK: 1

    STACK_TEXT:
    8054d348 806f18df 0000009c 00000000 8054d370 nt!KeBugCheckEx+0x1b
    8054d474 806ecc2e 80042000 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd
    8054d474 00000000 80042000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x46


    STACK_COMMAND: dds @$csp ; kb

    FOLLOWUP_IP:
    nt!KdPitchDebugger+ef4
    8054d370 0200 add al,[eax]

    FAULTING_SOURCE_CODE:


    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: nt!KdPitchDebugger+ef4

    MODULE_NAME: nt

    IMAGE_NAME: ntoskrnl.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9

    FAILURE_BUCKET_ID: 0x9C_IA32_GenuineIntel_nt!KdPitchDebugger+ef4

    BUCKET_ID: 0x9C_IA32_GenuineIntel_nt!KdPitchDebugger+ef4

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

    probably faulting memory. Run memtest 86+ booted from a floppy.
     
  5. howard_hopkinso

    howard_hopkinso TS Rookie Posts: 24,177   +19

    Your bugcheck of 9C means the following.

    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).

    As you can see from the above, you have some kind of hardware failure.

    You will need to Diagnose which hardware is the culprit. This can be a long and difficult process.

    You should start by disconnecting anything not required to run your system.

    Just leave the mobo/cpu/psu/1 stick of ram/hdd/graphics card.

    If you still get the same crashes, then obviously the problem lies with one of those components.

    Then, you will need to start swapping out parts in order to narrow the culprit down. This i where it can be expensive, if you don`t have access to fresh parts.

    As Tedster said, test your ram with Memtest86+.

    Also make sure your system isn`t overclocked at all and check for any possible overheating.

    Check your mobo for bulging or leaking capacitors. See HERE for further info.

    Good luck.

    Regards Howard :)
     
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...