1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

BSOD error, computer restarts!

Discussion in 'Windows XP' started by vladale, Jun 10, 2007.

Thread Status:
Not open for further replies.
Advertisement
  1. vladale

    vladale Thread Starter

    Joined:
    Jun 10, 2007
    Messages:
    2
    Hi. Before registering I read all similiar threads regarding to my problem. I didn't solved it. So, I decided to open a new one and get help from you guys.

    I bought a new processor, AMD Sempron 2800+, a new Foxconn NF3 motherboard and a 512MB DDR memory. I didn't had problems installing them, but when I started using my new machine on a new Windows my problems appeared.

    My computer keeps restarting, and I don't know why! Computer restarts only when I am trying to encode some video (DVD to Divx or similiar) and I tried to encode with different tools - nah, that doesn't help - it's still restarting.

    I saw that my machine is reporting BSOD with a error: MACHINE_CHECK_EXCEPTION.

    I thought it was a memory but I downloaded memtest and passed 3-4 with no errors. My temperature is 40 C, so processor is not the problem. I have power supply of 400W (bought in 2006) and I didn't had any of problems with it. I am stuck here for 3 weeks and I don't know what to do. Can you help me? Here are my minidumps.
     
  2. vladale

    vladale Thread Starter

    Joined:
    Jun 10, 2007
    Messages:
    2
    Symbol search path is: *** Invalid ***
    ********************************************************************** ******
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ********************************************************************** ******
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
    Debug session time: Sat Jun 9 09:21:39.859 2007 (GMT+2)
    System Uptime: 0 days 0:26:21.456
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...................................................................... ........................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *** WARNING: Unable to verify timestamp for hal.dll
    *** ERROR: Module load completed but symbols could not be loaded for hal.dll
    ********************************************************************** *********
    * *
    * Bugcheck Analysis *
    * *
    ********************************************************************** *********

    Use !analyze -v to get detailed debugging information.

    BugCheck 9C, {2, 80545ff0, f6002000, 17a}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    Probably caused by : ntoskrnl.exe ( nt+21925 )

    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: 00000002
    Arg2: 80545ff0
    Arg3: f6002000
    Arg4: 0000017a

    Debugging Details:
    ------------------

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

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


    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.

    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_OVER_UC_EN_ADDRV_PCC_MEMHIRERR_7A

    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.

    MODULE_NAME: nt

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107b0c

    BUGCHECK_STR: 0x9C_AuthenticAMD

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    LAST_CONTROL_TRANSFER: from 806d38df to 804f8925

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    80545fc8 806d38df 0000009c 00000002 80545ff0 nt+0x21925
    80545fcc 00000000 00000002 80545ff0 f6002000 hal+0x58df


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt+21925
    804f8925 5d pop ebp

    SYMBOL_STACK_INDEX: 0

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: ntoskrnl.exe

    SYMBOL_NAME: nt+21925

    BUCKET_ID: WRONG_SYMBOLS

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



    Thank you very much!
     
  3. Frank4d

    Frank4d Trusted Advisor

    Joined:
    Sep 10, 2006
    Messages:
    9,126
    Your debug log is hosed. Post your minidump.DMP file here as a zipped attachment and I will run a different debug utility on it.
     
As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Loading...
Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/582714