stop 0x00000124 after Windows loads. rinse/repeat.

Did you run Intel Processor diag with admin privileges? The report seems to say that you may not have admin rights.

Right-click on the program and click "Run as Administrator"

Let me check out your SFC scan.

Im pretty sure these corrupt files can pretty much be ignored as they were introduced by an update, if i remember correctly.

I'll see if I can get Noel to take a look and confirm/provide a fix.

Code:

2015-06-20 16:18:20, Info                  CSI    00000346 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
  Found: {l:32 b:hxHfXj427JxbVLpmOJKBMMwJ3nfvwV57qrOPwblWU6s=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-06-20 16:18:20, Info                  CSI    00000347 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-06-20 16:18:20, Info                  CSI    00000348 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-06-20 16:18:20, Info                  CSI    00000349 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
  Found: {l:32 b:rX0CB3J2u+8b88W40OtkWxE6DLvV/cFEMvqhqqbQIlI=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-06-20 16:18:20, Info                  CSI    0000034a [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

Make sure you try to remove all Gigabyte utilities.

Code:

gdrv.sys Thu Mar 12 23:22:29 2009 (49B9D175)  
Gigabyte Easy Saver - mobo power utility  driver}http://www.gigabyte.com.tw/Support/Motherboard/Driver_List.aspx 
Driver Reference Table - gdrv.sys 

etdrv.sys Thu Mar  19 22:59:06 2009 (49C3067A) 
Generic Port I/O[br]May be part of  Gigabyte Tools Easy Tune 6 (incompatible with Win7)}Windows Update[br]May be  available from Gigabyte 
Driver Reference Table - etdrv.sys

Code:

AppleCharger.sys Sun Oct 27 21:59:21 2013  (526DC4F9) 
GIGABYTE On/Off Charge driver. See here for details -  http://www.gigabyte.us/MicroSite/185/on-off-charge.htm May cause BSOD on Win7/8 systems - uninstall to test (haven't seen  recently (15Jan2013)}Removal may be necessary. Updates can be found here -  http://www.gigabyte.us/support-downloads/support-downloads.aspx 
Driver Reference Table - AppleCharger.sys

Lets try a few things:
1. Remove ESET and install Microsoft Security Essentials. You can choose to go back to ESET after and test but since ESET was mentioned in a crash dump, lets make sure its not it.

Code:

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  ekrn.exe

Remove ESET and install MSE
Microsoft Security Essentials - Microsoft Windows

2. Monitor your CPU Temperatures. Ensure your fans are running properly. Clean the inside of the PC to ensure no dust is accumulating inside

3. Go into your BIOS and reset your BIOS settings to the defaults

4. Run Memtest86+ - Follow the instructions in the tutorial. Run for at least 8 passes or until you find any errors. Stop the test and move onto the next step if you have ANY errors

RAM - Test with Memtest86+

5. Try a clean boot
Troubleshoot Application Conflicts by Performing a Clean Startup

If all of the above fails, your CPU is likely faulty.

Yep - the CBS errors are the result of MS mis-coding variable files as static ones (KB3068708) - you can either uninstall the update and hide it, or ignore these two fails.