1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

0x0000009c [Dump Data]

Discussion in 'Windows XP' started by cliffro, 2006/06/14.

  1. 2006/06/14
    cliffro

    cliffro Inactive Thread Starter

    Joined:
    2006/06/14
    Messages:
    1
    Likes Received:
    0
    I am not very familiar with running so I hope I did it correctly. If I read this and understood it, it seems to be telling me my memory is causing my computer to crash. Would you say this is correct?


    Loading Dump File [C:\WINDOWS\Minidump\Mini061206-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 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
    Debug session time: Mon Jun 12 02:15:44.565 2006 (GMT-5)
    System Uptime: 4 days 19:45:26.235
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** 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, 805535f0, be000300, 20020135}

    Probably caused by : memory_corruption ( nt!MiRemoveUnusedSegments+637 )

    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: 805535f0
    Arg3: be000300
    Arg4: 20020135

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


    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.

    EN - Error Enabled
    Indicates that the error was enabled by the associated EEj bit of the
    IA32_MCi_CTL register.

    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.

    PCC - Processor Context Corrupt
    Indicates that the state of the processor might have been corrupted
    by the error condition detected and that reliable restarting of the
    processor may not be possible.

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



    Concatenated Error Code:
    --------------------------
    _VAL_UC_EN_MISCV_ADDRV_PCC_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 80702bf7 to 805372b2

    STACK_TEXT:
    805535c8 80702bf7 0000009c 00000000 805535f0 nt!MiRemoveUnusedSegments+0x637
    805536f4 806fdc52 80042000 00000000 00000000 hal!_allshr+0x9
    00000000 00000000 00000000 00000000 00000000 hal!HalpWriteCmosTime+0xce


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiRemoveUnusedSegments+637
    805372b2 5d pop ebp

    FAULTING_SOURCE_CODE:


    SYMBOL_STACK_INDEX: 0

    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: nt!MiRemoveUnusedSegments+637

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 433b2f11

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0x9C_IA32_GenuineIntel_nt!MiRemoveUnusedSegments+637

    BUCKET_ID: 0x9C_IA32_GenuineIntel_nt!MiRemoveUnusedSegments+637

    Followup: MachineOwner
     
  2. 2006/06/15
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    cliffro - Welcome to the Board :)

    I am no expert on analysing dump logs and yours is a little different from those I have seen in the past.

    We have an expert on these logs so please be patient until he takes a look - I have edited your thread to indicate dump data.

    In the meantime I suggest you test out the memory using either Windows Memory Diagnostic Tool or Memtest and post the results.
     

  3. to hide this advert.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.