[SOLVED] Functional machine deteriorates through weird login screen issue, to slow BIOS boot phase, to boot looping.

SquishousKnid

Reputable
Oct 16, 2015
4
0
4,520
MB: MSI Z77A-G45
CPU: Intel i5-3570K
PSU: 500W Thermaltake
RAM: G.Skill 4x4GB 2133MHz
Storage: Samsung 840 EVO 250GB SSD, Seagate 1TB HDD, Seagate 2TB HDD
OS: Win10 64bit

TL;DR: Functional machine experienced weird login screen problem, followed by very slow BIOS boot (but normal BIOS config menu), and is now looping through boot sequence, staying on for only 12 seconds, but successfully beeps if RAM is removed.

So, let me start with that this computer, despite its occasionally troubled history, a few mistakes and speeding tickets, was running fine, as per normal, 24 hours ago.

It was moved between houses several days before and has not had internet available since then due to ISP. Its most recent stress is having been pushed to its limits with SW Battlefront II. After Battlefront II was closed it was left to run. It was powered on when a local blackout took it offline. It is surge protected, and that protection did not trigger. It did not attempt to power on when power was restored as per configured.

When powered on first after the blackout, the first discrepancy noticed was that at the Win10 login, when clicking / entering past the first screen displaying the time, no login screen as such appeared. The background image zoomed and darkened and the time screen slid upward, but no profile image, or text field, or password reset button appeared, and only the few buttons in the bottom right remained. On rebooting, the BIOS was extremely slow to boot (a few minutes). Normally my MB displays B4, then A2 in the bottom right, before the branded splash - this time, it displayed B4 for some time, followed by 92, followed by A2, and the branded screen. Windows booted slowly, but presented the initial welcome screen normally, and the same login screen issue presented. Problem was consistent across restarts.

Startup repair and system file checker were run from a Win10 installation USB to no effect. System restore was unable to be run so as to see available points. BIOS setup was loaded, very slowly, but once operating ran fine, at full speed. No problems could be found therein. BIOS setup was again very slow on attempting to exit and restart the machine. A memory diagnostic was started from the Win10 USB and ran slowly, was left overnight, and got stuck about 22% of the way through test 4 of 15. The machine was restarted.

The machine now does not output any display, loops through booting staying on for only 12 seconds, does not beep in this time, but will issue three long beeps if it is booted without RAM, despite still losing power in this timeframe and then restarting. Machine was cleaned out, and devices reseated to no effect. All but CPU, fans, speaker and power button cables and such were disconnected, and boot attempted, to no effect and the same, boot loopy, no output, no beep except for when the RAM is out, result.

I don't suspect an MB short as the cabling nor the seating / shielding of the MB have changed recently, certainly not since it was last functional. I might suspect the PSU if this problem weren't first preceded by the weird login screen issue, and the super slow BIOS booting. I'm considering that the MB might be shot, or in the worst case, the CPU.

At this point, I'm a little fatigued and blinded by my proximity. I've worked through a few of the historical stickies on the topic. Questions, even little ones, and instruction are welcome, and I will endeavour to provide answers. I type now from my phone, so I'm sure I'll have missed including some detail.

Thanks!
 
Solution
Unbelievable. It spat the dummy on the memory config. (see my first thread for an adventure in that). Switching XMP off and letting the BIOS sit with default settings allows it now to tolerate the RAM, that it had tolerated fine before. Had to let it sit for a bit and hit it with fresh eyes. Thanks peeps!

SquishousKnid

Reputable
Oct 16, 2015
4
0
4,520
Unbelievable. It spat the dummy on the memory config. (see my first thread for an adventure in that). Switching XMP off and letting the BIOS sit with default settings allows it now to tolerate the RAM, that it had tolerated fine before. Had to let it sit for a bit and hit it with fresh eyes. Thanks peeps!
 
Solution