win 7 64 bit blue screen error

Discussion in 'Windows 64bit' started by ciccio, Mar 11, 2010.

  1. ciccio

    ciccio Guest

    can help me ,tnks

    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\031110-33665-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\*http://msdl.microsoft.com/download/
    symbols
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02a4d000 PsLoadedModuleList =
    0xfffff800`02c8ae50
    Debug session time: Thu Mar 11 11:37:06.007 2010 (GMT+1)
    System Uptime: 0 days 0:00:25.740
    Loading Kernel Symbols
    ........................................................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    *
    *
    * Bugcheck
    Analysis *
    *
    *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, fffffa80051dc8f8, 0, 0}

    Probably caused by : hardware

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

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

    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type
    of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa80051dc8f8, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


    BUGCHECK_STR: 0x124_AuthenticAMD

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    STACK_TEXT:
    fffff880`033b66f0 fffff800`02d07a89 : fffffa80`051dc8d0
    fffffa80`039f9b60 00000000`00000006 00000000`00000001 : nt!
    WheapCreateLiveTriageDump+0x6c
    fffff880`033b6c10 fffff800`02be9547 : fffffa80`051dc8d0
    fffff800`02c625f8 fffffa80`039f9b60 00000003`00000005 : nt!
    WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`033b6c40 fffff800`02b51b95 : fffff800`02cc4360
    fffffa80`0516ae58 fffffa80`0516ae50 fffffa80`039f9b60 : nt!
    WheapProcessWorkQueueItem+0x57
    fffff880`033b6c80 fffff800`02acc161 : fffff880`01343e00
    fffff800`02b51b70 fffffa80`039f9b60 00000000`00000000 : nt!
    WheapWorkQueueWorkerRoutine+0x25
    fffff880`033b6cb0 fffff800`02d62166 : 00000000`00000000
    fffffa80`039f9b60 00000000`00000080 fffffa80`039e4890 : nt!
    ExpWorkerThread+0x111
    fffff880`033b6d40 fffff800`02a9d486 : fffff880`03163180
    fffffa80`039f9b60 fffff880`0316dfc0 00000000`00000000 : nt!
    PspSystemThreadStartup+0x5a
    fffff880`033b6d80 00000000`00000000 : fffff880`033b7000
    fffff880`033b1000 fffff880`04730540 00000000`00000000 : nt!
    KxStartSystemThread+0x16


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

    BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

    Followup: MachineOwner
     
    ciccio, Mar 11, 2010
    #1
    1. Advertising

  2. ciccio

    Carlos Guest

    ciccio,
    You are experimenting a major hardware failure which is not related to the
    operating system you are using.
    There are countless posts all over the internet with your hardware issue.
    You will need spare parts like CPU, power supply, memory, etc. in order to
    find the faulty part.
    It might even be a motherboard failure!.
    Best of luck.
    Carlos

    "ciccio" wrote:

    > can help me ,tnks
    >
    > Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    > Copyright (c) Microsoft Corporation. All rights reserved.
    >
    >
    > Loading Dump File [C:\Windows\Minidump\031110-33665-01.dmp]
    > Mini Kernel Dump File: Only registers and stack trace are available
    >
    > Symbol search path is: SRV*c:\*http://msdl.microsoft.com/download/
    > symbols
    > Executable search path is:
    > Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    > Product: WinNt, suite: TerminalServer SingleUserTS
    > Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    > Machine Name:
    > Kernel base = 0xfffff800`02a4d000 PsLoadedModuleList =
    > 0xfffff800`02c8ae50
    > Debug session time: Thu Mar 11 11:37:06.007 2010 (GMT+1)
    > System Uptime: 0 days 0:00:25.740
    > Loading Kernel Symbols
    > ........................................................
    > Loading User Symbols
    > Mini Kernel Dump does not contain unloaded driver list
    > *******************************************************************************
    > *
    > *
    > * Bugcheck
    > Analysis *
    > *
    > *
    > *******************************************************************************
    >
    > Use !analyze -v to get detailed debugging information.
    >
    > BugCheck 124, {0, fffffa80051dc8f8, 0, 0}
    >
    > Probably caused by : hardware
    >
    > Followup: MachineOwner
    > ---------
    >
    > 1: kd> !analyze -v
    > *******************************************************************************
    > *
    > *
    > * Bugcheck
    > Analysis *
    > *
    > *
    > *******************************************************************************
    >
    > WHEA_UNCORRECTABLE_ERROR (124)
    > A fatal hardware error has occurred. Parameter 1 identifies the type
    > of error
    > source that reported the error. Parameter 2 holds the address of the
    > WHEA_ERROR_RECORD structure that describes the error conditon.
    > Arguments:
    > Arg1: 0000000000000000, Machine Check Exception
    > Arg2: fffffa80051dc8f8, Address of the WHEA_ERROR_RECORD structure.
    > Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    > Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    >
    > Debugging Details:
    > ------------------
    >
    >
    > BUGCHECK_STR: 0x124_AuthenticAMD
    >
    > CUSTOMER_CRASH_COUNT: 1
    >
    > DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    >
    > PROCESS_NAME: System
    >
    > CURRENT_IRQL: 0
    >
    > STACK_TEXT:
    > fffff880`033b66f0 fffff800`02d07a89 : fffffa80`051dc8d0
    > fffffa80`039f9b60 00000000`00000006 00000000`00000001 : nt!
    > WheapCreateLiveTriageDump+0x6c
    > fffff880`033b6c10 fffff800`02be9547 : fffffa80`051dc8d0
    > fffff800`02c625f8 fffffa80`039f9b60 00000003`00000005 : nt!
    > WheapCreateTriageDumpFromPreviousSession+0x49
    > fffff880`033b6c40 fffff800`02b51b95 : fffff800`02cc4360
    > fffffa80`0516ae58 fffffa80`0516ae50 fffffa80`039f9b60 : nt!
    > WheapProcessWorkQueueItem+0x57
    > fffff880`033b6c80 fffff800`02acc161 : fffff880`01343e00
    > fffff800`02b51b70 fffffa80`039f9b60 00000000`00000000 : nt!
    > WheapWorkQueueWorkerRoutine+0x25
    > fffff880`033b6cb0 fffff800`02d62166 : 00000000`00000000
    > fffffa80`039f9b60 00000000`00000080 fffffa80`039e4890 : nt!
    > ExpWorkerThread+0x111
    > fffff880`033b6d40 fffff800`02a9d486 : fffff880`03163180
    > fffffa80`039f9b60 fffff880`0316dfc0 00000000`00000000 : nt!
    > PspSystemThreadStartup+0x5a
    > fffff880`033b6d80 00000000`00000000 : fffff880`033b7000
    > fffff880`033b1000 fffff880`04730540 00000000`00000000 : nt!
    > KxStartSystemThread+0x16
    >
    >
    > STACK_COMMAND: kb
    >
    > FOLLOWUP_NAME: MachineOwner
    >
    > MODULE_NAME: hardware
    >
    > IMAGE_NAME: hardware
    >
    > DEBUG_FLR_IMAGE_TIMESTAMP: 0
    >
    > FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    >
    > BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    >
    > Followup: MachineOwner
    > .
    >
     
    Carlos, Mar 11, 2010
    #2
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Mike
    Replies:
    10
    Views:
    19,936
  2. =?Utf-8?B?TGlnaHRuYg==?=

    XP 64 bit crashes (blue screen)

    =?Utf-8?B?TGlnaHRuYg==?=, Oct 6, 2005, in forum: Windows 64bit
    Replies:
    6
    Views:
    619
    Lightnb
    Oct 9, 2005
  3. =?Utf-8?B?QnJhbmRvbiBX?=

    Windows XP 64 bit Installation Blue Screen HELP!!

    =?Utf-8?B?QnJhbmRvbiBX?=, Jan 14, 2006, in forum: Windows 64bit
    Replies:
    1
    Views:
    504
  4. Guven YILDIZ
    Replies:
    4
    Views:
    776
    Mark H
    Jul 24, 2008
  5. Big.Doc.D
    Replies:
    17
    Views:
    955
    Big.Doc.D
    Jul 27, 2009
Loading...

Share This Page