PC Rebooting after playing demanding games

yertho77

Prominent
Nov 25, 2017
13
0
510
Hi all, I recently built my gaming computer two months ago and I just started playing some demanding games. I started with Fallout 4 and after a few minutes of being in a certain area, my monitor would turn black and restart my PC. I then tried testing this with Rust, and after a couple of minutes, it would do the same thing. I don't know which part is the culprit. Thank you for your help.

PC Parts:

Ryzen 5 1600 @ 3.2 GHz
Asrock AB350M Pro4
WD Blue 1TB HDD
MSI Gaming X RX580
Seasonic Focus Plus 650w 80+ Gold Power Supply
G.Skill Ripjaws V 1x8gb DDR4-2666 RAM
 
Thats normally symptoms of a bad or under powered power supply, but since yours is a good brand with plenty of power in this case likely not. My next though is unstable RAM either system or on the GPU. I suggest you run memtest to check the RAM, if thats all OK run OCCT and run the various CPU and GPU tests and see if you can narrow it down.
 
have you tried lowering the settings for the graphics card and any other effects tabs in any of the games that you have a problem with... make notes for each item you alter it might help you narrow down what individual setting could be the cause of your problem.
 

yertho77

Prominent
Nov 25, 2017
13
0
510
I checked Event Viewer a while ago during my crashes on Fallout 4 before starting my memory checks on MEMTEST and got an error: Bugcheck involving MEMORY.dmp. could that narrow things down to my gpu or RAM?

Edit: I could try posting the full reboot error once I finish this memory test.
 

yertho77

Prominent
Nov 25, 2017
13
0
510


Oh, forgot to update..I finished memtest yesterday and got no errors within 4 passes.

Edit 1: Here is the error that came with the reboot:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xffffb38d1e5e4010, 0xfffff809aaf4f7e8, 0xffffffffc0000001, 0x0000000000000003). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: a999ef20-6515-496b-801b-593b954a7b98.

Based on what I searched, this seems to be an issue with video drivers, so I guess i'll start checking there..