I have the following issue - a few seconds after turning on the computer, it automatically powers down (after the BIOS POST checks, in a moment when Windows should start booting). Then when I turn it on again, it boots and works normally.
The strange thing is, that this issue happens only from time to time - my feeling is that it happens more often when I turn on the computer in the morning (when the computer is turned off during the night). But also when I turn off and on the computer during the day, it sometimes happen: based on my observations about 2-3 times during 10 power-ons. It has never happened two times in a row (yet).
I have NOT noticed this happening when rebooting the computer, only when powering on.
All the components in the computer are entirely new, I just put them together last week:
Motherboard: GIGABYTE Z97X-Gaming 3 (Bios version updated from F3 to F5)
RAM: Crucial 16GB KIT DDR3 1600MHz CL8 Ballistix Tactical LP (PC3-12800, CL8-8-8-24, 1.35V)
CPU: Intel Core i5-4690K 3.5GHz @3.9GHz (set to 3.9GHz automatically by BIOS) with SCYTHE Ashura cooler
Graphics: GIGABYTE N770OC-2GD
PSU: Corsair RM750
SSD: Samsung 840 EVO Series Basic 250GB
HDD: Seagate Barracuda 7200.14 3000GB
Case: FRACTAL Define R4 Black Pearl
OS: Windows 8.1
My first suspicion was that it could be caused by the RAMs. To explain - I first noticed the issue one day after putting the PC together when changing the default 9-9-9-24 1333Mhz 1.35V setting to XMP profile1 (8-8-8-24 1600Mhz 1.35V). But when doing some tests, the issue also occurs on the default profile (maybe less often? but could be just me feeling). I also tried putting the RAM sticks in different DIMM slots a using only one RAM stick at a time with no change.
Loading the bios optimized defaults also did not help.
When using the fast boot (or ultra fast boot) option in BIOS, the issue also happens from time to time, just the computer gets powered off almost immediately after start.
I am pretty sure that overheating is not an issue here - all the coolers are working fine and the temperatures are good even after hours of gaming.
Any idea what could be the issue? Anything that I could try to troubleshoot it??
The strange thing is, that this issue happens only from time to time - my feeling is that it happens more often when I turn on the computer in the morning (when the computer is turned off during the night). But also when I turn off and on the computer during the day, it sometimes happen: based on my observations about 2-3 times during 10 power-ons. It has never happened two times in a row (yet).
I have NOT noticed this happening when rebooting the computer, only when powering on.
All the components in the computer are entirely new, I just put them together last week:
Motherboard: GIGABYTE Z97X-Gaming 3 (Bios version updated from F3 to F5)
RAM: Crucial 16GB KIT DDR3 1600MHz CL8 Ballistix Tactical LP (PC3-12800, CL8-8-8-24, 1.35V)
CPU: Intel Core i5-4690K 3.5GHz @3.9GHz (set to 3.9GHz automatically by BIOS) with SCYTHE Ashura cooler
Graphics: GIGABYTE N770OC-2GD
PSU: Corsair RM750
SSD: Samsung 840 EVO Series Basic 250GB
HDD: Seagate Barracuda 7200.14 3000GB
Case: FRACTAL Define R4 Black Pearl
OS: Windows 8.1
My first suspicion was that it could be caused by the RAMs. To explain - I first noticed the issue one day after putting the PC together when changing the default 9-9-9-24 1333Mhz 1.35V setting to XMP profile1 (8-8-8-24 1600Mhz 1.35V). But when doing some tests, the issue also occurs on the default profile (maybe less often? but could be just me feeling). I also tried putting the RAM sticks in different DIMM slots a using only one RAM stick at a time with no change.
Loading the bios optimized defaults also did not help.
When using the fast boot (or ultra fast boot) option in BIOS, the issue also happens from time to time, just the computer gets powered off almost immediately after start.
I am pretty sure that overheating is not an issue here - all the coolers are working fine and the temperatures are good even after hours of gaming.
Any idea what could be the issue? Anything that I could try to troubleshoot it??