BSOD since upgrade to windows 8, still happening after going back to 7

Like this title says I've been dealing with this ever since I "upgraded" to windows 8. I tried reverting back to 7 to solve the problem but its still present, and this has been going on for a while now.

With the BSOD came with higher operating temps. But I can recreate the crash just by streaming video (Youtube, Netflix, etc) as well as playing most video games. I've tried for months off and on but I'm getting to the end of my ropes of dealing with it, this is getting to my last ditch effort before I just outright build a new rig. Any and all help is greatly appreciated.

attached is the file that SF Diagnostic Tool created.

Edit: I forgot to add that I'm using Windows 7 64bit, not sure if that helps.

STOP 0x00000101: CLOCK_WATCHDOG_TIMEOUT
Usual causes: Device driver, BIOS bug, hardware defect

   Information

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.

You may refer to this as reference: Win 7 A Clock Interrupt... BSOD (101 Error)

- Try to install the driver for this device

Code:

Not Available	ACPI\PNP0510\2	The drivers for this device are not installed.

- Most likely this is the issue

Code:

Event[1694]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2013-05-14T08:51:04.450
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Eric-PC
  Description: 
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Internal Timer Error
Processor ID: 4

The details view of this entry contains further information.

- My biggest guess is your processor's at fault. Try to stress test using Prime95
Hardware - Stress Test With Prime95

Well, things do happen. I don't know why that happened right after you upgraded. I think it's totally a coincidence

If you think it's positively a hardware issue, might as well build a new one if you can't get a RMA

Best of luck :)

You're mostly welcomed

oh, so disabling the faulty core still manages to work...
thanks for your update :) may you have better fortune with the new build