Please Help BSOD

Starvin Marvin · 02 Aug 2011

OK so I am getting a fairly regular BSOD. I have attached the requested files according to the posting instructions.

System Info:

OS: Windows 7 Home Premium 64bit full retail version

CPU: Intel Core i-7 875K @2.93Ghz, currently overclocked to 3.61Ghz (yes I turned overclocking off to see if that would fix the problem...it didn't)

MB: ASUSTeK P7P55D-E PRO

BIOS: American Megatrends

RAM: 4 G.Skill DDR3 4GB (Total 16GB)

GRAPHICS: Radeon HD 5870

HDD: OCZ Vertex2 (Boot) and 2xWD 1TB hard drives in RAID format

Addition Info:

The BSODs usually occur when I'm not doing much, just internet browsing or playing Minecraft. Never had an issue whilst playing BFBC2 or MW2 etc. Also, I am unable to install Windows Service Pack 1 and Windows Backup fails every time it runs. On a side note, I occasionally get a high pitched tone from my speakers when I start my PC but that goes away with a restart. I'm not sure if that's related or if it's an interference issue.

What I have tried so far:

I have updated all drivers and this did slow down the occurrence of the BSODs but did not stop them. I have re-seated all components and cleaned all the slots. I have run MEMtest86 for 12 hours with no errors. I have turned off the cpu overclocking, still no change.

If you need anymore info just ask :)

Thanks, Pete

SledgeDG · 03 Aug 2011

Hi Starvin Marvin and welcome to SF!
It appears as if all dumps from Dec 24 2010 to Aug 02 2011 have all the same reasons

Code:

WHEA_UNCORRECTABLE_ERROR (124)

Main causes for that is usually either defective or incompatible Hardware.
Did you change/add any hardware components before this type of BSOD occurred [Christmas 2010]? (the CPU perhaps?)
Take back the OC. In fact reset the BIOS to safe defaults. If the system is unstable OC puts an unnecessary additional strain on it. (Why one would OC an I7 is beyond me anyways but that's just me

On the slim chance it's a driver problem replace the Intel processor driver

Code:

intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)

from here: http://downloadcenter.intel.com/Default.aspx

Code:

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


Loading Dump File [C:\Users\David\Desktop\StarvinMarvin\080211-9921-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02c4d000 PsLoadedModuleList = 0xfffff800`02e8ae50
Debug session time: Tue Aug  2 02:21:39.332 2011 (GMT-4)
System Uptime: 0 days 4:32:18.284
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800f78d028, fa000000, 400405}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware

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

6: 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: fffffa800f78d028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fa000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, 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:  f

STACK_TEXT:  
fffff880`03301b58 fffff800`02c16903 : 00000000`00000124 00000000`00000000 fffffa80`0f78d028 00000000`fa000000 : nt!KeBugCheckEx
fffff880`03301b60 fffff800`02dd3493 : 00000000`00000001 fffffa80`0f795d30 00000000`00000000 fffffa80`0f795d80 : hal!HalBugCheckSystem+0x1e3
fffff880`03301ba0 fffff800`02c165c8 : 00000000`00000728 fffffa80`0f795d30 fffff880`03301f30 fffff880`03301f00 : nt!WheaReportHwError+0x263
fffff880`03301c00 fffff800`02c15f1a : fffffa80`0f795d30 fffff880`03301f30 fffffa80`0f795d30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`03301d50 fffff800`02c15dd5 : 00000000`00000008 00000000`00000001 fffff880`03301fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`03301d90 fffff800`02c09e88 : 00000000`00000000 fffff880`032f9180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`03301dc0 fffff800`02cbbfac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`03301df0 fffff800`02cbbe13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`03301f30 fffff880`02fbc9c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`03321c98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x39c2


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

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

6: kd> lmntsm
start             end                 module name
fffff880`0554b000 fffff880`05589000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00f24000 fffff880`00f7b000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`01491000 fffff880`0149c000   acs6nts  acs6nts.sys  Wed May 26 02:28:54 2010 (4BFCBFA6)
fffff880`04742000 fffff880`047cb000   afd      afd.sys      Sun Apr 24 22:43:58 2011 (4DB4DFEE)
fffff880`055b7000 fffff880`055cd000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`04983000 fffff880`0498b000   ALSysIO64 ALSysIO64.sys Sun Apr 19 15:41:04 2009 (49EB7E50)
fffff880`014fe000 fffff880`01509000   amdxata  amdxata.sys  Fri Mar 19 12:18:18 2010 (4BA3A3CA)
fffff880`05589000 fffff880`05591000   ASACPI   ASACPI.sys   Wed Jul 15 23:31:29 2009 (4A5E9F11)
fffff880`02f8d000 fffff880`02f93000   AsIO     AsIO.sys     Thu Apr 22 07:18:03 2010 (4BD0306B)
fffff880`04978000 fffff880`04983000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`0145e000 fffff880`01467000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01467000 fffff880`01491000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`05b38000 fffff880`05b59000   AtihdW76 AtihdW76.sys Thu Mar 31 03:15:43 2011 (4D942A1F)
fffff880`04a4b000 fffff880`0538a000   atikmdag atikmdag.sys Tue May 24 22:40:32 2011 (4DDC6C20)
fffff880`03e7a000 fffff880`03ecb000   atikmpag atikmpag.sys Tue May 24 22:25:42 2011 (4DDC68A6)
fffff960`008a0000 fffff960`00901000   ATMFD    ATMFD.DLL    unavailable (00000000)
fffff880`04696000 fffff880`0469d000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`02f7c000 fffff880`02f8d000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`02bbf000 fffff880`02bdd000   bowser   bowser.sys   Wed Feb 23 00:15:06 2011 (4D6497DA)
fffff960`00720000 fffff960`00747000   cdd      cdd.dll      unavailable (00000000)
fffff880`04632000 fffff880`0465c000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`015c7000 fffff880`015f7000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d40000 fffff880`00d9e000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01000000 fffff880`01073000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`055a7000 fffff880`055b7000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`02a9e000 fffff880`02aa7000   cpuz134_x64 cpuz134_x64.sys Fri Jul 09 07:16:58 2010 (4C37052A)
fffff880`0660c000 fffff880`0661a000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`05bdb000 fffff880`05bed000   dc3d     dc3d.sys     Fri Apr 08 18:58:20 2011 (4D9F930C)
fffff880`02f5e000 fffff880`02f7c000   dfsc     dfsc.sys     Tue Apr 26 22:57:39 2011 (4DB78623)
fffff880`02f4f000 fffff880`02f5e000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`019da000 fffff880`019f0000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`05b96000 fffff880`05bb8000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`0661a000 fffff880`0662d000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`04400000 fffff880`0460a000   dump_iaStor dump_iaStor.sys Wed Mar 03 21:51:31 2010 (4B8F2033)
fffff880`06600000 fffff880`0660c000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`03ecb000 fffff880`03fbf000   dxgkrnl  dxgkrnl.sys  Tue Jan 25 23:22:56 2011 (4D3FA1A0)
fffff880`0538a000 fffff880`053d0000   dxgmms1  dxgmms1.sys  Tue Jan 25 23:22:12 2011 (4D3FA174)
fffff880`01555000 fffff880`01569000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01509000 fffff880`01555000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`01600000 fffff880`0160a000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`00db8000 fffff880`00df2000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01200000 fffff880`0124a000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`05591000 fffff880`0559e000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff800`02c04000 fffff800`02c4d000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`053d0000 fffff880`053f4000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`054b3000 fffff880`054cc000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`05bed000 fffff880`05bf5080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`054a5000 fffff880`054b3000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`02af7000 fffff880`02bbf000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`019d1000 fffff880`019da000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`01254000 fffff880`0145e000   iaStor   iaStor.sys   Wed Mar 03 21:51:31 2010 (4B8F2033)
fffff880`01090000 fffff880`011ae000   iaStorV  iaStorV.sys  Fri Mar 05 16:27:48 2010 (4B917754)
fffff880`02fb9000 fffff880`02fcf000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`05485000 fffff880`05494000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`054cc000 fffff880`054da000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00baf000 fffff800`00bb9000   kdcom    kdcom.dll    Sat Feb 05 07:21:45 2011 (4D4D40D9)
fffff880`05a5b000 fffff880`05a9e000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`017d5000 fffff880`017ef000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01860000 fffff880`0188b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`05bb8000 fffff880`05bbd200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`03fe2000 fffff880`03ff7000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`03fbf000 fffff880`03fe2000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00ce8000 fffff880`00d2c000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`0662d000 fffff880`0663b000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`05494000 fffff880`054a3000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`03e56000 fffff880`03e63000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00d9e000 fffff880`00db8000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`0465c000 fffff880`0468d000   MpFilter MpFilter.sys Tue Sep 14 20:19:28 2010 (4C901110)
fffff880`048b1000 fffff880`048c1000   MpNWMon  MpNWMon.sys  Tue Sep 14 20:19:30 2010 (4C901112)
fffff880`02bdd000 fffff880`02bf5000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`02a00000 fffff880`02a2d000   mrxsmb   mrxsmb.sys   Tue May 03 22:51:06 2011 (4DC0BF1A)
fffff880`02a2d000 fffff880`02a7b000   mrxsmb10 mrxsmb10.sys Tue May 03 22:51:08 2011 (4DC0BF1C)
fffff880`02a7b000 fffff880`02a9e000   mrxsmb20 mrxsmb20.sys Tue May 03 22:51:05 2011 (4DC0BF19)
fffff880`046fb000 fffff880`04706000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00f84000 fffff880`00f8e000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01569000 fffff880`015c7000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`02f44000 fffff880`02f4f000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`019bf000 fffff880`019d1000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`018cd000 fffff880`019bf000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`055f1000 fffff880`055fd000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`05400000 fffff880`0542f000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`05b23000 fffff880`05b38000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02ea9000 fffff880`02eb8000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02e35000 fffff880`02e7a000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01800000 fffff880`01860000   NETIO    NETIO.SYS    Thu Apr 08 22:43:59 2010 (4BBE946F)
fffff880`048c1000 fffff880`048d6000   NisDrvWFP NisDrvWFP.sys Tue Sep 14 20:20:25 2010 (4C901149)
fffff880`04706000 fffff880`04717000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`02f38000 fffff880`02f44000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02c4d000 fffff800`03229000   nt       ntkrnlmp.exe Sat Apr 09 00:14:44 2011 (4D9FDD34)
fffff880`01633000 fffff880`017d5000   Ntfs     Ntfs.sys     Thu Mar 10 22:39:25 2011 (4D79996D)
fffff880`0468d000 fffff880`04696000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`05b0a000 fffff880`05b23000   nusb3hub nusb3hub.sys Thu Nov 18 20:34:24 2010 (4CE5D420)
fffff880`04a11000 fffff880`04a42000   nusb3xhc nusb3xhc.sys Thu Nov 18 20:34:25 2010 (4CE5D421)
fffff880`02e83000 fffff880`02ea9000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00fce000 fffff880`00fe3000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f8e000 fffff880`00fc1000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00e5c000 fffff880`00e63000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00cc0000 fffff880`00cd0000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`017ef000 fffff880`01800000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`03a7a000 fffff880`03b20000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`03e63000 fffff880`03e73000   point64  point64.sys  Fri Apr 08 18:58:14 2011 (4D9F9306)
fffff880`05b59000 fffff880`05b96000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00d2c000 fffff880`00d40000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`055cd000 fffff880`055f1000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0542f000 fffff880`0544a000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`0544a000 fffff880`0546b000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`0546b000 fffff880`05485000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`02ee7000 fffff880`02f38000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`046e0000 fffff880`046e9000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`046e9000 fffff880`046f2000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`046f2000 fffff880`046fb000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`01893000 fffff880`018cd000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`03b20000 fffff880`03b28000   regi     regi.sys     Mon Apr 16 11:19:10 2007 (462393EE)
fffff880`02e00000 fffff880`02e18000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`054db000 fffff880`0554b000   Rt64win7 Rt64win7.sys Mon Mar 21 09:20:32 2011 (4D8750A0)
fffff880`03b28000 fffff880`03b33000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`0188b000 fffff880`01893000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`0481c000 fffff880`048b1000   srv      srv.sys      Thu Apr 28 23:13:05 2011 (4DBA2CC1)
fffff880`03b72000 fffff880`03bd9000   srv2     srv2.sys     Thu Apr 28 23:12:51 2011 (4DBA2CB3)
fffff880`03b33000 fffff880`03b60000   srvnet   srvnet.sys   Thu Apr 28 23:12:35 2011 (4DBA2CA3)
fffff880`0149c000 fffff880`014fe000   storport storport.sys Thu Mar 10 23:24:35 2011 (4D79A403)
fffff880`054a3000 fffff880`054a4480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01a01000 fffff880`01bfe000   tcpip    tcpip.sys    Sun Apr 24 22:47:33 2011 (4DB4E0C5)
fffff880`03b60000 fffff880`03b72000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`04735000 fffff880`04742000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`04717000 fffff880`04735000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`02ed3000 fffff880`02ee7000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00520000 fffff960`0052a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`02f93000 fffff880`02fb9000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`05a00000 fffff880`05a54000   udfs     udfs.sys     Mon Jul 13 19:23:37 2009 (4A5BC1F9)
fffff880`05a9e000 fffff880`05ab0000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`05bbe000 fffff880`05bdb000   usbccgp  usbccgp.sys  Thu Mar 24 23:23:03 2011 (4D8C0A97)
fffff880`04a42000 fffff880`04a43f00   USBD     USBD.SYS     Thu Mar 24 23:22:51 2011 (4D8C0A8B)
fffff880`04a00000 fffff880`04a11000   usbehci  usbehci.sys  Thu Mar 24 23:22:57 2011 (4D8C0A91)
fffff880`05ab0000 fffff880`05b0a000   usbhub   usbhub.sys   Thu Mar 24 23:23:22 2011 (4D8C0AAA)
fffff880`03e00000 fffff880`03e56000   USBPORT  USBPORT.SYS  Thu Mar 24 23:23:03 2011 (4D8C0A97)
fffff880`02e18000 fffff880`02e33000   USBSTOR  USBSTOR.SYS  Thu Mar 10 23:31:17 2011 (4D79A595)
fffff880`00fc1000 fffff880`00fce000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`0469d000 fffff880`046ab000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`0663f000 fffff880`06800000   viahduaa viahduaa.sys Wed Aug 04 03:51:53 2010 (4C591C19)
fffff880`046ab000 fffff880`046d0000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00fe3000 fffff880`00ff8000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e00000 fffff880`00e5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`011ae000 fffff880`011fa000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`02eb8000 fffff880`02ed3000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`046d0000 fffff880`046e0000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e71000 fffff880`00f15000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f15000 fffff880`00f24000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02e7a000 fffff880`02e83000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000b0000 fffff960`003c2000   win32k   win32k.sys   unavailable (00000000)
fffff880`0559e000 fffff880`055a7000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00f7b000 fffff880`00f84000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`02fcf000 fffff880`02ff0000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)
fffff880`048d6000 fffff880`04907000   WUDFRd   WUDFRd.sys   Mon Jul 13 20:06:06 2009 (4A5BCBEE)

Unloaded modules:
fffff880`04907000 fffff880`04978000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`019f0000 fffff880`019fe000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`04415000 fffff880`0461f000   dump_iaStor.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0461f000 fffff880`04632000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

-DG

Maguscreed · 03 Aug 2011

The most common cause of a WHEA result in the debugger when it isn't a actual hardware failure. Is when there is a problem in the overclock.
Remove the overclock I'm pretty sure your problem will clear up.
You'll have to figure out what's choking your clock yourself though.
That chip should be able to handle the clock you have on it.

Starvin Marvin · 04 Aug 2011

Thanks SledgeDG and Maguscreed for your quick responses

In regards to your question, I didn't add or change any hardware around that time. I only got the system about a month before that date so everything is pretty much brand new. I will take your advice and reset the BIOS, however I'm a little unsure on how to do this. I'm fairly new to the technical side of things but want to learn!

Could you tell me the process?

Also, do you think the other issues I'm having are related or am I potentially dealing with multiple problems?

SledgeDG · 04 Aug 2011

Even though there were 3-4 other errors among the 43 dumps i checked, mostly pointing towards RAM...since you said you had run memtest successfully I'm quite confident it's only one issue.
Let me guess...you got the system new and everything worked fine until you started to OC, right?
As for you BIOS, it's an AMI so check here Award BIOS / CMOS Setup how to load the "Optimized Defaults". Test it for a while and if you still get BSODs go in the BIOS again and load the "Failsafe Defaults".
-DG

Dave76 · 04 Aug 2011

New to the technical side of things and overclocking is likely the cause. There are many things that can go wrong when OC'ing, sometimes they won't show up until later.

Return your BIOS to Optimized Defaults as recommended by SledgeDG, see if your BSoDs stop.
If you OC again, this is how to get a stable system if things go wrong.

When you OC the CPU sometimes you need to under clock the RAM.
Have you been checking the CPU temps?

With 16GB RAM, did you adjust the RAM timings and voltages?
If yes, what did you do?

Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Have you been checking your temperatures?
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

What PSU do you have?
Give brand name, size, etc.

Starvin Marvin · 05 Aug 2011

When I got the system, I friend of mine built and OC'd it, however he has moved away so I'm stuck to sort these things out

Don't worry Dave76, I would never attempt Overclocking as a newbie!! I'm just attempting to fix the issues until I one day have the knowledge to mess around with those settings.

Ok so I have returned the BIOS so the Auto settings, but I will have to wait a good week or two until I am confident the BSOD's have stopped.

I spoke to the guy who built my system and he said he didn't underclock the RAM. I have been keeping a close eye on my CPU temps with Core Temp and all four cores sit around 35-40 degrees Celsius at idle. Under testing, with 3D Mark and Stress Prime and temps never went higher than 50 degrees per core.

In regards to adjusting RAM timings and voltages, the guy who built the system said he used the recommended settings outlined by the manufacturer. He did say it could be an issue with Bank Timing?? And I should try removing 2 sticks, one on either side, and see if that clears up the issue.

My PSU is Fatal1ty Gaming Gear 550w Professional Series.
Currently my RAM voltage is 1.5 and CPU voltage is 1.136 (I hope I read that right, still learning what everything means in the BIOS) I couldn't find the CPU integrated memory controller voltage.

Dave76 · 05 Aug 2011

Temps look good.

The CPUZ tabs look good, may need to make some adjustments.

For the CPU integrated memory controller voltage.
Check in your motherboard manual page 3-15 and 3-20, it is 'IMC voltage' control, this is the Integrated Memory Controller voltage.
In your BIOS look under 'AI Tweaker', then scroll down.

When using recommeded setting, "he used the recommended settings outlined by the manufacturer", be sure what they are recommending it for, you can search your RAM manufacturer's help website to find out what settings are 'recommended' for 16GB RAM.

When you install 4GB RAM or more you will need to adjust settings to get stability, this can be confirmed on many RAM help sites.

Most of the manufacturer's recommended settings are for 4GB RAM or less, they are for the vast majority of users that don't have a high amount of RAM.

With more than 4GB RAM, and definitely with 16GB RAM, you will need an integrated memory controller voltage bump.
More RAM cards, and more memory chips per card, will need more voltage to run correctly.
Too much IMC voltage can damage the CPU, so you must be careful when bumping the voltage.

Let me know the IMC voltage and we'll go from there.

Starvin Marvin · 05 Aug 2011

Ok, thanks for that info! I checked the BIOS and the current IMC voltage is sitting between 1.106v and 1.131v

Dave76 · 06 Aug 2011

They are usually a fixed voltage, anyway, set IMC voltage to 1.150v, and DRAM voltage to 1.550v, Save and Exit BIOS.

Run memtest86+ for a full 8 passes, best to run overnight.
If you get any errors you can stop the test.

If that passes, try to replicate the crash scenario, or stress the memory by playing games etc.

Let us know the results.