Diagnose minidump.dmp file

By dtooth71
Sep 18, 2008
  1. Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Users\name\Desktop\Mini091508-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols
    Executable search path is:
    Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (2 procs) Free x64
    Product: Server, suite: TerminalServer SingleUserTS StorageServer
    Built by: 3790.srv03_sp1_qfe.070321-2340
    Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d7120
    Debug session time: Mon Sep 15 10:28:27.342 2008 (GMT-4)
    System Uptime: 50 days 23:14:10.203
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * *
    * Bugcheck Analysis *
    * *

    Use !analyze -v to get detailed debugging information.

    BugCheck 9C, {5, fffffadfc8a81240, b2000018, 2000e0f}

    Probably caused by : tcpip.sys ( tcpip!ProcessSynTcbs+c2 )

    Followup: MachineOwner

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

    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
    SAL returned an error for SAL_GET_STATEINFO while processing MCA.
    SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
    4 - MCA_FATAL
    FW reported a fatal MCA.
    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.
    SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
    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
    Arg1: 0000000000000005
    Arg2: fffffadfc8a81240
    Arg3: 00000000b2000018
    Arg4: 0000000002000e0f

    Debugging Details:

    BUGCHECK_STR: 0x9C_GenuineIntel





    LAST_CONTROL_TRANSFER: from fffff8000080ef6c to fffff8000104e890

    fffff800`00123b88 fffff800`0080ef6c : 00000000`0000009c 00000000`00000001 fffff800`00123bc0 00000000`b2000000 : nt!KeBugCheckEx
    fffff800`00123b90 fffff800`0104db77 : 00000000`00000000 00000000`00000000 00000000`000000fa fffff800`00123ef0 : hal!HalHandleMcheck+0x12c
    fffff800`00123cf0 fffff800`0104d9b5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x77
    fffff800`00123e70 fffffadf`c72ff6de : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0xf5
    fffff800`001173d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!ProcessSynTcbs+0xc2


    fffffadf`c72ff6de 498b2c0e mov rbp,qword ptr [r14+rcx]


    SYMBOL_NAME: tcpip!ProcessSynTcbs+c2

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: tcpip

    IMAGE_NAME: tcpip.sys


    FAILURE_BUCKET_ID: X64_0x9C_GenuineIntel_tcpip!ProcessSynTcbs+c2

    BUCKET_ID: X64_0x9C_GenuineIntel_tcpip!ProcessSynTcbs+c2

    Followup: MachineOwner
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,984   +72

    As per auhma.org -- 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).

    Try the following:

    If you have overclocked I suggest you ease back to see if that brings you stability.

    Run memtest on your RAM for a minimum of 7 passes. www.memtest.org

    Check your airflow. See if all your fans are working: case, cpu, video card.
  3. dtooth71

    dtooth71 TS Rookie Topic Starter

    if this is the case, then I should just allow Dell to replace the board, CPU, and memory. that will elliminate those three hardware peices. there is no overclocking and the DSET test I ran yesterday noted that the system temperature and the fans were running just fine.

    I understnad the; 0x0000009C: MACHINE_CHECK_EXCEPTION, however it is pointing to the tcpip.sys. this I do not understand, can you explain?
  4. Route44

    Route44 TechSpot Ambassador Posts: 11,984   +72

    it has to do with your internet protocol and it is a core Windows driver. Often Window core drivers are too general to help.

    We don't know which is causing you the crashes so to have Dell replace all three at this juncture is a move that I believe they will highly unlikely do. How old is your system?

    First check your RAM with memtest. It is free and a good test.

    Read this link: https://www.techspot.com/vb/topic51365.html
Topic Status:
Not open for further replies.

Similar Topics

Add your comment to this article

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