F5F Stay Refreshed Hardware Desktop Starts briefly then restarts repeatedly in a cycle

Starts briefly then restarts repeatedly in a cycle

Starts briefly then restarts repeatedly in a cycle

X
xFqtal_
Senior Member
670
12-27-2017, 02:25 PM
#1
Hello, I've noticed a few threads that seem a bit off, so I thought I'd post my own concerns. I'm trying to figure out if the problem lies with the power supply unit, which is one of the newer components in my setup. I know it should be able to handle the power needs of what I have installed. Whenever I turn on the machine in the morning or after work, it starts up but quickly shuts down within five seconds. The only code on my motherboard is 00, which the manual says isn't used. I've tried different fixes, but nothing seems to work consistently. After clearing the CMOS, which initially made me suspect a BIOS change, it still happens even without altering the BIOS (except enabling the M.2 drive). Clearing the CMOS doesn't always resolve it.

As if this wasn't confusing enough, I compare it to a car engine: it won't start cold, but once it's running, it works fine. You can turn it off and back on repeatedly, and it should start again if the engine is still warm. For my PC specs: - PSU: EVGA Supernova 850 G2 - Motherboard: Asus Maximus VII Ranger - CPU: Intel I7 4790K - RAM: Two 8GB sticks from Corsair (different models tried) - GPU: GTX 1070 Ti and an RTX 2070S - OS: Windows 10 64-bit

Anything else you need? I really appreciate your help. This computer has been a source of frustration for three years now, with most issues I've fixed, but this one has left me puzzled.
X
xFqtal_
12-27-2017, 02:25 PM #1

Hello, I've noticed a few threads that seem a bit off, so I thought I'd post my own concerns. I'm trying to figure out if the problem lies with the power supply unit, which is one of the newer components in my setup. I know it should be able to handle the power needs of what I have installed. Whenever I turn on the machine in the morning or after work, it starts up but quickly shuts down within five seconds. The only code on my motherboard is 00, which the manual says isn't used. I've tried different fixes, but nothing seems to work consistently. After clearing the CMOS, which initially made me suspect a BIOS change, it still happens even without altering the BIOS (except enabling the M.2 drive). Clearing the CMOS doesn't always resolve it.

As if this wasn't confusing enough, I compare it to a car engine: it won't start cold, but once it's running, it works fine. You can turn it off and back on repeatedly, and it should start again if the engine is still warm. For my PC specs: - PSU: EVGA Supernova 850 G2 - Motherboard: Asus Maximus VII Ranger - CPU: Intel I7 4790K - RAM: Two 8GB sticks from Corsair (different models tried) - GPU: GTX 1070 Ti and an RTX 2070S - OS: Windows 10 64-bit

Anything else you need? I really appreciate your help. This computer has been a source of frustration for three years now, with most issues I've fixed, but this one has left me puzzled.

Y
Ygr1k
Member
218
01-02-2018, 11:46 PM
#2
I've experienced this with my Rampage V Extreme. Your remark about "cold/warm starting" fits it best. It took a few CMOS resets for the PC to finally boot. I believe the problem stemmed from memory issues. My G.Skill setup struggled at higher speeds but worked fine at the base JEDEC rate. Likely, it's a memory or training concern. I resolved it by setting the memory to run at the base JEDEC speed—2133MHz for DDR4, which would be 1333MHz on a DDR3 platform.
Y
Ygr1k
01-02-2018, 11:46 PM #2

I've experienced this with my Rampage V Extreme. Your remark about "cold/warm starting" fits it best. It took a few CMOS resets for the PC to finally boot. I believe the problem stemmed from memory issues. My G.Skill setup struggled at higher speeds but worked fine at the base JEDEC rate. Likely, it's a memory or training concern. I resolved it by setting the memory to run at the base JEDEC speed—2133MHz for DDR4, which would be 1333MHz on a DDR3 platform.

K
kenton12
Member
204
01-03-2018, 02:16 AM
#3
Thanks for reaching out. Adjusting the memory to 1333MHz hasn't fixed the issue, but I'm willing to experiment to find a solution.
K
kenton12
01-03-2018, 02:16 AM #3

Thanks for reaching out. Adjusting the memory to 1333MHz hasn't fixed the issue, but I'm willing to experiment to find a solution.

_
112
01-08-2018, 12:24 PM
#4
It's disappointing to hear. Are you aware of the BIOS version? An update might resolve some problems. You mentioned enabling the M.2 drive in your request, but did the system start up normally before that? There could have been booting issues with M.2/NVMe drives on the Z97 platform, though I'm not entirely certain.
_
_ReflexLegend_
01-08-2018, 12:24 PM #4

It's disappointing to hear. Are you aware of the BIOS version? An update might resolve some problems. You mentioned enabling the M.2 drive in your request, but did the system start up normally before that? There could have been booting issues with M.2/NVMe drives on the Z97 platform, though I'm not entirely certain.

D
Darkstar_TV
Junior Member
48
01-12-2018, 06:25 PM
#5
I need to attempt that because I haven’t activated the feature twice before—once during setup and again recently when I reset the CMOS. My main concern is the boot drive, so I’m hoping it isn’t the cause. Regarding the BIOS, it’s version 26.01 released on March 26, 2015. It’s been challenging to locate updates for this specific board model, and I’m unsure if it’s current. EDIT: Even after making no changes to the BIOS, the issue persists. EDIT2: Could this be related to a faulty CMOS battery cell?
D
Darkstar_TV
01-12-2018, 06:25 PM #5

I need to attempt that because I haven’t activated the feature twice before—once during setup and again recently when I reset the CMOS. My main concern is the boot drive, so I’m hoping it isn’t the cause. Regarding the BIOS, it’s version 26.01 released on March 26, 2015. It’s been challenging to locate updates for this specific board model, and I’m unsure if it’s current. EDIT: Even after making no changes to the BIOS, the issue persists. EDIT2: Could this be related to a faulty CMOS battery cell?