Is there a method to verify or inspect the motherboard for faults?
Is there a method to verify or inspect the motherboard for faults?
Hello everyone.
I’m facing an issue with my PC that’s really frustrating. It keeps restarting randomly, sometimes multiple times in an hour, other times it won’t restart at all for hours. I’ve tried explaining what I was doing, but nothing seems to work yet.
My PC is mainly used in my shop for managing stock, sending emails, preparing offers, and printing documents. I don’t think it’s under heavy stress or intensive use.
Here’s the hardware setup:
- Motherboard: ASUS Z370-P
- CPU: Core i7-8700
- RAM: 16GB (1 slot) Kingston PC-2666 DDR43 RAM
- Hard drive: Crucial Mx500 1TB M.2 SSD
- VGA: Built-in motherboard
Power supply: Thermaltake Touch Power Grand 850W full modular.
I’ve tried several fixes:
1. Removed all connected devices except the wireless keyboard and mouse.
2. Updated BIOS and changed the battery.
3. Installed a new SATA SSD with Windows installation, then removed the M.2 SSD.
4. Swapped RAM to a new one in the same slot and tested all slots.
5. Used an external VGA (RTX2070).
6. Replaced CPU and installed a new Core i5-8400.
7. Changed all connections on the case front panel, reset switches, and power switch.
8. Removed all fans except the CPU fan.
After trying everything, I tested my removed hardware on another PC, and it worked perfectly. I’m 100% confident the problem is now limited to the motherboard.
My main question is: how can I troubleshoot the motherboard issue? Is there a way to repair a damaged board without buying a new one? Any advice would be greatly appreciated.
Thanks for your help.
It's difficult to provide an answer. When the system stops abruptly without displaying an error screen, it appears to encounter a triple hardware exception. Typically, during a fault, a stack unwinding occurs to reach a minimal function for recovery. However, once a certain failure point is reached, further operations may worsen data corruption on storage devices. To protect the device, an immediate reset is initiated.
Debugging a motherboard often demands specialized, expensive equipment—often costing hundreds of thousands of dollars. A useful approach is to examine Linux's behavior during such failures. You might consider adding a second hard drive, such as a standard SATA unit, and disabling the primary one, then installing Linux on the spare. Alternatively, using a bootable distribution like KUbuntu allows you to run the system entirely in RAM without installation, which can be initiated remotely via a button.
Within Linux, commands like "dmesg --follow" can display live logs, helping identify errors. If an exception arises, it usually disappears quickly; however, monitoring with a web browser or similar tool may capture the issue. Without a dedicated console, the message vanishes instantly, suggesting you might need to use a video camera to record the log.
If all else fails, the problem could stem from the motherboard itself. Ground loops, improperly secured mounting points, or incorrect alignment can cause instability. Temperature fluctuations are another concern—thermal imaging can reveal hotspots, though correcting them may be costly and complex.