Using the reset function caused permanent damage to your system, but resetting the CMOS restored normal operation.
Using the reset function caused permanent damage to your system, but resetting the CMOS restored normal operation.
Hey, today I wrapped up my first real build. The storytelling part is skipped if you don’t mind. I think my initial post here was about swapping a new power supply into a pre-built HP I bought for my GTX1660. Eventually, I found a nearly matching PSU from their gaming lineup that matched the motherboard, case, and other parts. Since then, I upgraded to a Ryzen 5 2600, added two SSDs, another HDD, and more RAM. That old Pavilion kept running smoothly. But when the 2600 CPU came along, heat issues started and frame rates dropped noticeably. A few days later, I finally installed a standard ATX motherboard, PSU, and case. Even though it seemed like the right choice from the start, I ended up building a fully custom tower and am really happy with it.
Later at home, I ran into some Windows activation problems. After adjusting a few settings, I pressed the reset button on my case and expected it to shut down. But the fans and power LED stayed on. After a couple minutes, I forced it off by holding the power button and then turned it back on. My MSI board had EZ Debug LEDs, and the CPU was lit. The machine just ran fans and lights. No way to explain why it stopped working at all. After reseating the RAM, I tried clearing the CMOS and it worked! I unplugged the reset switch right away. Then I went straight to the computer and wrote this down on the machine that was acting up. My biggest question is… why did the reset switch fail to fix it? And why did clearing the CMOS make a difference? If this is the simplest thing you’ve ever seen, please explain.
Maybe the front panel reset switch is wrongly wired? Keep in mind that front panel connectors on different motherboards can vary, so look at the schematic in your motherboards manual, and see if it is wired correctly. Another possibilty is that the reset button wire is broken and there is a short somewhere. Or maybe that you downloaded the bloatware that motherboard manufacturer include, and that was doing something with the BIOS settings while you promptly cut the power to the pc, bricking the bios. That is why you shouldn't use them. Either way, windows has a built in restart button, so I would just use that, no more worries.
I've encountered similar problems before with Fastboot in the BIOS. When it's active, my system fails to restart correctly. I usually have to follow a series of steps—disconnecting the power supply, waiting a bit, then reconnecting it—which often resolves the issue. I also had to clear the CMOS once for a fix. Turning it off and back on now works perfectly.
The issue reappeared during another reset attempt. I'll try to see how long it works before giving up.
Updated: After finally accessing the BIOS, I turned off fast boot. Then I managed to start Windows properly, and completed three tests. Restarted software, shut it down, and powered off the hardware (using the power button). Each time I managed to boot the machine. It seems disabling FastBoot might have helped. Until now, I'm staying alert—those four EZ Debug lights will be a nuisance, and I wish this issue never happens again!