Recently Built PC - BSOD Dump file

Lupac · 03 Jun 2011

Hello,

I believe I am posting every thing correctly and in the correct spot but if it is not then please move to the appropriate location, thanks.

This is the fourth BSOD I have received.
My system is as follows:

OS: Windows 7 Ultimate 64-bit OEM
CPU: Intel i7-950
Motherboard: Gigabyte GA-X58A-UD3R (rev 2.0) Motherboard
RAM: G.SKILL PI Series 6GB (3 x 2GB) DDR3 1600 Model F3-12800CL7T-6GBPI
GPU: SAPPHIRE 100314SR Radeon HD 6870 1GB 256-bit
SSD: 80 GB Intel X25-M
HDD - SAMSUNG Spinpoint F3 HD103SJ 1TB 7200 RPM SATA 3.0Gb/s 3.5"-Bare Drive
PSU: Corsair 650W

Water Cooling Components

Top Radiator - XSPC RX360 - 3X120mm Radiator Rev. 2
Top Radiator Fans - Scythe Gentle Typhoon 120mm Silent Case Fan - 1850 RPM
Front Radiator - XSPC RX120 - 1X120mm Radiator Rev. 2
Front Radiator Fans - Scythe Gentle Typhoon 120 mm Silent Case Fan - 1850 RPM
Reservoir - XSPC Acrylic Dual 5.25” Reservoir for one Laing D5 / MCP655
Pump - Swiftech MCP655 / D5 Vario 12v DC Pump - with Speed Controller
CPU Water Block - EK Waterblocks EK-Supreme HF - Full Nickel - Rev 2
GPU Water Block - XSPC EK-Nickel water block for Radeon HD 6870
Fan Controller - Scythe KM03-BK KAZE MASTER PRO 5.25in. 6- Channel
Tubing - Feser Tube Active UV Hose - ID 1/2" - UV BLUE

Thank again for any help you may be able to provide.

Lupac · 03 Jun 2011

I also have the most recently updated BIOS (FF i believe) and drivers as far I know, thanks again.

usasma · 04 Jun 2011

MSINFO32 shows hardware errors, a crash due to a memory access error, and a video driver timeout.

First, I'd have to wonder about the stability of your overclock. Please return the system to default values while we're troubleshooting. Once we have the system stable at default values, then you can add the overclock back in to see how it works (that's the procedure for troubleshooting overclocks).

After that, I'd then have to wonder about the seating of your video card with all that water cooling stuff hanging off of it (My last STOP 0x124 was on a video card that wasn't completely plugged in).

The STOP 0x117 (video driver timeout) isn't present in the memory dumps that you've uploaded, yet it's dated 28May2011.

After you've checked out the seating of the video card, have a look at this topic for troubleshooting suggestions (it was written with air-cooling in mind, but you can make the adjustment for water cooling as needed): STOP 0x116: VIDEO_TDR_ERROR troubleshooting
STOP 0x117's are troubleshot the same way as STOP 0x116's.

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

Code:


winhv.sys               Sat Nov 20 04:20:02 2010 (4CE792C2)
vmbus.sys               Sat Nov 20 04:57:29 2010 (4CE79B89)
iaStorV.sys             Thu Jun 10 20:46:19 2010 (4C11875B)
amdxata.sys             Fri Mar 19 12:18:18 2010 (4BA3A3CA)
SYMDS64.SYS             Mon Aug 17 19:35:30 2009 (4A89E942)
SYMEFA64.SYS            Wed Apr 21 17:47:39 2010 (4BCF727B)
MpFilter.sys            Tue Sep 14 20:19:28 2010 (4C901110)
nusb3xhc.sys            Thu Nov 18 20:34:25 2010 (4CE5D421)
SRTSP64.SYS             Wed Feb 24 18:59:29 2010 (4B85BD61)
Ironx64.SYS             Tue Apr 27 20:48:23 2010 (4BD785D7)
SRTSPX64.SYS            Wed Feb 24 18:59:48 2010 (4B85BD74)
SYMEVENT64x86.SYS       Thu Aug 13 18:28:21 2009 (4A849385)
MpNWMon.sys             Tue Sep 14 20:19:30 2010 (4C901112)
purendis.sys            Sat Jun 06 00:32:06 2009 (4A29F146)
SYMTDIV.SYS             Tue May 04 00:38:27 2010 (4BDFA4C3)
SymIMv.sys              Fri Apr 30 22:12:21 2010 (4BDB8E05)
IDSvia64.sys            Fri Mar 11 21:15:42 2011 (4D7AD74E)
GIDv2.SYS               Thu Mar 03 18:42:40 2011 (4D702770)
pnarp.sys               Sat Jun 06 02:06:44 2009 (4A2A0774)
ccHPx64.sys             Fri Feb 05 16:05:45 2010 (4B6C8829)
GEARAspiWDM.sys         Mon May 18 08:17:04 2009 (4A1151C0)
atikmpag.sys            Tue Apr 19 21:22:32 2011 (4DAE3558)
nusb3hub.sys            Thu Nov 18 20:34:24 2010 (4CE5D420)
AtihdW76.sys            Wed Nov 17 07:02:04 2010 (4CE3C43C)
SaiHF51A.sys            Thu May 31 04:46:53 2007 (465E8B7D)
ALSysIO64.sys           Sun Apr 19 15:41:04 2009 (49EB7E50)
WinRing0x64.sys         Sat Jul 26 09:29:37 2008 (488B26C1)
NisDrvWFP.sys           Tue Sep 14 20:20:25 2010 (4C901149)
SaiUF51A.sys            Thu May 31 04:47:01 2007 (465E8B85)
EraserUtilRebootDrv.sys Tue May 03 00:23:25 2011 (4DBF833D)
Rt64win7.sys            Thu Jan 13 06:57:19 2011 (4D2EE89F)
atikmdag.sys            Tue Apr 19 21:53:29 2011 (4DAE3C99)
atikmpag.sys            Tue Mar 08 23:17:42 2011 (4D76FF66)

In particular, please update your Norton Protection to the latest version - and update the outdated SaiTek drivers (from 2007)

Please post back with any BSOD's after you've removed the overclock.

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\053111-46035-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue May 31 20:35:36.814 2011 (UTC - 4:00)
System Uptime: 0 days 2:57:29.764
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  ccsvchst.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_VRF_PROCESSOR_MAE
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`08dc5028 00000000`fa000000 00000000`00400405
BiosVersion = FF
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i7 CPU         950  @ 3.07GHz"
MaxSpeed:     3070
CurrentSpeed: 4000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052811-14040-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 18:21:13.290 2011 (UTC - 4:00)
System Uptime: 0 days 4:00:45.102
*** 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
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`0834e028 00000000`ba000000 00000000`00400405
BiosVersion = FF
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i7 CPU         950  @ 3.07GHz"
MaxSpeed:     3070
CurrentSpeed: 4000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052411-15022-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue May 24 11:42:15.921 2011 (UTC - 4:00)
System Uptime: 0 days 2:53:36.733
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  sidebar.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`05530028 00000000`fa000000 00000000`00400405
BiosVersion = FF
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i7 CPU         950  @ 3.07GHz"
MaxSpeed:     3070
CurrentSpeed: 4000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052311-15584-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun May 22 22:30:49.593 2011 (UTC - 4:00)
System Uptime: 0 days 7:25:04.764
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72d6 )
BUGCHECK_STR:  0x19_22
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  prime95.exe
FAILURE_BUCKET_ID:  X64_0x19_22_nt!_??_::FNODOBFM::_string_+72d6
Bugcheck code 00000019
Arguments 00000000`00000022 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = FF
BiosReleaseDate = 02/18/2011
CPUID:        "Intel(R) Core(TM) i7 CPU         950  @ 3.07GHz"
MaxSpeed:     3070
CurrentSpeed: 4000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Lupac · 04 Jun 2011

Thanks for the reply, I just run 4 instances of Memtest with 1050 mhz in each was successful.

I did trouble shoot everthing before I started to overclock and still did not get a BSOD for a month or so.

I hear what you are saying about the watercooling and perhaps the gpu is not fully seated which I will def. check.

Thanks for the assistance, I hope to be able to also try the other things that you mentioned as well when I get back home on Monday as wellm thanks again.

usasma · 04 Jun 2011

After running a system for a while the overclock may deteriorate (if a particular piece of hardware is stressed too much). So, start with the system at default values and then increase it slowly, stress testing it along the way.

Good Luck!

Lupac · 07 Jun 2011

USAMSA,

Hey man, thanks for the thorough analysis of the dump, it is truly appreciated.
I just removed the OC. I do however have my memory settings set to the manufacturer specifications, which I believe should stay that way while I begin trouble shooting.

I will do some more research following the links that you provided and will hopefully be able to post a reply in the next day or so.

Thanks again for your assistance regarding these issues.

Lupac · 08 Jun 2011

USAMSA,

I am attempting to decode and resolve this issue.
My GPU is seated correctly and although I am almost positive that it is not a heat issue I do have an additional large fan blowing on it at the moment.

How did you determine that the error is a 0x116 or 0x117?

I think that it is a 124 error but I am not familiar with this type of analysis and it seems that you are.

I am also interested in how you determined that the drivers you mentioned (nortan & Sai Tek) are not up to date and I believe that you are most likely correct in terms of these being out of date.
Thanks again for your assistance and I look forward to hearing back from you.

usasma · 09 Jun 2011

Look in the MSINFO32 report - the last section (Error reporting). Often you can find BSOD errors there that haven't been captured by the OS. And, in most cases like that, the failure to capture suggests a hardware problem that's most likely with the video card.

The Saitek drivers are highlighted in RED in my quoted report above.
In the same report are drivers starting with SYM - those are some of your Symantec/Norton drivers (there are others there also).
Each of those drivers has a date stamp to the left of it - that's what tells me that they're older.