Blue screen on start up (Solved??)

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? 

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. 
 

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.
 
 

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

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.

I'll second Mikes suggestion...
 
Don't assume that because it's new... that the RAM is fine.
Test to be sure...
DDR3 is the most common (hardware) culprit on a modern build machine.

It still goes back to what I said about the diagnostic display on the motherboard.  When you power on and it bombs out, look at the display and note the code that is being displayed.  If it is an error code the list in the manual will tell you what it is. 
 
If there is no error code, then go with the memtest86 or whatever.

OK memory test passed. I will do what Jack is recommending tomorrow,
I'll open up the side and see what the LED Say's when it goes blue screen. 

I ran the Windows memory test as startabartfast posted. I ran 2x and reported no issues.
 
Just now I opened it, re seated the RAM, unplugged the front USB 3.0 to Mobo cable which isn't working anyway? and on start got blue screen. The LED fires off a million numbers and I took note of as many as I could read, last 2 are slower and A2 then it stays at A0. Both these are IDE related and as far as I can tell are not issues but just reporting it has initialized.  
 
Memory error would be 50-55, which I don't see after watching a few re boots. 
There is always the one beep. 
I re booted a dozen times and the pattern seems to be that every second boot is OK. 
I was using the Mobo on /off button inside. 
Note that when it boots , it boots super fast and there seems to be absolutely no issues at all. It's working as expected.
 
I guess because I have 4 sticks of RAM, I could now try removing in pairs. 
 
So far the history is: 
Initial build only 2 sticks of 4 Gig DDR3 1600 RAM 
Single beep from first boot up. 
Machine performed as expected and installed Widows 8.1 to new SSD drive. 
Beep continued, LED always shows A0 after boot. 
Machine was re booted dozens of times without issues while running updates etc. 
First Blue screen was once it was placed in studio. 
So I unplugged all usb devices and the second monitor too. 
I checked all connections inside including the RAM. 
Reading the single beep was memory, I double checked memory channel placement and decided I'd order 2 more sticks of Identical RAM. 
This did not change the behavior so therefore I posted here. 
 
I'm not in love with this Gigabyte Mobo. I'm more used to Asus boards. The instructions are terrible and there's 100 pages about overclocking and very little about the connections. 
 
One other question, the instructions and pictures are not clear regarding SATA connections. 
Other mobos I've used the connection is pointing up and clearly marked 1-2-3-4-5-6-
This stupid board the connectors are sideways and hard to get at.  
There are 2 stacked marked SATA 3 
then a 6 gang stack marked SATA express. 
 
I have my OS SSD drive and the DVD drive connected to the Sata 3 pair
 
my 2 data drives are connected to the sata express.
Is this correct? 
 
and I really appreciate you all taking the time to walk me through this. 
 
I've got to get busy editing yesterdays session so no time for the dumb computer part until tonight. Thanks once again. 
 
 
 
 

This does look like the manual for the motherboard: 
 
http://www.cdromland.nl/productpdf/00162283-manual.pdf
 
Trouble shooting begins on page 110 in the manual.  You can click on the line in the Table of Contents to go straight there.
 
Explanations for displayed 2-digit codes are also listed a couple pages later
 
A0 seems to indicate simply that IDE initialization has started.
 
BoB Bone
 

Now that you've saved all this time with Windows memory test, you might want to try a boot CD with Memtest and actually test the memory.
 
Memtest will ferret out an intermittent problem. Heck, I run memtest on memory I think is good... if you have a reason to think your memory is bad, the sooner you ferret out a problem the less likely you are to corrupt your Windows install and have to go back to square one.
 
If you had never gotten it to boot to Windows I would be more focused on the motherboard info... but the fact that you have had Windows running makes me think it's time to check that memory.
 
Good luck.
 

That is one impressive motherboard, from looking at the specs.
 
Quick question: what BIOS version is currently on the motherboard?  I believe from your initial post that you hadn't done anything with updating BIOS, if I recall correctly, and I just wanted to take a look at the various versions they released.
 
What a bizarre error condition, to have 2nd boots seemingly OK - that's a new one on me.
 
Forgive me for being behind the 8-ball on your issues - I AM trying to get up to speed on the thread, and will do my best to help you, if I can.  :)
 
I did double-check the supported memory, and all seems fine and good with that (I was also pretty sure you would have checked that too, but I was just trying to be thorough).
 
Also, early in the thread, you indicated all maintenance and firmware being done.  For the maintenance, are you strictly referring to Windows maintenance, or driver maintenance, or both?  Thanks for some clarification on that, too.
 
I ask, because for one of the computers I built, there were some 3rd-party drivers for the USB 3 support, and it made me wonder if you had applied the base drivers from the disc that came with the motherboard, and then was wondering about any subsequent application of drivers from the Gigabyte site.
 
Bob Bone

Hang in there, so we can all go down with the ship - actually, I am hoping that between everyone, and the internet, there should be some kind of solution for this mess.  I'm optimistic.  
 
Bob Bone
 

Mike, First I clicked on the direct download link you posted, It downloaded in 2 seconds.. so it's bogus I guess. 
That's the site I didn't like as it has typical false Download buttons all over it... sorry, I avoid downloads from sites  like that.
I downloaded the one from the link I posted and it seems clean and the site was straight forward. I'll give it a go tomorrow night. 
 

That's why I bought the second pair of RAM, All 4 slots are full of the same stick. 
 
I did re check my little microscopic connections and all is good. They are for the front panel switches and lights which all work fine.The USB 3.0 connector is big. looks like at least 12 pin so there's no way to mix it up.  The connection works, sort of, but it has trouble recognizing USB storage devices. There is a USB 2.0 connector on the front that is working fine. 
 
I think Bob has nailed it with there might be special drivers that were not on the CD or didn't get installed. I'll run the mobo driver CD again and see what's on it, I just let it automaticly do it's thing, but there might be more stuff on it I missed. 
This issue just might be resolved with a little more updating. I see my wireless adaptor has arrived at the depot so I'll pick it up tomorrow.