Before I post anything else, I assume my complete specs would be helpful:
This is my first ever build which I put together over the weekend of 2013-11-15. Initially there were no issues.
However, soon after the build was complete (around early December) the system randomly turned off and turned back on. The issue disappeared and I thought no more about it.
Just before Christmas the system did it again but this time repeatedly power cycled and would not boot. I stripped the whole thing down and tested it as I put each component in and the system was fine. No issues.
I read somewhere that faulty q-connectors my have cause the problem so I took them out.
I thought the problem was gone until about an hour ago (of which I have been searching). The system now will not boot and is recursively stuck in a phase of powering on for around a second, dropping power completely, and then powering on again before just cutting out.
I've watched the debug LED output and the system always cuts after the value 0x15 is shown. The manual (which is avalble here) states that this represents "Early North Bridge Initialization" (page 1-37 of the manual).
I've Googled around but not been able to find anything. I'm sure after I go back to my machine after conducting this it'll likely power-on but that doesn't detract from the fact that there is an issue.
I'm new to hardware so I'm not sure what could be causing this. Anyone that can help?
UPDATE: After a power lost the system can only be restarted by removing the RAM, swapping the BIOS, and then turning on leaving the side panel off.
UPDATE #2: After my last discovery I have left the side panel fan unplugged. And this time my machine did not power down. Could a molex connector cause a short and shutdown the system? I'm very much a software person and decided to build a machine to learn these things.
■My case is a Zalman Z11 Plus,
■Motherboard is a MSI Z77-MPower (LGA 1155 socket),
■I have an Intel Core i5-3570K CPU (this is not over-clocked in anyway),
■My RAM is two 4 GB sticks of Corsair's Vengeance (DDR3 1866 MHz) running in dual channel; again no modifications have been made to voltages,
■For graphics I have two NVIDIA GTX 770s with 2GB of dedicated memory from MSI (these are running in SLI),
■The system is powered by a Corsair AX860i 860W power supply, and
■I have a Creative Sound Blaster Z soundcard.
This is my first ever build which I put together over the weekend of 2013-11-15. Initially there were no issues.
However, soon after the build was complete (around early December) the system randomly turned off and turned back on. The issue disappeared and I thought no more about it.
Just before Christmas the system did it again but this time repeatedly power cycled and would not boot. I stripped the whole thing down and tested it as I put each component in and the system was fine. No issues.
I read somewhere that faulty q-connectors my have cause the problem so I took them out.
I thought the problem was gone until about an hour ago (of which I have been searching). The system now will not boot and is recursively stuck in a phase of powering on for around a second, dropping power completely, and then powering on again before just cutting out.
I've watched the debug LED output and the system always cuts after the value 0x15 is shown. The manual (which is avalble here) states that this represents "Early North Bridge Initialization" (page 1-37 of the manual).
I've Googled around but not been able to find anything. I'm sure after I go back to my machine after conducting this it'll likely power-on but that doesn't detract from the fact that there is an issue.
I'm new to hardware so I'm not sure what could be causing this. Anyone that can help?
UPDATE: After a power lost the system can only be restarted by removing the RAM, swapping the BIOS, and then turning on leaving the side panel off.
UPDATE #2: After my last discovery I have left the side panel fan unplugged. And this time my machine did not power down. Could a molex connector cause a short and shutdown the system? I'm very much a software person and decided to build a machine to learn these things.