Multiple BSODs, Stop Error 0X0000001E, computer locks up/auto reboots

I should add, this processor has 'Turboboost' which is essentially automatic overclocking up to I believe around 20%. I'm sure it will be suggested to disable it - but wanted to mention it for full disclosure.

Can you upload the crash reports? 0x101 is occasionally caused by driver faults, as well. Usually it is hardware as you said, but it can also be an underlying driver conflict.

Attached is the jcgriff zipped file (hopefully with everything you need to analyze) and a new performance report. I'll add after2-3 BSOD's, the computer locked up once or twice and I shut it down hard, so that might have generated a crash report as well. Look forward to your next comments.

Problem Devices:

Code:

WD SES Device USB Device	USBSTOR\OTHER&VEN_WD&PROD_SES_DEVICE&REV_1003\575844314139315439333534&1	The drivers for this device are not installed.
Not Available	ACPI\ATK0110\1010110	The drivers for this device are not installed.
psc 2500 series	ROOT\MULTIFUNCTION\0000	This device is disabled.

Security Software:[code]ccsvchst.exe c:\program files (x86)\norton internet security\engine\19.6.1.8\ccsvchst.exe 1656 8 1024 10240 3/20/2012 10:22 AM 11.2.1.4 134.99 KB (138,232 bytes) 3/8/2012 9:15 PM
ccsvchst.exe c:\program files (x86)\norton internet security\engine\19.6.1.8\ccsvchst.exe 2528 8 1024 10240 3/20/2012 10:22 AM 11.2.1.4 134.99 KB (138,232 bytes) 3/8/2012 9:15 PM
[code]


The .dmp file was corrupted... It was: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg as you said, but beyond that, I could not determine anything useful from it. I would suggest turning off all overclocking and setting all hardware to stable default settings (this does include disabling turboboost).


Due to the corrupted .dmp file, check for data corruption:

• 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 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.