Bluescreen: MACHINE_CHECK_EXCEPTION

Dieses Thema Bluescreen: MACHINE_CHECK_EXCEPTION im Forum "Windows XP Forum" wurde erstellt von tante_horst, 24. Dez. 2008.

Thema: Bluescreen: MACHINE_CHECK_EXCEPTION Hallo.. habe seit kurzem ständig Bluescreens auf meinem Zweitrechner. Ich habe mal mit dem Windows Debugging Tool...

  1. Hallo..

    habe seit kurzem ständig Bluescreens auf meinem Zweitrechner. Ich habe mal mit dem Windows Debugging Tool den Crashdump ausgelsen. Ich würde gerne mal Eure Meinung und Einschätzung dazu hören. Ich habe auf diversen Seiten gelesen, dass der Bluescreen mit der Meldung MACHINE_CHECK_EXCEPTION viele Ursachen haben kann ( Überhitzung, defekter BUS-Treiber, etc.). Wenn ich das ausgelesene Dumpfile richtig verstehe wird die Datei ntoskernel.exe dafür verantwortlich gemacht. Hat einer eventuell ne Idee die Problemursache weiter einzugrenzen?

    Schon mal vielen Dank!

    Loading Dump File [D:\Dokumente und Einstellungen\Administrator\Desktop\Mini122408-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: M:\Programme\Debugging Tools for Windows (x86)\Symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
    Debug session time: Wed Dec 24 15:05:47.843 2008 (GMT+1)
    System Uptime: 0 days 0:09:22.438
    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, {4, 80545ff0, b2000000, 70f0f}

    Probably caused by : ntoskrnl.exe ( nt!FsRtlRemoveMcbEntryPrivate+68 )

    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: 00000004
    Arg2: 80545ff0
    Arg3: b2000000
    Arg4: 00070f0f

    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:

    - Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors
    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
    ----------------------------------------------------------------
    1011001000000000000000000000000000000000000001110000111100001111


    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.

    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_UC_EN_PCC_BUSCONNERR_30F

    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_AuthenticAMD

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    PROCESS_NAME: Idle

    LAST_CONTROL_TRANSFER: from 806d38df to 804f8925

    STACK_TEXT:
    80545fc8 806d38df 0000009c 00000004 80545ff0 nt!FsRtlRemoveMcbEntryPrivate+0x68
    80545fc8 00000000 0000009c 00000004 80545ff0 hal!HalpGetFeatureBits+0x75


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!FsRtlRemoveMcbEntryPrivate+68
    804f8925 5d pop ebp

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!FsRtlRemoveMcbEntryPrivate+68

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntoskrnl.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107b0c

    FAILURE_BUCKET_ID: 0x9C_AuthenticAMD_nt!FsRtlRemoveMcbEntryPrivate+68

    BUCKET_ID: 0x9C_AuthenticAMD_nt!FsRtlRemoveMcbEntryPrivate+68

    Followup: MachineOwner
    ---------
     
Die Seite wird geladen...

Bluescreen: MACHINE_CHECK_EXCEPTION - Ähnliche Themen

Forum Datum
Bluescreen Crash SYSTEM_SERVICE_EXCEPTION 0x0000003b Ntfs.sys Windows 7 Forum 6. Dez. 2015
Dauerhaft Bluescreens beim Hochfahren des Pcs Windows 8 Forum 18. Feb. 2015
Bluescreen bei Installation Windows 8 Forum 18. Feb. 2015
Bluescreen DRIVER POWER STATE FAILURE Windows 7 Forum 30. Dez. 2014
Bluescreen bei Windows 7 Windows 7 Forum 17. Dez. 2014