minidump.TXT

Version 1

    Laptop(Pentium D and Vista Home Basic) gets blue screen every time  on its boot. Can somebody help explain the output of win debug tool about the mini dump file.  Thanks!

     

    ------------------------------------------------------------------------------

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86

    Copyright (c) Microsoft Corporation. All rights reserved.

     

     

    Loading Dump File [C:\Windows\Minidump\Mini090814-02.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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 6002.18881.x86fre.vistasp2_gdr.130707-1535

    Machine Name:

    Kernel base = 0x82a14000 PsLoadedModuleList = 0x82b2bc70

    Debug session time: Mon Sep  8 12:13:27.864 2014 (UTC + 8:00)

    System Uptime: 0 days 0:00:06.848

    Loading Kernel Symbols

    ...............................................

    Loading User Symbols

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

     

    Use !analyze -v to get detailed debugging information.

     

    BugCheck 9C, {0, 855b9120, f2000040, 800}

     

    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

     

    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: 855b9120

    Arg3: f2000040

    Arg4: 00000800

     

    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

       ----------------------------------------------------------------

       1111001000000000000000000100000000000000000000000000100000000000

     

     

    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.

     

    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.

     

    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.

     

    BUSCONNERR - Bus and Interconnect Error   BUS{LL}_{PP}_{RRRR}_{II}_{T}_err

            These errors match the format 0000 1PPT RRRR IILL

     

     

     

       Concatenated Error Code:

       --------------------------

       _VAL_OVER_UC_EN_PCC_BUSCONNERR_0

     

       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:  2

     

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

     

    PROCESS_NAME:  System

     

    CURRENT_IRQL:  0

     

    LAST_CONTROL_TRANSFER:  from 82dd5021 to 82ae19bd

     

    STACK_TEXT: 

    82b06fbc 82dd5021 0000009c 00000000 855b9120 nt!KeBugCheckEx+0x1e

    82b06ff4 82dd099f 80158000 00000000 00000000 hal!HalpMcaExceptionHandler+0x149

    82b06ff4 00000000 80158000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77

     

     

    STACK_COMMAND:  kb

     

    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

     

    FOLLOWUP_NAME:  MachineOwner

     

    MODULE_NAME: Unknown_Module

     

    IMAGE_NAME:  Unknown_Image

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

     

    FAILURE_BUCKET_ID:  0x9C_GenuineIntel_ANALYSIS_INCONCLUSIVE

     

    BUCKET_ID:  0x9C_GenuineIntel_ANALYSIS_INCONCLUSIVE

     

    Followup: MachineOwner

    ---------