My computer keeps turning itself off when playing quite intensive games like Fallout 4 and Max Mad. It hasn't turned off when playing low games like Age of Empires and such (although I haven't really played them long enough to find out).
It usually happens when the game starts to get a bit graphically intense (e.g Overlooking the entire map or when close to something that has to render in quite great detail (e.g it turns off when I'm very close to a very large, detailed tree on fallout 4). I've also tried turning the settings down on fallout to the lowest settings but it still happens
I've actually found a specific place in fallout where it happens. Its near a extremely big,detailed tree about 4 times the size of the character and if I basically strafe around it, the computer will turn off/restart after a couple minutes. I've also noticed that before the computer turns off, the game starts to micro stutter yet remains around 55 - 60fps (but feels around 20fps).
I've had a look around on the internet and the general conscious seems to be either problems with heating, the CPU, PSU or the GPU which doesn't really narrow it down at all..
I don't know how to figure out what part is causing the problem without replacing them individually and performing a test.
I've tried a memtest and I found no errors. I've monitored my temperature and it doesn't go to any dangerous levels when it happens. I've also made sure everything is plugged in correctly and cleaned the system so that there's no dust.
Sometimes it restarts and sometimes it just shuts down. However, when it does shut down I can still hear the fans running. I have to hold in the power button to turn the rest of the computer off then I can turn it back on again.
Any idea on how I can tackle this issue without having to manually replace each part till it stops happening?
Specs -
GTX 770
AMD FX-8350
Cooler Master 212 EVO
Corsair Builder Series CXM 600W
Patriot 8GB 1600MHz
edit: I've only just realized I only started having this issue around a month after installing windows 10. I've had this computer for almost 2 years and its been pretty much flawless. Is there a chance this could be a software issue?
It usually happens when the game starts to get a bit graphically intense (e.g Overlooking the entire map or when close to something that has to render in quite great detail (e.g it turns off when I'm very close to a very large, detailed tree on fallout 4). I've also tried turning the settings down on fallout to the lowest settings but it still happens
I've actually found a specific place in fallout where it happens. Its near a extremely big,detailed tree about 4 times the size of the character and if I basically strafe around it, the computer will turn off/restart after a couple minutes. I've also noticed that before the computer turns off, the game starts to micro stutter yet remains around 55 - 60fps (but feels around 20fps).
I've had a look around on the internet and the general conscious seems to be either problems with heating, the CPU, PSU or the GPU which doesn't really narrow it down at all..
I don't know how to figure out what part is causing the problem without replacing them individually and performing a test.
I've tried a memtest and I found no errors. I've monitored my temperature and it doesn't go to any dangerous levels when it happens. I've also made sure everything is plugged in correctly and cleaned the system so that there's no dust.
Sometimes it restarts and sometimes it just shuts down. However, when it does shut down I can still hear the fans running. I have to hold in the power button to turn the rest of the computer off then I can turn it back on again.
Any idea on how I can tackle this issue without having to manually replace each part till it stops happening?
Specs -
GTX 770
AMD FX-8350
Cooler Master 212 EVO
Corsair Builder Series CXM 600W
Patriot 8GB 1600MHz
edit: I've only just realized I only started having this issue around a month after installing windows 10. I've had this computer for almost 2 years and its been pretty much flawless. Is there a chance this could be a software issue?