locked
Fuzzy Screen then computer restarts (custom built PC with windows 7) RRS feed

  • Question

  • I built a computer and on the second day after building, the screen randomly displayed a purplish pixelated version of what was on my screen. When this does happen the computer restarts about 5 seconds after it is shown.

    This happens everyday at completely random times. When i am doing CPU and GPU intensive tasks and when i am not doing CPU and GPU intensive tasks.

    I have no idea how to fix it and would be glad of some help.

    here is the dump files that windows has made:

    http://dl.dropbox.com/u/35974608/dump.zip

    Saturday, April 7, 2012 2:45 PM

Answers

  • 0x124 WHEA_UNCORRECTABLE_ERROR:

    http://mikemstech.blogspot.com/2010/07/windbgkd-debugging-processor-cache.html

    In this case it is a bus timeout error, which does not necessarily indicate a hardware failure. If you are using non-standard timings or have incompatible components (most often motherboard/RAM), this can be the case. If you are overclocking, then you shouldn't be...

    http://mikemstech.blogspot.com/2012/04/overclocking-is-bad-idea.html

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa8007f76038, 0, 0}
    
    Probably caused by : hardware
    
    Followup: MachineOwner
    ---------
    
    2: 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: fffffa8007f76038, 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`0318d5b0 fffff800`032d0cb9 : fffffa80`07f76010 fffffa80`06aa0040 00000000`0000000b 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`0318dad0 fffff800`031b1687 : fffffa80`07f76010 fffff800`0322b2b8 fffffa80`06aa0040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`0318db00 fffff800`03118a35 : fffff800`0328cac0 00000000`00000001 fffffa80`07fd5100 fffffa80`06aa0040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`0318db40 fffff800`03095471 : fffff880`0109ae00 fffff800`03118a10 fffffa80`06aa0000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`0318db70 fffff800`03325f7a : 00000000`00000000 fffffa80`06aa0040 00000000`00000080 fffffa80`069f4040 : nt!ExpWorkerThread+0x111
    fffff880`0318dc00 fffff800`0307c9c6 : fffff880`009b3180 fffffa80`06aa0040 fffff880`009be040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`0318dc40 00000000`00000000 : fffff880`0318e000 fffff880`03188000 fffff880`0318cc50 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
    ---------
    
    2: kd> !errrec fffffa8007f76038
    ===============================================================================
    Common Platform Error Record @ fffffa8007f76038
    -------------------------------------------------------------------------------
    Record Id     : 01cd14c8e74025c9
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 4/7/2012 14:15:44
    Flags         : 0x00000002 PreviousError
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8007f760b8
    Section       @ fffffa8007f76190
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : BUS error
    Operation     : Generic
    Flags         : 0x00
    Level         : 3
    CPU Version   : 0x0000000000600f12
    Processor ID  : 0x0000000000000000
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8007f76100
    Section       @ fffffa8007f76250
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : 12 0f 60 00 00 08 06 00 - 0b 22 98 1e ff fb 8b 17
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    Proc. Info 0  @ fffffa8007f76250
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8007f76148
    Section       @ fffffa8007f762d0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
      Status      : 0xfe00000000070f0f
      Address     : 0x00000100000085e4
      Misc.       : 0xc00a0fff01000000
    
    • Proposed as answer by Jeremy_Wu Monday, April 9, 2012 3:06 AM
    • Marked as answer by Mortifera Wednesday, April 11, 2012 1:05 PM
    Sunday, April 8, 2012 4:07 AM

All replies

  • Just a thought, did you OC or crank your rig? It would be great if you could provide the make & model of the motherboard. So far have you try swapping the graphic card to a workable one?

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    Sunday, April 8, 2012 12:41 AM
    Answerer
  • 0x124 WHEA_UNCORRECTABLE_ERROR:

    http://mikemstech.blogspot.com/2010/07/windbgkd-debugging-processor-cache.html

    In this case it is a bus timeout error, which does not necessarily indicate a hardware failure. If you are using non-standard timings or have incompatible components (most often motherboard/RAM), this can be the case. If you are overclocking, then you shouldn't be...

    http://mikemstech.blogspot.com/2012/04/overclocking-is-bad-idea.html

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa8007f76038, 0, 0}
    
    Probably caused by : hardware
    
    Followup: MachineOwner
    ---------
    
    2: 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: fffffa8007f76038, 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`0318d5b0 fffff800`032d0cb9 : fffffa80`07f76010 fffffa80`06aa0040 00000000`0000000b 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`0318dad0 fffff800`031b1687 : fffffa80`07f76010 fffff800`0322b2b8 fffffa80`06aa0040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`0318db00 fffff800`03118a35 : fffff800`0328cac0 00000000`00000001 fffffa80`07fd5100 fffffa80`06aa0040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`0318db40 fffff800`03095471 : fffff880`0109ae00 fffff800`03118a10 fffffa80`06aa0000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`0318db70 fffff800`03325f7a : 00000000`00000000 fffffa80`06aa0040 00000000`00000080 fffffa80`069f4040 : nt!ExpWorkerThread+0x111
    fffff880`0318dc00 fffff800`0307c9c6 : fffff880`009b3180 fffffa80`06aa0040 fffff880`009be040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`0318dc40 00000000`00000000 : fffff880`0318e000 fffff880`03188000 fffff880`0318cc50 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
    ---------
    
    2: kd> !errrec fffffa8007f76038
    ===============================================================================
    Common Platform Error Record @ fffffa8007f76038
    -------------------------------------------------------------------------------
    Record Id     : 01cd14c8e74025c9
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 4/7/2012 14:15:44
    Flags         : 0x00000002 PreviousError
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8007f760b8
    Section       @ fffffa8007f76190
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : BUS error
    Operation     : Generic
    Flags         : 0x00
    Level         : 3
    CPU Version   : 0x0000000000600f12
    Processor ID  : 0x0000000000000000
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8007f76100
    Section       @ fffffa8007f76250
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : 12 0f 60 00 00 08 06 00 - 0b 22 98 1e ff fb 8b 17
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    Proc. Info 0  @ fffffa8007f76250
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8007f76148
    Section       @ fffffa8007f762d0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
      Status      : 0xfe00000000070f0f
      Address     : 0x00000100000085e4
      Misc.       : 0xc00a0fff01000000
    
    • Proposed as answer by Jeremy_Wu Monday, April 9, 2012 3:06 AM
    • Marked as answer by Mortifera Wednesday, April 11, 2012 1:05 PM
    Sunday, April 8, 2012 4:07 AM
  • My graphics card came overclocked by default but nothing else is overclocked. The crash happen when i am not doing any computer intensive tasks so i don't really know why it does crash. It maybe that the RAM and motherboard are not compatible. I will dig out my motherboard manual.
    Wednesday, April 11, 2012 12:40 PM
  • Thank you for your help. I found that the RAM is not on the motherboards list of compatible RAM. I should of checked the list before buying RAM...
    Wednesday, April 11, 2012 1:05 PM