First PC Build, Constantly Crashing ("MEMORY_MANAGEMENT")

0Calories

Reputable
Jan 19, 2016
1
0
4,510
Hello everyone,

I just finished building my first pc today and it was working earlier this morning. I booted windows through my USB in the BIOS and it set up just fine. Right after the Windows set up it was working perfectly fine, so I turned it off because I had to go.

About 6 hours later I turn it back on and it's working fine still, until I go to change the resolution. I don't change any settings yet, but I switch my fan speed from the fan controller on my case, and suddenly Windows says that it has crashed and it will restart. So it automatically powers off and then powers back on, and then crashes once it boots up to windows, and this keeps happening so I'm forced to turn off my PSU. Then when I tried again, the intervals before the computer restarting has shortened. Now it can't even get to the BIOS screen before it powers itself off! I'm in quite a predicament here, neither myself nor my friend know what's going on here, any help would be greatly appreciated! Thanks guys.

My specs:

Mobo: MSI Z97 PC Mate
CPU: Intel i5-4690K Quad core
GPU: EVGA GeForce GTX 960 SSC 4GB
PSU: EVGA 600b 80 Plus Bronze
Case: Deepcool Dukase
HDD: Western Blue 1 TB
SSD: Kingston 120GB
CPU cooler: Cooler Master Hyper D92
RAM: G. Skill Ares Series 16GB (8x2)

EDIT: So I thought that the problem was due to the PSU's plug being in the wrong socket in the power bar. After I switched it, it seemed to be working perfectly fine, but the case's stock fan was annoying me, so I unplugged everything and replaced the stock case fan. I plugged everything back in and turned it back on and proceeded to use it (it was working at this time) but then crashed a few minutes later and kept trying to restart itself like before! What could be causing this problem?? Please help me out guys 🙁

UPDATE: So I saw the Windows 10 blue screen again, except this time I had enough time to notice that it said this: "Search for this error for more info: MEMORY_MANAGEMENT" Could this be an issue with my RAM sticks?