Blue Screen Of Death and Constant Crashing

[KeelinTy]

Hello, I have a PC that I built, it has Windows 8.1 on it. Everyday it will constantly crash and restart. Most of the time i get a BSOD but for the past while i have been in school while i has happened. Sorry if I sound either too smart or too stupid. I am a self taught computer engineer and programmer and I'm only 15.
I've managed to stop the MEMORY_MANAGEMENT BSOD by controlling the voltage and turning off the internal Intel graphics. But I need help with all of the other crashes.


Here are the specs of my computer
Windows 8.1 64bit
Intel i7 4790K @ 4.7Ghz
12Gb DDR3 1600 RAM
AsRock Z97 Killer Motherboard
Evga Geforce GT740 4gb
Corsair H60
Evga 750 watt PSU
1TB WD Caviar Blue

 

[Jonathan Cave]

Which BSOD message are you getting ? it's probably because your overclock is unstable @ 4.7ghz

0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

 

[KeelinTy]

Which BSOD message are you getting ? it's probably because your overclock is unstable @ 4.7ghz

0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

I went into the Event Viewer and I couldnt find much. I just found the bug checker which reported an error

Here is the text from the Event Viewer

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109 (0xa3a01f59ab6239f0, 0xb3b72bdffde1b097, 0xfffff801a990cf8c, 0x0000000000000001). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 112014-13234-01.