locked
Constant Blue Screen Error Windows 7 RRS feed

  • Question

  • Can someone look at my dmp file? I think it's a hardware incompatibility, but not sure what.

    Thanks. Here's the file.

    Tuesday, April 26, 2011 12:25 PM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        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: fffffa8005fe68f8, 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_GenuineIntel
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    STACK_TEXT:  
    fffff880`033bd6b0 fffff800`02ee2d29 : fffffa80`05fe68d0 fffffa80`03cefb60 00000000`0000000a 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`033bdbd0 fffff800`02dc2217 : fffffa80`05fe68d0 fffff800`02e3c658 fffffa80`03cefb60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`033bdc00 fffff800`02d29865 : fffff800`02e9e3a0 00000000`00000202 fffff880`033bdc68 00000000`00000018 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`033bdc40 fffff800`02ca9a21 : fffff880`013c0e00 fffff800`02d29840 fffffa80`03cefb00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`033bdc70 fffff800`02f3ccce : 00540052`002e0031 fffffa80`03cefb60 00000000`00000080 fffffa80`03cdd040 : nt!ExpWorkerThread+0x111
    fffff880`033bdd00 fffff800`02c90fe6 : fffff880`03163180 fffffa80`03cefb60 fffff880`0316dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`033bdd40 00000000`00000000 : fffff880`033be000 fffff880`033b8000 fffff880`033bcb90 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_GenuineIntel_PROCESSOR_BUS_PRV
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
    Followup: MachineOwner
    ---------
    _______________________________________________
    Yes, it is a hardware problem. You have a problem with your processor.
    Make sure that it is not too hot and contact your manufacturer Technical Support.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    • Marked as answer by Juke Chou Friday, April 29, 2011 8:46 AM
    Tuesday, April 26, 2011 1:47 PM