A motherboard that fails to boot can harm another system [Feedback and suggestions appreciated]
A motherboard that fails to boot can harm another system [Feedback and suggestions appreciated]
Hello, glad you can make it.
So here is what we're dealing with.
Your little brother's computer is not booting!
MB: Gigabyte GA-970A-UD3
CPU: AMD (I'll have to edit this part when I find out the type)
GPU: GTX 770
HD: Western Digital 6TB
OS: It was windows 10
So you start the computer... and nothing, okay...
Lets try mashing del, F2, F1, all the keys.
Nothing...
Okay... lets start removing ram sticks and changing orientation
Nothing...
Graphics Card? Removed...
Nothing...
All the connections firmly connected... yep.
Any visible signs of soot, or shortage... not a sign
Okay... off to Amazon to buy an AM3+ motherboard, a cheap ASRock 970M Pro3 will do.
Changing the parts, booting the computer, and we have BIOS great!
Enter the computer, backup data, all is well. Return computer to little brother.
Little brother texts... computer is not booting!
Strange... it was working a day ago
Repeat process again, and nothing...
Time to reset CMOS, and that does bring you back into boot. But when the computer shutdown and turned back on again, no boot...
Maybe somethings wrong with Windows, lets install a random flavor of linux Deb12 will do for no particular reason.
Deb12 installed, restarted, no boot.
New motherboard so old component failing?
Motherboard needs update? Flash the bios?
Maybe it the memory?
In the meantime little brother is getting impatient and decides to buy new computer... cool now a new toy for us to fix and convert to a home lab.
While I try different things, I'll document here.
When sharing a troubleshooting thread, it's important to provide detailed system specifications. List them clearly as follows:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
Include the age of the PSU along with its make and model.
If you reused the PSU from a previous build, it could be the reason.
I've discovered I was using incorrect terms; upon restarting, the system will load an OS but won't POST after reboot.
To provide Lutfij with the complete system details, here are the specifications:
CPU: AMD FX™-8350, 8-core processor at 4000MHz
CPU cooler: Cooler Master unit with fan
Motherboard: ASRock 970M Pro3 UEFI P1.60
RAM: Two Crucial Ballistix Sport modules, 1600Mhz, 9-9-9-24, 1.5V, 4GB
Storage: Western Digital 6TB drive
GPU: Nvidia GTX 770
Power supply: Seasonic Focus (model not confirmed)
Chassis: Fractal
Operating system: Debian 12
Monitor: MSI Monitor
The PSU is approximately six to seven years old.
Taking out the RAM sticks results in three long beeps. One RAM stick means no beeps. I plan to perform another CMOS reset and then flash a new BIOS.
Flash bios data; initial outcomes positive
After a complete system shutdown, it restarted, system logged in and booted...
Continued testing, power will remain off for three minutes.
A multimeter is prepared to measure battery voltage should the system fail to POST.
Removed battery
Reset CMOS
Tried to post, accessed BIOS and applied UEFI defaults (hoping it would help)
Powering off
Disconnected from power source
Reconnected to power
Powered on
Result: No post detected
Shutting down using power button
CMOS reset completed
Waiting about 15 seconds before reaching the UEFI setup tool after reset
Saved changes and exited
GRUB loaded successfully
First restart (checking if power loss during boot is causing the problem or a full reboot)
Restarted successfully
Second restart
GRUB launched again
Five beeps from MB speaker – this time new
Third restart attempted to recreate the five beeps
One long beep – this was different
Fourth restart
No one long beep
GRUB started without any five beeps
System power down initiated – no disconnection from power
Waiting 30 seconds
Power on
GRUB booted again
System power down again – no disconnection from power
Waiting 60 seconds
Power on
Waiting 60 seconds
No POST, no BIOS/UEFI detected
Strangely odd...
Multiple consecutive restarts didn’t cause issues returning to Debian’s login screen after GRUB loaded.
A short shutdown of 30 seconds is acceptable, but after a minute it stops the system from accepting a post.
Interesting to observe some patterns
CMOS battery was removed during all these tests; the machine will remain in this inactive state for 10–30 minutes while I prepare dinner and check if it still appears unresponsive