BSOD crash during games and browsing

Windows 7 64bit Home Premium
- installed myself (full retail)

Just upgraded mobo, graphics card , new RAM, and water cooler for cpu

ASUS Motherboard M5
AMD FX(tm) - 8150 Eight-Core Processor
Radeon AMD HD 6950
(tried a backup Nvidia 650 TI but had the same problems)

Though the comp seems to crash the most during games, it has also crashed while using the internet, and on the desktop with nothing but programs and windows open. It doesn't always give me BSOD, sometimes it just freezes and system manager cannot be called up. One time it even cut out the sound of the game after stuttering for a second. A minute later the rest of it froze.

I used Blue Screen View and it seems to source ntoskrnl.exe as the main culprit though others like blbdrive.sys and win32k.sys have also showed up.

Any help would be great. Let me know if you need anymore info.

Yes, I did a clean reinstall.
This is my first watercooler, but it's the self contained kind :
Thermaltake WATER2.0 Pro Closed-Loop All In One Liquid CPU Cooler Dual 120mm PWM Fans 120x49mm Radiator CLW0216

I downloaded the bios from the cd which had an upgrade button, so I upgraded from there. Windows seemed to auto download a driver for the gpu when I attached it but I also went to the AMD website and downloaded the latest one while wiping any driver previous.
I haven't tried finding a driver for the cpu yet.

I downloaded the drivers and updated the bios. Tried it for a couple hours and it seemed to work much longer. It inevitably froze though. No more BSOD though, so I'm not getting a dump file for it.

Software Concerns:

Recommend removing your ASUS utilities through Start Menu -> Control Panel -> Uninstall a program. They can provide software interfaces with the hardware for overclocking, and even when the overclock is not enabled, that interface can cause instability. They are also not needed for the system to function properly and may reduce system resources.

Analysis:

Hardware Checks:

Freezing generally means a hardware issue. Run some hardware checks.

• If you are overclocking any hardware, please stop.
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!
  
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Software Checks:

Freezing can sometimes mean software, but it is rare since the advent of XP. If hardware checks out, though, you should check software: Troubleshoot Application Conflicts by Performing a Clean Startup

BugCheck Codes in .dmps:

You had a number of 0x124 crashes and a 0x101 crash. See the following for these BugChecks:

BugCheck 0x101:

STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

BugCheck 0x124:

Stop 0x124 - what it means and what to try

3rd Party Drivers:

The following is for informational purposes only:

Code:

GEARAspiWDM.sys Mon May 18 06:17:04 2009 (4A1151C0)
athrx.sys Tue Jun 9 12:06:49 2009 (4A2EA4B9)
mcupdate.dll Mon Jul 13 19:29:09 2009 (4A5BDF65)
amdxata.sys Fri Mar 19 10:18:18 2010 (4BA3A3CA)
AsUpIO.sys Mon Aug 2 20:47:59 2010 (4C57835F)
AsIO.sys Mon Aug 23 19:53:02 2010 (4C7325FE)
AiChargerPlus.sys Sun Nov 7 23:48:26 2010 (4CD79D3A)
RTKVHD64.sys Tue Nov 23 03:14:08 2010 (4CEB93F0)
jraid.sys Wed Nov 24 20:27:17 2010 (4CEDD795)
amd_sata.sys Fri Mar 4 13:45:41 2011 (4D714F75)
amd_xata.sys Fri Mar 4 13:45:44 2011 (4D714F78)
Rt64win7.sys Tue Aug 23 07:55:41 2011 (4E53B15D)
asmtxhci.sys Wed Sep 14 01:36:09 2011 (4E705969)
asmthub3.sys Wed Sep 14 01:36:19 2011 (4E705973)
ASUSFILTER.sys Tue Sep 20 09:46:33 2011 (4E78B559)
lvuvc64.sys Tue Jan 17 23:41:08 2012 (4F166984)
AtihdW76.sys Thu Feb 23 05:30:12 2012 (4F463154)
atikmpag.sys Mon Jun 11 10:26:14 2012 (4FD61C26)
atikmdag.sys Mon Jun 11 10:59:31 2012 (4FD623F3)
WRkrn.sys Sat Jun 30 22:34:33 2012 (4FEFD359)

GEARAspiWDM.sys
athrx.sys
mcupdate.dll
amdxata.sys
AsUpIO.sys
AsIO.sys
AiChargerPlus.sys
RTKVHD64.sys
jraid.sys
amd_sata.sys
amd_xata.sys
Rt64win7.sys
asmtxhci.sys
asmthub3.sys
ASUSFILTER.sys
lvuvc64.sys
AtihdW76.sys
atikmpag.sys
atikmdag.sys
WRkrn.sys