My new build seems to be misbehaving a bit.  
 
Form day one I get one beep on start up. There was conflicting information on Gigabites web site. One list says this means all OK the other say's there's an issue. 
There is a LED inside that always shows A0. 
I first bought 2 sticks of RAM 
Start up was fine with just the beep, then after a few weeks I'd get a blue screen and "with errors" 
Pressing reset and the computer would boot and run all day fine. 
 
I just added 2 more sticks of the exact same RAM and the "with errors" disappeared for first 3 boots. Now it is just a blue screen with no message. But the reset button fires it up just fine. 
Any clues of what I have obviously overlooked building this thing? 
 
Gigabyte Z97X-SOC ATX LGA1150 Z97
DDR3 PCI-E16 PCI-E8 XFIRE/SLI SATA3
USB3 HDMI DVI Motherboard 
 
Patriot Viper 3 8GB 2X4GB PC3-12800
DDR3-1600 10-10-10-27 1.5V Dual Channel Memory Kit - 
 
Intel Core i5 I5-4460 Haswell 3.2GHZ Processor LGA1150 6MB 
 
Samsung 840 EVO Series MZ-7TE120BW 120GB 2.5in SATA III 
 
Cooler Master HAF 912 Combat ATX Mid Tower Case Black 
 
Cooler Master Extreme 2 Power Plus 725W
ATX 12V Power Supply 20/24PIN 120mm Fan 
 
Windows 8.1 
 
All updates and firmware done. 
I tried unplugging all USB devices
I tried using one monitor. 
 
Latency Mon shows good performance, no issues. 
Could this be a bad stick of RAM?? how do you test that,,, pull them one by one? 

generally RAm sticks have to be put in pairs.  they have to be the same speed and if you have 2 at one speed and 2 at another speed then you have to put the pairs in in a certain order.  I think it is slowest then fastest in other bank and then the fast ram clocks at the lower speed (kinda of a waste but at least you get to use all ram).
 
you may have a bad stick.  if you have 4 I would play with only 2 sticks and swap , reboot, swap , reboot and see if you can identify the bad ram stick.
 
you may have a bad BIOS setting that is doing something odd.  very hard to tell.
 
one long beep and 1 short beep is memory error usually.
 
aslo check and make sure that the memory stick is actually seated properly.  they can look seated and be just a bit off and that will give you problems.

It's one short beep. The RAM are all the same. I double checked the seating.  All 16 Gigs shows in windows. That's why I was reluctant to blame the RAM. The Bios I havn't even touched and I'll check to make sure there is no updates.
The other mystery is this only happens on a cold boot.
A re start works fine.
I've ordered a wireless USB device so I can put it back on line to see if there's something just not updated properly. I left it for 3 days on line and it stopped updating. But the tray is nagging me. I guess Windows 8 sucks at being off line. I figure the USB wireless will be perfect as I'll just yank it out when not wanted ( mostly)
There's also weirdness with the front USB 3.0 Maybe I hooked the wires up wrong to the header?
Trouble is I'm  too busy recording to mess around to much and it does work once fired up. I'm just scared it won't fire up the day a client is sitting there. 
 

I bought parts and had the store do my latest build.  didn't have time or energy to test and figure out all the little things.
 
I would say something is set weird in your boot BIOS settings, but who knows.  I got nuttin.

With a new build, anything can be suspect.  As it does it at power on, the board is doing a power on self test and is apparently detecting some issue.  It has a 2 digit display on the board and an error code could help in problem determination.   That is the first place to start.  Just installing more memory, moving memory around or whatever isn't going to really get you to the problem.  You have to start with the POST (Power On Self Test) and what the two digit readout is showing you.   There is a long list of the debug error codes that can be displayed on the two digit display on the motherboard in the manual.
 
This board has large array of buttons for over clocking, turning memory on off, etc.  I would make sure they are not affecting anything.  Do not use any over clocking, etc until you have the system stabilized.
 
 

It can be helpful to have a keyboard that works at the most basic level handy. Maybe something with a PS2 connector.

A PS/2 keyboard connector is a thing of the past on most new motherboards.

I just went to the Intel website and looked at the first board in their list of currrent offerings:
 
http://ark.intel.com/prod...l-Desktop-Board-DQ87PG
 
It has a PS/2 connector.
 
Granted I may be wrong in that it may be for the mouse instead of the keyboard. I didn't see that info.
 
On my 18 month old motherboard I have a PS2 connector, that I hope is for the keyboard and on the day that the system will not boot with my USB/wireless motherboard I hope to rescue it with an old PS2 keyboard.
 
When I hear beeps the first thing I think is "bad keyboard"... I know that's old school thinking, but BIOS likes to find a keyboard.
 

The Z77 boards I have, right now an ASRock and an ASUS do not have the PS/2 connector.
 
But, I don't think the keyboard type is an issue as modern BIOS' are designed to work with USB keyboards and mice.  This wasn't the case years ago, the USB devices were not recognized until Windows started.
 
As I noted the first step is to check the two digit diagnostic display on the motherboard for any error codes and go from there.

In the absence of a trustworthy keyboard, I'd go with a MemTest boot disk and run it for 24 hours and see what that says.