Ok so my fist board after moving it to my new office would not post. I was getting error codes 00 E8 01 62 repeat. So after several attempts with support EVGA decided to RMA the board (even though the board was a couple weeks out of warranty.. I know right....the best CS in the business.) however the RMA board arrived today and it has the exact same error codes. I scoured the net only to find many many people with the exact same issue with the exact same board. I thought I would check with the forum pros at EVGA see if anybody has come up with a solution to this issue. The original board only sat for about a month. The only thing that changed was the PSU, though I took a corsair 450w out of another one of my builds that was working and had the same result seems kinda odd that all these models have the same issue even an RMA, whats up with that, do they not test the board before sending them out. I can only assume that I got a refurbished MOBO that did not actually get fixed because nobody seems to know what the issue is. 

It's possible to receive a defective replacement. It has happened before. Only thing you can do is ask for another RMA.
 
 

I have not cleared the cmos yet but I did do a bare bones boot with only the cpu and cooler and got the same codes. I will however try and clear the cmos and reboot with no ram. I must say though it is not hard to believe that you could receive a RMA with the same issue as there are people all over the net with the same issue. If the memory controller went bad would intel back up there cpu its only 2 years old.

Never mind all problems solved I am up and running. Thank you again.
 

MSim
It's possible to receive a defective replacement. It has happened before. Only thing you can do is ask for another RMA.
 
 

+1, I sent in a GTX 570 in the past (first one was Dead On Arrival, second one worked) it happens.
 
evga even paid for the return shipping on the dead RMA so I didn't have to pay it a second time.

In reading post on here it seems a good percentage of folks don't understand the importance  of clearing cmos when debugging an issue. I have seen a psu, a gpu, and a HDD corupt the cmos to where it had to be reset before the system would operate correctly after replacing the part. Simply replacing the failing part without a cmos reset will not always make the system operate correctly. So how is it known if the part was the issue or not if a cmos reset was not performed? I'm just throwing this out there for those debugging to think about, not to criticize.