TechSpot

Need help on HARD BSOD problem

By inerax
Nov 4, 2007
  1. alright so... i have been working with the same BSOD problem for some time now. i have a dual core AMD system, 1 stick 1gig ram, 10000rpm raptor. i am currently useing a PCI-E x1600 pro. i have changed the mother board and processor. when i take the x1600 pro out and use the onboard graphics i no longer get blue screen, so that points to the card. i borrowd a PCI-E card from a friend that is in good working order and am get BSOD with that card!!! if any one has any idea what is going on i would sure love the help... when i pull the temps from the nvidia card i borrowed from my friend it is showing 150+ and the x1600 shows even hotter. is it possible that some software is causing this? if so what software??? also when i touch the card in the computer it does not feel hot.. here is the crash dump log



    Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini110307-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 0n2
    *** 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 = 0x8055c700
    Debug session time: Sat Nov 3 21:03:14.406 2007 (GMT-7)
    System Uptime: 0 days 4:58:53.109
    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, 8054d5f0, b2000000, 70f0f}



    Probably caused by : hardware ( nt!KeForceResumeThread+1 )

    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: 00000004
    Arg2: 8054d5f0
    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

    MISALIGNED_IP:
    nt!KeForceResumeThread+1
    804f9deb 5d pop ebp

    LAST_CONTROL_TRANSFER: from 806e7bff to 804f9deb

    STACK_TEXT:
    8054d5c8 806e7bff 0000009c 00000004 8054d5f0 nt!KeForceResumeThread+0x1
    8054d6f4 806e2c52 80042000 00000000 00000000 hal!KeRevertToUserAffinityThread+0x5
    00000000 00000000 00000000 00000000 00000000 hal!HalpWriteCmosTime+0xce


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KeForceResumeThread+1
    804f9deb 5d pop ebp

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!KeForceResumeThread+1

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MODULE_NAME: hardware

    FAILURE_BUCKET_ID: IP_MISALIGNED

    BUCKET_ID: IP_MISALIGNED

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

    if you have any questions please ask!!!
     
  2. pdyckman@comcas

    pdyckman@comcas TS Rookie Posts: 527

    Offhand I think that your motherboard might be messed up. If all is O.K. when you pull external video cards and run integrated, your video interface slot could be shot.
     
  3. inerax

    inerax TS Rookie Topic Starter

    i thought the mother board would be messed up too BUT it is less then 2 weeks old. it was happening with the old board and the new board also.
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

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