If you're overclocking, please return the system to normal values while we troubleshoot. If there's a problem with the overclock it'll show as a hardware problem until the system is returned to stock values - so stopping the overclock is the way to troubleshoot these issues (and prevent having to replace hardware unnecessarily)
According to the MSINFO32 report you've had a bunch of video errors (STOP 0x117), followed by a couple of hardware errors (STOP 0x124) and then one error that may be related to your networking (a STOP 0x3B). The analysis of the last error shows a video
driver issue, and no firm evidence of a networking error.
I also see that you have Alcohol 52% installed. It has a
driver that's known to cause BSOD's (sptd.sys). Please uninstall Alcohol 52% and then use this free tool to remove the offending
driver:
DuplexSecure - FAQ - Remove 64 bit sptd.sys
Then please update your networking driver (it's a part of your nForce chipset
drivers) from here:
NVIDIA DRIVERS 15.53 WHQL
Next, please update your video
drivers from the nVidia website here:
NVIDIA DRIVERS 266.58 WHQL
Then, please follow the steps at this link to troubleshoot your video card (the STOP 0x117 issue is very similar to the STOP 0x116 error - so the troubleshooting is the same):
STOP 0x116: VIDEO_TDR_ERROR troubleshooting
Next, please do the following:
OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system.
Reference links 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:
BSOD BUGCHECK SUMMARY Code:
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Fri Mar 25 02:17:33.249 2011 (UTC - 4:00)
System Uptime: 0 days 13:50:36.952
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+c1f1 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: iexplore.exe
FAILURE_BUCKET_ID: X64_0x3B_nt!_??_::FNODOBFM::_string_+c1f1
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`0306f734 fffff880`089df630 00000000`00000000
BiosVersion = V1.2
BiosReleaseDate = 01/20/2010
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Mar 22 12:44:09.875 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:07.578
Probably caused by : hardware
BUGCHECK_STR: 0x124_AuthenticAMD
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`046c28f8 00000000`00000000 00000000`00000000
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Mar 10 12:24:53.828 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.578
Probably caused by : hardware
BUGCHECK_STR: 0x124_AuthenticAMD
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`045a28f8 00000000`00000000 00000000`00000000
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 19 02:11:04.828 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:08.843
Probably caused by : hardware
BUGCHECK_STR: 0x124_AuthenticAMD
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`04d8d8f8 00000000`00000000 00000000`00000000
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``