This is the second time it happened. I've recently built a new PC for the first time alone. Every part I got is brand new, I will list them below. Just a few minutes ago, I was working on something for school and I was listening to music and doing some research, and the screen suddenly went black and my speakers started buzzing. Then, it went to blue "Your PC ran into a problem and needs to restart" screen on Win 10. The only thing I had open was Chrome with about 10 tabs open because of my research. I checked the temperatures right after the PC rebooted (which was very quick), nothing seemed too much out of the ordinary. I thought that the processor might have been the problem, but it was around 27 degrees, max being 35. The only thing that seemsed weird was that the SSD was hotter than the HDD, but I guess that doesn't have to mean much.
Here are the components:
-AMD Ryzen 2200G
-AM4 ASUS PRIME A-320M-K
-2x DIMM DDR4 4GB 2400MHz Kinston Fury Black CL15
-SSD SATA3 120 GB SiliconPower Slim S55 550/420MB/s
-HDD SATA3 2'5" 7200 500GB WD Black
Previous time this happened the screen went just black. I'm a gamer too, but when I play games, nothing bad happens.
Also, I have Windows 10 Pro, and my motherboard is running on an older version of BIOS (3401) even though I have a Ryzen 2000 series processor. I requested for the BIOS to be upgraded before they delivered it to me and they didn't do it, but the system seemed to be running smoothly regardless. Could this have caused the problem?
Here are the components:
-AMD Ryzen 2200G
-AM4 ASUS PRIME A-320M-K
-2x DIMM DDR4 4GB 2400MHz Kinston Fury Black CL15
-SSD SATA3 120 GB SiliconPower Slim S55 550/420MB/s
-HDD SATA3 2'5" 7200 500GB WD Black
Previous time this happened the screen went just black. I'm a gamer too, but when I play games, nothing bad happens.
Also, I have Windows 10 Pro, and my motherboard is running on an older version of BIOS (3401) even though I have a Ryzen 2000 series processor. I requested for the BIOS to be upgraded before they delivered it to me and they didn't do it, but the system seemed to be running smoothly regardless. Could this have caused the problem?