Computer BSODing recently


  1. Posts : 4
    Windows 7 Professional x64
       #1

    Computer BSODing recently


    Hello everyone,

    I built this system in early 2009 and it has been fairly stable until recently. Over the course of the last 2 weeks I have had 6 BSODs and I am beginning to think something is up. I often watch a stream and play a game at the same time and noticed that every once in a both my monitors would flicker and the stream would be green. I would have an error that said the video card drive had stopped responding and recovered. If I restarted the stream the computer would almost always crash. I swapped video cards and haven't had this problem yet but still getting BSODs.

    Systems specs:
    Windows 7 Professional 64bit
    Intel Core i7-920 Bloomfield 2.66GHz
    GIGABYTE GA-EX58-UD5
    CORSAIR DOMINATOR 6GB
    SAPPHIRE 100245L Radeon HD 4850

    Files attached, if anything else is needed please let me know.
      My Computer


  2. Posts : 6,668
    Windows 7 x64
       #2

    the minidumps are pointing to a hardware level fault.
    This usually means failing hardware, or a overclock that has become unstable over time.
    If the computer is currently overclocked at all, I suggest returning to the default settings now.

    Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.bak

    The minidumps are mostly incomplete which is preventing me from getting all the details I need to look at possible software side causes.

    The only thing software side I know of that can actually cause this error though is a really serious problem with antivirus/firewall software.

    Code:
    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: fffffa8006caa618, 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`033626f0 fffff800`032dcc59 : fffffa80`06caa5f0 fffffa80`05220680 00000000`00000006 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`03362c10 fffff800`031bcfa7 : fffffa80`06caa5f0 fffff800`032372b8 fffffa80`05220680 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`03362c40 fffff800`031245c5 : fffff800`03298ac0 00000000`00000202 fffff880`03362ca8 00000000`00000018 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`03362c80 fffff800`030a4021 : fffff880`01177e00 fffff800`031245a0 fffffa80`05220600 dfbbdfbb`0d3c0d3c : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`03362cb0 fffff800`0333632e : 62696269`0f0c0f0c fffffa80`05220680 00000000`00000080 fffffa80`051fcb30 : nt!ExpWorkerThread+0x111
    fffff880`03362d40 fffff800`0308b666 : fffff880`03186180 fffffa80`05220680 fffff880`031910c0 6eee6eee`fa1afa1a : nt!PspSystemThreadStartup+0x5a
    fffff880`03362d80 00000000`00000000 : fffff880`03363000 fffff880`0335d000 fffff880`03361fd0 00000000`00000000 : nt!KiStartSystemThread+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_CACHE_PRV
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE_PRV
    
    Followup: MachineOwner
    ---------
    
    1: kd> lm n t
    start             end                 module name
    fffff800`00bac000 fffff800`00bb6000   kdcom    kdcom.dll    Sat Feb 05 10:52:49 2011 (4D4D8061)
    fffff800`0301a000 fffff800`03603000   nt       ntkrnlmp.exe Fri Apr 08 23:15:23 2011 (4D9FDD5B)
    fffff800`03603000 fffff800`0364c000   hal      hal.dll      Sat Nov 20 07:00:25 2010 (4CE7C669)
    fffff880`00c04000 fffff880`00c53000   mcupdate mcupdate.dll Sat Nov 20 07:03:51 2010 (4CE7C737)
    fffff880`00c53000 fffff880`00c67000   PSHED    PSHED.dll    Mon Jul 13 20:32:23 2009 (4A5BE027)
    fffff880`00c67000 fffff880`00cc5000   CLFS     CLFS.SYS     Mon Jul 13 18:19:57 2009 (4A5BC11D)
    fffff880`00cc5000 fffff880`00d85000   CI       CI.dll       Sat Nov 20 07:12:36 2010 (4CE7C944)
    fffff880`00d85000 fffff880`00de1000   volmgrx  volmgrx.sys  Sat Nov 20 03:20:43 2010 (4CE792EB)
    fffff880`00e21000 fffff880`00ec5000   Wdf01000 Wdf01000.sys Mon Jul 13 18:22:07 2009 (4A5BC19F)
    fffff880`00ec5000 fffff880`00ed4000   WDFLDR   WDFLDR.SYS   Mon Jul 13 18:19:54 2009 (4A5BC11A)
    fffff880`00ed4000 fffff880`00f2b000   ACPI     ACPI.sys     Sat Nov 20 03:19:16 2010 (4CE79294)
    fffff880`00f2b000 fffff880`00f34000   WMILIB   WMILIB.SYS   Mon Jul 13 18:19:51 2009 (4A5BC117)
    fffff880`00f34000 fffff880`00f3e000   msisadrv msisadrv.sys Mon Jul 13 18:19:26 2009 (4A5BC0FE)
    fffff880`00f3e000 fffff880`00f71000   pci      pci.sys      Sat Nov 20 03:19:11 2010 (4CE7928F)
    fffff880`00f71000 fffff880`00f7e000   vdrvroot vdrvroot.sys Mon Jul 13 19:01:31 2009 (4A5BCADB)
    fffff880`00f7e000 fffff880`00f93000   partmgr  partmgr.sys  Sat Nov 20 03:20:00 2010 (4CE792C0)
    fffff880`00f93000 fffff880`00fa8000   volmgr   volmgr.sys   Sat Nov 20 03:19:28 2010 (4CE792A0)
    fffff880`00fa8000 fffff880`00faf000   pciide   pciide.sys   Mon Jul 13 18:19:49 2009 (4A5BC115)
    fffff880`00faf000 fffff880`00fbf000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 18:19:48 2009 (4A5BC114)
    fffff880`00fbf000 fffff880`00fd9000   mountmgr mountmgr.sys Sat Nov 20 03:19:21 2010 (4CE79299)
    fffff880`01000000 fffff880`0105e000   msrpc    msrpc.sys    Sat Nov 20 03:21:56 2010 (4CE79334)
    fffff880`0105e000 fffff880`01089000   ksecpkg  ksecpkg.sys  Sat Nov 20 04:10:34 2010 (4CE79E9A)
    fffff880`010b9000 fffff880`010f5000   vmbus    vmbus.sys    Sat Nov 20 03:57:29 2010 (4CE79B89)
    fffff880`010f5000 fffff880`01109000   winhv    winhv.sys    Sat Nov 20 03:20:02 2010 (4CE792C2)
    fffff880`01109000 fffff880`01112000   atapi    atapi.sys    Mon Jul 13 18:19:47 2009 (4A5BC113)
    fffff880`01112000 fffff880`0113c000   ataport  ataport.SYS  Sat Nov 20 03:19:15 2010 (4CE79293)
    fffff880`0113c000 fffff880`01147000   amdxata  amdxata.sys  Fri Mar 19 11:18:18 2010 (4BA3A3CA)
    fffff880`01147000 fffff880`01193000   fltmgr   fltmgr.sys   Sat Nov 20 03:19:24 2010 (4CE7929C)
    fffff880`01193000 fffff880`011a7000   fileinfo fileinfo.sys Mon Jul 13 18:34:25 2009 (4A5BC481)
    fffff880`011a7000 fffff880`011b2ae0   PxHlpa64 PxHlpa64.sys Mon Dec 10 17:49:01 2007 (475DD06D)
    fffff880`01222000 fffff880`013c5000   Ntfs     Ntfs.sys     Thu Mar 10 21:39:39 2011 (4D79997B)
    fffff880`013c5000 fffff880`013e0000   ksecdd   ksecdd.sys   Sat Nov 20 03:21:15 2010 (4CE7930B)
    fffff880`0140c000 fffff880`0147e000   cng      cng.sys      Sat Nov 20 04:08:45 2010 (4CE79E2D)
    fffff880`0147e000 fffff880`0148f000   pcw      pcw.sys      Mon Jul 13 18:19:27 2009 (4A5BC0FF)
    fffff880`0148f000 fffff880`01499000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 18:19:45 2009 (4A5BC111)
    fffff880`01499000 fffff880`0158c000   ndis     ndis.sys     Sat Nov 20 03:23:30 2010 (4CE79392)
    fffff880`0158c000 fffff880`015ec000   NETIO    NETIO.SYS    Sat Nov 20 03:23:13 2010 (4CE79381)
    fffff880`01600000 fffff880`01613000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 18:21:51 2009 (4A5BC18F)
    fffff880`01619000 fffff880`0181d000   tcpip    tcpip.sys    Sun Apr 24 21:37:30 2011 (4DB4DE6A)
    fffff880`0181d000 fffff880`01867000   fwpkclnt fwpkclnt.sys Sat Nov 20 03:21:37 2010 (4CE79321)
    fffff880`01867000 fffff880`01877000   vmstorfl vmstorfl.sys Sat Nov 20 03:57:30 2010 (4CE79B8A)
    fffff880`01877000 fffff880`018c3000   volsnap  volsnap.sys  Sat Nov 20 03:20:08 2010 (4CE792C8)
    fffff880`018c3000 fffff880`018cb000   spldr    spldr.sys    Mon May 11 11:56:27 2009 (4A0858BB)
    fffff880`018cb000 fffff880`018e8000   sbp2port sbp2port.sys Sat Nov 20 03:19:21 2010 (4CE79299)
    fffff880`018e8000 fffff880`01922000   rdyboost rdyboost.sys Sat Nov 20 03:43:10 2010 (4CE7982E)
    fffff880`01922000 fffff880`01934000   mup      mup.sys      Mon Jul 13 18:23:45 2009 (4A5BC201)
    fffff880`01934000 fffff880`0193d000   hwpolicy hwpolicy.sys Sat Nov 20 03:18:54 2010 (4CE7927E)
    fffff880`0193d000 fffff880`01977000   fvevol   fvevol.sys   Sat Nov 20 03:24:06 2010 (4CE793B6)
    fffff880`01977000 fffff880`0198d000   disk     disk.sys     Mon Jul 13 18:19:57 2009 (4A5BC11D)
    fffff880`0198d000 fffff880`019bd000   CLASSPNP CLASSPNP.SYS Sat Nov 20 03:19:23 2010 (4CE7929B)
    fffff880`019bd000 fffff880`019c9000   avgrkx64 avgrkx64.sys Wed Mar 16 09:06:34 2011 (4D80C3EA)
    fffff880`019c9000 fffff880`019d3000   AVGIDSEH AVGIDSEH.Sys Mon Feb 21 23:23:04 2011 (4D634838)
    fffff880`019d3000 fffff880`019e1000   crashdmp crashdmp.sys Mon Jul 13 19:01:01 2009 (4A5BCABD)
    fffff880`019e1000 fffff880`019ed000   dump_ataport dump_ataport.sys Mon Jul 13 18:19:47 2009 (4A5BC113)
    fffff880`019ed000 fffff880`019f6000   dump_atapi dump_atapi.sys Mon Jul 13 18:19:47 2009 (4A5BC113)
    Mini Kernel Dump does not contain unloaded driver list
      My Computer


  3. Posts : 4
    Windows 7 Professional x64
    Thread Starter
       #3

    The file was renamed. Is there a way I can start testing for faulty hardware? I have a feeling it's either the videocard or motherboard based on the driver responding error.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:33.
Find Us