Random System Crash on Ryzen 5 1600x

Sho Co2

Commendable
Oct 8, 2016
34
0
1,530
Recently purchased a Ryzen 5 1600x as an upgrade from my Fx-4300 and so far its working pretty good. It was working fine for about a week or 2 now and all of a sudden today it crashed twice in the middle of gaming and fiddling with blender. My cpu temps seemed to be fine and both applications shouldn't be really doing any intense work so I'm not sure what the problem is. I currently have a GA-AB350 Gaming 3 motherboard, and 16gb or Trident Z RGB 3000mhz as well as a Xigmatek Taros 500W (not popular, but it was an alternative to the corsair cx500w that was out of stock and works fine). As I mentioned earlier, this was all working fine for a good week or 2 and it just happened today twice. I'm going to update my BIOS after this and see what happens to my system.
 

Sho Co2

Commendable
Oct 8, 2016
34
0
1,530


I currently aren't running an overclock on my CPU, also I'm running a GTX1060 3gb ZOTAC mini
 

Sho Co2

Commendable
Oct 8, 2016
34
0
1,530
Another weird thing I realized is that after the second time the system black screened and shutdown itself, the bios was partially reset since my XMP profile was disabled aswell as my RGB profile to the default, since my PC was running the default red instead of the color shift mode that I changed it to I was able to tell the RGB profile has been reset.
 

Sho Co2

Commendable
Oct 8, 2016
34
0
1,530


Running the ram at 3000mhz via xmp profile was working fine for the past week tho.. could it just randomly stop working?
 

Sho Co2

Commendable
Oct 8, 2016
34
0
1,530


In an XMP profile it automatically sets the required voltage, its an automatic process so it adjusts all the settings for me, but I'll try disabling XMP profile if a crash occurs one more time, just updated my BIOS to F7 and going to see how it works out
 

Sho Co2

Commendable
Oct 8, 2016
34
0
1,530


Checked the event viewer and I have 3 Event 41 Kernel power errors... I never experienced a crash or shutdown prior to today so I'm not sure why theres an error listed for the 16th, but the other 2 seem to be 15-20min off of when the black screen actually occured