BSOD after upgrading computer local error 1033

Last week I did a complete overhaul of my system and once last week and again last night my computer blue screened while browsing the internet. I changed out my motherboard, cpu, ram, and reinstalled windows afterward; and for now I'm not overclocking until I can find the source of this problem.

Edit: I looked at it again, and it looks like a 124 code error.

I'm running:
Intel Core i5 4760k
Asus z87-a
G.SKILL Ripjaws X Series 16GB (2 x 8GB)
Nvidia GTX 670
Windows 7 64 home premium edition

Welcome to Seven Forums.

RTCore64.sys Mon Mar 11 11:32:06 2013 (513D6C56)
RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Win7)
Driver Reference Table - RTCore64.sys

If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens. Use Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.

Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log

Run SFC /SCANNOW Command - System File Checker to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

Make scans with Kaspersky TDSskiller and ESET Online scanner.

Perform a Clean Start up, this will help avoid any problematic applications from bugging the system.

dtsoftbus01.sys Thu Jun 20 13:22:51 2013 (51C2ADCB)
Daemon Tools driver [br] Possible BSOD issues in Win7
Driver Reference Table - dtsoftbus01.sys

Daemon Tools (also Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall Daemon Tools.

• DuplexSecure - FAQ

As an alternative:

• We recommend the use of Total Mounter or Magic ISO

Code:

Debug session time: Sat Sep 21 20:29:18.809 2013 (UTC + 6:00)
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
System Uptime: 3 days 9:32:03.011
Probably caused by : GenuineIntel
BugCheck 124, {0, fffffa800e12a028, be000000, 100110a}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800e12a028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  bf3.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
MaxSpeed:     3400
CurrentSpeed: 3400
BiosVersion = 1405
BiosReleaseDate = 08/19/2013
SystemManufacturer = ASUS
SystemProductName = All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Sep 16 06:01:22.972 2013 (UTC + 6:00)
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
System Uptime: 0 days 4:56:37.174
Probably caused by : GenuineIntel
BugCheck 124, {0, fffffa800dd7f028, be000000, 100110a}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800dd7f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  prime95.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
MaxSpeed:     3400
CurrentSpeed: 3400
BiosVersion = 1405
BiosReleaseDate = 08/19/2013
SystemManufacturer = ASUS
SystemProductName = All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try

Thanks for the update, best of luck.