New Computer BSOD playing Starcraft2 and browsing internet

[RevengeT]

I just put together a new gaming computer, but every once in a while it will randomly (or at least it seems) Blue Screen and reset. I am running Windows 7 Home Premium OEM. This has happened a couple times while I was playing Starcraft2 and a couple of times while just browsing the internet.
Please help!! Any and all help is very much appreciated!!
I followed the BSOD instructions and attached is the ZIP folder.

Also, my parts are as follows:
MOTHERBOARD: GIGABYTE GA-Z68X-UD3H-B3 LGA 1155 Intel Z68 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard
VIDEO CARD: EVGA 01G-P3-1561-AR GeForce GTX 560 Ti FPB (Fermi) 1GB 256-bit GDDR5 PCI Express 2.0 x16 HDCP Ready SLI Support FPB
PSU: CORSAIR Builder Series CX600 V2 600W ATX12V v2.3 80 PLUS Certified Active PFC Power Supply
CPU: Intel Core i5-2500 Sandy Bridge 3.3GHz (3.7GHz Turbo Boost) LGA 1155 95W Quad-Core Desktop Processor Intel HD Graphics 2000
RAM: CORSAIR Vengeance 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model CMZ8GX3M2A1600C9
HARD DRIVE: Seagate Barracuda ST1000DM003 1TB 7200 RPM SATA 6.0Gb/s 3.5" Internal Hard Drive -Bare Drive
OPTICAL DRIVE: SAMSUNG CD/DVD Burner Black SATA Model SH-222AB - OEM

 

[RevengeT]

I have tried a couple things but I am still having problems. I ran the Windows Memory Diagnostic and it immediately said "Hardware problems were detected. To identify and repair these problems, you will need to contact the computer manufacturer." I also uninstalled the driver that the System Health Report said had an error '52.' I ran the Windows Memory Diagnostic again. No hardware problems detected; my computer seemed to be working fine, but it just blue screened again today. After running the Windows Memory Diagnostic yet again, it again says the hardware problem message and when Windows 7 restarts it now says I have a memory problem. Could this mean my RAM is defective?
I have also had problems installing drivers. Specifically, on the one driver that I uninstalled because of the error 52, when trying to reinstall it (I got it from the Gigabyte website), it says Windows can't verify the publisher of this driver software. Other errors have also occurred while trying to install other drivers.
I've also had problems with installed programs. After installing some drivers, it said they may have not been installed correctly, would you like to try again with recommended settings. Also, Starcraft2 once said this to me after it had an error and crashed. I used the Blizzard repair to fix that. This makes me wonder, would this be a problem with my hard drive??? Or would this be RAM still? I am trying to pinpoint the problem, but am not sure how. Please help!

 

[usasma]

I'm not a great fan of the Windows Memory Diagnostic. I prefer MemTest86+. Try this free procedure to test your RAM: Memory Diagnostics (read the details at the link)

Perfmon states a Code 52 on the Intel HD graphics. Please visit http://downloadcenter.intel.com and download/install the appropriate drivers for your graphics card/device.

Please visit Windows Update and get all available updates for your system. You have 51 updates after SP1, and most systems have 65 or more.

Gigabyte EasyTune6 (ET6) is known to cause BSOD's on some Win7 systems. Please uninstall this program.

If this doesn't fix things, post back and we'll work on other stuff (personally, I suspect your RAM but am not 100% certain)

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011012-19546-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 10 18:55:48.741 2012 (UTC - 5:00)
System Uptime: 0 days 0:29:32.990
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`002c9250 00000000`0000ffff 00000000`00000000
BiosVersion = F9
BiosReleaseDate = 09/01/2011
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011012-17440-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 10 00:26:56.357 2012 (UTC - 5:00)
System Uptime: 0 days 0:37:06.606
Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x24
PROCESS_NAME:  SC2.exe
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsPagingFileIo+155
Bugcheck code 00000024
Arguments 00000000`000c08a5 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = F9
BiosReleaseDate = 09/01/2011
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3292
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010812-23431-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan  8 04:14:11.116 2012 (UTC - 5:00)
System Uptime: 0 days 0:19:07.364
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`002da110 00000000`0000ffff 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010812-15927-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan  8 03:53:47.361 2012 (UTC - 5:00)
System Uptime: 0 days 0:11:46.175
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`002aac50 00000000`0000ffff 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010712-22760-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan  7 13:24:17.846 2012 (UTC - 5:00)
System Uptime: 0 days 1:18:21.095
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  nvSCPAPISvr.ex
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`002dea90 00000000`0000ffff 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[RevengeT]

Thanks for the help, I did everything you said. Windows Update only had 3 more updates for me, though. When I re-downloaded that driver with the 52 error, it seems to have installed properly and did not say it couldn't verify the publisher.
When doing the memtest86+, the first time errors immediately began popping up and by test #3 they were at count 95. I then reseated the RAM and redid the test. This time, the errors popped up slower and by test #3 they were ~ count 60. Does this mean i have bad RAM sticks? Have they been the cause of all of my problems?

 

[usasma]

Yep, it's most likely bad RAM. Test the sticks in the first slot - one at a time. Once you've determined what's good and what's bad - test a good one in the rest of the slots. That'll tell you if it's the sticks or the slots that are bad.

 

[RevengeT]

It seems one of my RAM sticks was the one with the errors. After following your instructions, one stick had errors in both slots. Though, mysteriously the first time I tried to test them they both had no errors. After trying the test again the next day, I found the one with the errors. I have taken that one out of my computer for the moment and since I did that, I have not had a Blue Screen. Looks like I am going to have to exchange my RAM. Thank you so much for the help!!

 

[usasma]

I'm glad that you found the problem.
Thanks for letting us know!