F5F Stay Refreshed Hardware Desktop Hardware issue detected. My computer shuts down after a moment and restarts on its own.

Hardware issue detected. My computer shuts down after a moment and restarts on its own.

Hardware issue detected. My computer shuts down after a moment and restarts on its own.

S
Sweg_Patato
Junior Member
23
10-05-2017, 01:21 AM
#1
I have a GIGABYTE GA-H110M-DS2 board, an Intel i3 7th gen chipset, two 8 GB RAM modules, a graphics card, and two storage drives — one 250 GB (main) and another 1 TB. My power source is a Cooler Master MasterWatt Lite 600W. About six months ago, my system experienced some problems until I replaced the thermal paste, after which it operated smoothly for two months. However, the next morning after powering it on, the PC shut down after just one second, then rebooted itself briefly before shutting off again, repeating this cycle continuously until manually turned off. The issue began suddenly and has persisted since. Previously it would restart after a delay, but now it keeps cycling every second. I've already swapped the CPU and the problem persists. Please help identify what's happening. Thanks! PC.mp4
S
Sweg_Patato
10-05-2017, 01:21 AM #1

I have a GIGABYTE GA-H110M-DS2 board, an Intel i3 7th gen chipset, two 8 GB RAM modules, a graphics card, and two storage drives — one 250 GB (main) and another 1 TB. My power source is a Cooler Master MasterWatt Lite 600W. About six months ago, my system experienced some problems until I replaced the thermal paste, after which it operated smoothly for two months. However, the next morning after powering it on, the PC shut down after just one second, then rebooted itself briefly before shutting off again, repeating this cycle continuously until manually turned off. The issue began suddenly and has persisted since. Previously it would restart after a delay, but now it keeps cycling every second. I've already swapped the CPU and the problem persists. Please help identify what's happening. Thanks! PC.mp4

A
AliensFour
Junior Member
13
10-05-2017, 06:14 AM
#2
Consider removing the RAM and reinstalling it. If you have an extra battery, swap it in.
A
AliensFour
10-05-2017, 06:14 AM #2

Consider removing the RAM and reinstalling it. If you have an extra battery, swap it in.

M
MrKryp
Senior Member
643
10-05-2017, 08:00 AM
#3
I’ve already checked the RAM and swapped out the CMOS battery, but I’m out of replacements. I’ll purchase a fresh one and check if it resolves the issue. Thanks!
M
MrKryp
10-05-2017, 08:00 AM #3

I’ve already checked the RAM and swapped out the CMOS battery, but I’m out of replacements. I’ll purchase a fresh one and check if it resolves the issue. Thanks!

T
Tracyy14
Member
133
10-05-2017, 02:12 PM
#4
I've already attempted to re-seat the RAM and changed both the old and new CMOS battery, but I don't have a backup. I'll purchase a replacement battery and check if that resolves the issue. Thanks!
T
Tracyy14
10-05-2017, 02:12 PM #4

I've already attempted to re-seat the RAM and changed both the old and new CMOS battery, but I don't have a backup. I'll purchase a replacement battery and check if that resolves the issue. Thanks!

E
Emoney1018
Junior Member
19
10-16-2017, 02:12 AM
#5
It seems like the RAM might be having problems. Try removing it, cleaning dust, and repositioning it. This issue appears to be related to memory retraining and failure. Unless a RAM stick was damaged, it shouldn’t be behaving this way.
E
Emoney1018
10-16-2017, 02:12 AM #5

It seems like the RAM might be having problems. Try removing it, cleaning dust, and repositioning it. This issue appears to be related to memory retraining and failure. Unless a RAM stick was damaged, it shouldn’t be behaving this way.

S
Sheikrik
Senior Member
441
10-22-2017, 01:49 PM
#6
I've already checked the RAM; removing both cables and using just one still gives the same result. I also cleaned the contacts prior to testing.
S
Sheikrik
10-22-2017, 01:49 PM #6

I've already checked the RAM; removing both cables and using just one still gives the same result. I also cleaned the contacts prior to testing.

W
Wapr
Member
56
10-24-2017, 02:07 AM
#7
Here’s a rephrased version of your text:

The situation you’re facing isn’t easily ruled out unless you try something unconventional. The next more probable causes are less likely: a BIOS flash failure, which I’ve encountered with certain Gigabyte boards where the system mistakenly re-flashes memory during what should be a firmware update. That kind of issue seems to have faded away since the Core2Duo era.

Another possibility is PSU damage. This is rare but worth investigating. Make sure all power cables are properly seated on the motherboard, ATX12V, and any PCIe connections. If the power supply has been compromised, it often won’t come back on—sometimes it powers up briefly before shutting down completely. In contrast, a BIOS flash issue typically keeps the screen lit during the attempt, then either spins up after a short delay or fails to power on at all.

If simply reapplying the CPU paste resolved the problem, it’s likely something happened afterward. Checking for external factors like spilled water or other contaminants can help, but if you can’t find any obvious signs and still can’t get the system up, you’ll need to disassemble components one by one to pinpoint the exact cause. Not everyone has access to replacement parts for such detailed testing.
W
Wapr
10-24-2017, 02:07 AM #7

Here’s a rephrased version of your text:

The situation you’re facing isn’t easily ruled out unless you try something unconventional. The next more probable causes are less likely: a BIOS flash failure, which I’ve encountered with certain Gigabyte boards where the system mistakenly re-flashes memory during what should be a firmware update. That kind of issue seems to have faded away since the Core2Duo era.

Another possibility is PSU damage. This is rare but worth investigating. Make sure all power cables are properly seated on the motherboard, ATX12V, and any PCIe connections. If the power supply has been compromised, it often won’t come back on—sometimes it powers up briefly before shutting down completely. In contrast, a BIOS flash issue typically keeps the screen lit during the attempt, then either spins up after a short delay or fails to power on at all.

If simply reapplying the CPU paste resolved the problem, it’s likely something happened afterward. Checking for external factors like spilled water or other contaminants can help, but if you can’t find any obvious signs and still can’t get the system up, you’ll need to disassemble components one by one to pinpoint the exact cause. Not everyone has access to replacement parts for such detailed testing.

R
RockySD
Junior Member
12
10-24-2017, 05:58 AM
#8
Sure, I'm ready to help. Enjoy your day!
R
RockySD
10-24-2017, 05:58 AM #8

Sure, I'm ready to help. Enjoy your day!

C
Cyanstrophic
Senior Member
668
10-24-2017, 08:02 PM
#9
Occasionally adjusting RAM timings slightly can affect stability. Resetting the BIOS by clearing it usually resolves the issue, but only if there aren’t underlying hardware problems. Avoid removing the battery during this process; instead, wait a short time, then discharge the PSU’s capacitors before powering back on. After about ten minutes, reinsert the battery and restore power to test. It may take a moment or two for the system to respond after resetting. If your RAM was near the optimal range, it might not work as expected, leading to boot failures. XMP profiles aren’t always reliable and can sometimes cause issues.
C
Cyanstrophic
10-24-2017, 08:02 PM #9

Occasionally adjusting RAM timings slightly can affect stability. Resetting the BIOS by clearing it usually resolves the issue, but only if there aren’t underlying hardware problems. Avoid removing the battery during this process; instead, wait a short time, then discharge the PSU’s capacitors before powering back on. After about ten minutes, reinsert the battery and restore power to test. It may take a moment or two for the system to respond after resetting. If your RAM was near the optimal range, it might not work as expected, leading to boot failures. XMP profiles aren’t always reliable and can sometimes cause issues.

H
HiddenCat
Junior Member
3
10-24-2017, 09:10 PM
#10
Thank you for your prompt response. I appreciate the details and will proceed.
H
HiddenCat
10-24-2017, 09:10 PM #10

Thank you for your prompt response. I appreciate the details and will proceed.