BSOD when 6 cores are working

Hello everyone
I have a problem i bought the bulldozer fx 6 with 4gb RAM as a bundle and my problem is that when my 6 cores are activated i either get BSOD or just complete freeze im running Radeon HD 6770 as GPU. I have attached mini dump as instructed any help would be appreciated.

System Information
------------------
Time of this report: 5/4/2012, 12:46:55
Machine name: PASHA-PC
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.120305-1505)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: BIOS Date: 03/26/12 09:14:22 Ver: 10.03
Processor: AMD FX(tm)-6100 Six-Core Processor (4 CPUs), ~3.3GHz
Memory: 4096MB RAM
Available OS Memory: 4078MB RAM
Page File: 4072MB used, 4081MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode


Display Devices
---------------
Card name: AMD Radeon HD 6700 Series
Manufacturer: ATI Technologies Inc.
Chip type: ATI display adapter (0x68BA)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_68BA&SUBSYS_23121787&REV_00
Display Memory: 2797 MB
Dedicated Memory: 1014 MB
Shared Memory: 1783 MB
Current Mode: 1280 x 1024 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: SAMSUNG
Monitor Id: SAM07C0
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: HDMI
Monitor Name: Generic PnP Monitor
Monitor Model: DELL E176FP
Monitor Id: DELA014
Native Mode: 1280 x 1024(p) (60.020Hz)
Output Type: HD15

Your crashes are related to your graphics card and are TDR Failure crashes.

• H2SO4 said:

  These are all stop 0x116 VIDEO_TDR_FAILURE conditions.
  
  It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.
  
  Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash. As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds. If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.
  
  If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling.
  The above quote was taken from https://www.sevenforums.com/crashes-d...tml#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining STOP 0x116: VIDEO_TDR_ERROR troubleshooting and proceed through each step. Let us know if you need further help.

Thank you i will get on it right now im surprised it was 0x116 Error i havent checked the dump this time myself however usually i get 0x00000101 BSOD ill try usasma methods and if i get any more BSOD i will surely come back to this forum

Sorry to bother again just done SFX.EXE/SCANNOW and apparently windows did find corrupted files however it stored it in a log which i cannot find is there a default location for it?

Hello Again
As expected new crashes have occurred here are the dumps,
For some reason i got a suspicion that something might be wrong with the harddrive however its brand new any suggestions on good software to check the harddrive ?

New dumps below

P.S sorry posted the wrong dump report new attached

You did get another 0x101 crash: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

For SFC:

• Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.

For your hard disk checks:

• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run the short and long tests with SeaTools for Windows and if that does not work, use SeaTools for DOS.

thank you will get on it right away will keep you updated after ill do all those checks