Final update.
 
After installing Windows 7 and using the bios updater for the motherboard to get to the latest BIOS I was able to pull out the 2x4GB DDR4 modules and install the new Corsair 2x16GB DDR4 modules and everything worked like a charm.

The symptoms OP described sound like what happens if you try to boot with no ram sticks.  Gets through a few post codes then clicks off.  I would have blamed the RAM from the get go.
 
This is why I agree with Puget Systems...put vanilla 2133 Mhz memory in there and call it a day unless you want to spend time potentially troubleshooting boot issues.  The 2666 memory in my desktop I downclocked to 2400 to make sure it never gives me trouble.

Here is my experience in troubleshooting this problem.
 
C-04-19-60-FF-C cycle is normal for this board when no ram is present in the DDR4 slots, and this is despite there being post error code 55 in the manual that is specific to no memory installed. It seems the traditional method of troubleshooting for a faulty board no longer applies, by pulling ram and expecting a post code or beep code, at least with the 1.20 version firmware. Yes, the manual says the board won't boot without ram, but one should be able to expect a memory related post error code, right?
 
For my build I am using 16GB modules of the Gskill F4-3000C15Q series. For whatever reason the BIOS wasn't able to pull settings from the JEDEC tables for this RAM, and the board would act as if no RAM  was inserted at all. It wouldn't even halt on one of the post codes relating to memory initialization, which was very surprising to me.
 
I ended up having to buy and install a cheap stick of Corsair ram in order to get the board to boot so I could get into BIOS. Once there I was able to specify the speed and the timings manually, reinstall the Gskill ram, and THEN it would work as expected.
 
One final note, I was able to use the XMP profile with this ram but only up to 112 GB. It seemed that maxing the board out at 128GB was more than it could handle, as it would try to initialize and reset multiple times before finally booting and registering only 96 GB of ram, as if the last two dimm slots were disabled. So far a setting at 2666 for 128GB seems to be stable, at least.
 
 

I guess what you would be saying is the bios is not "out of box" updated to be able to accept the ram you originally wanted to use, though per evga website it states compatiblity, but should also state "out of box compatibility" on that section as well. So what type of cheap ram should that is known to work "out of box" on unit/evga x99 classified? Can I get part number please? This is a fresh build I am working on. I am trying to use f4-2133c15q-32grr in 1-3-5-7 equaling a no boot situation with code stated above in header. Tried one stick, same result. Thanks ahead of time.

I have used a listing in that group on the mobo. Please read Alanz response which is what I am truely referring to. He noted that he was able to use a different stick of cheaper corsair ram to be able to boot the mobo. I wonder which one he had used, because there are a number of them available?

The ram I am using is g. Skill f4-2133c15q-grr(on that list). I am using a 5960x CPU. If it(the ram) were to work out of the box with the x99 classified, neither him nor I would seem to have a boot problem according to the list Gtxjack provided. From alanz response it easily seems resolved from the use of something different than what I am using. Also, if you correspond Alanz ram, it's also listed, though his ram is of higher frequency than mine. He had the same problem I am having with the c-04-19-60-ff-c issue for boot. The board is never fully boots in its current state.

Note: Before even purchasing this mobo I did thorough research and ordered my ram based off of that exact list. This was not an issue that was foreseen in my build, though just a bump in the road if I could get a part number possibly? It would be nice for this to be a possible fix. Thanks for the response Gtxjack and any further info would be greatly appreciated.