Pink squares in bios, and will boot after windows install, but goes into boot loop.

May 19, 2018
1
0
10
It started when I was playing games (for a good few hours) and my monitor started flickering, then went black and a few seconds later my computer restarted. It booted like normal, I gave it a few minutes before I started playing again, and it did the same thing. It went into a boot loop, opened the bios and saw lines of pink squares. All of the squares are behind the letters, so it can't be a monitor issue (right). I decided to overlook it, while the hard drive, and reinstall windows. First boot into fresh windows goes great for a few minutes until it randomly rebooted, and loaded into windows again. Rebooted once more and now no longer boots into windows unless I reinstall it only to be on the homescreen, and able to use the internet until it randomly reboots and the cycle continues. I just replaced the power supply with a brand new one because, I sent it to get diagnosed and was told the was the issue, but still has the same issue. I then bought a new motherboard. I started reinstalling windows once again, and was able to boot into it just fine. It starts to install updates gets to a certain spot then reboots out of nowhere. Tried disabling restart after system failure, and low resolution mode to no avail, but able to get into safe mode just fine. I done want to call it quits on this machine but will ignore have too.

Specs:
AMD AM3+ FX-832 8 cores @ 3.5 ghz
WD Desktop perf. 1 TB HDD
Asus Radon R7 370 4gb Strip gaming edition
Asus M5A78L-M plus/usb3
EVGA 500W 80+ Bronze certified ATX
PNY 8GB DDR3 1600 C11 1 5V DIMM
 
Solution
Please add your systems' specs to your post with make and model#'s of the various parts.
Your post was moved to SYSTEMS as you have a hardware issue and not a Win10 issue, as evidenced by the graphics anomalies in the Bios.
Thank you.
Please add your systems' specs to your post with make and model#'s of the various parts.
Your post was moved to SYSTEMS as you have a hardware issue and not a Win10 issue, as evidenced by the graphics anomalies in the Bios.
Thank you.
 
Solution