ASUS Maximus VIII stuck at q code 04

[malagus]

Was playing a pretty graphically intensive game and had a hard crash. Attempting to restart resulted in Qcode:04
System: ASUS Maximus VIII Hero Alpha
i7 6700k processor overclocked to 4.7 GHz
MSI 980 ti gaming 6g
2x 8GB Gskillz DDR4-3200
The graphics card, right afterward was very hot, but after allowing it to cool, I took it out and didn't see (or smell) any burnt sections. The POST never gets past 04 meaning the mouse and keyboard never activate. If I leave it alone for 10+ minutes, the monitor WILL turn on briefly for a few seconds and then lose signal just before the 04 code.
I've checked for any lose connections (there were none I could see), I've tried to plug monitor directly into MB (no effect even after removing GPU).
Any suggestions?

 

[alexoiu]

Try testing different power supply, if possible.

 

[malagus]

Try testing different power supply, if possible.

Unfortunately, my new computer (built just 3 months ago) has a 16 pin connection power supply to the MB while my old one has 24pin.
My PS is a EVGA 850 P2, bought brand new.

Update: After leaving the computer alone for awhile (powered down with PS turned fully off), I attempted to swap PSs, not knowing about the incompatibility. After disconnecting all connections to my new PS, I immediately noticed the incompatibility, and I reconnected the original PS. It BOOTED! Well, kinda. Said overclocking failed and allowed me to enter BIOS. Since I've seen this issue before, I checked everything, didn't change anything, and saved/reset. It booted to q:code 64 which is: "CPU DXE initialization is started". It froze there. After resetting, it was back to q:code 04.

Any thoughts?

 

[alexoiu]

Try clearing the CMOS (unplug the power cord and remove the CMOS battery for a minute).

 

[malagus]

Try clearing the CMOS (unplug the power cord and remove the CMOS battery for a minute).

OK. I tried that. Computer started up like normal and mid-way through boot (before BIOS select option), restarted on its own. After restarting, back to qcode 04.
I would also like to point out that if I restart it over and over again, the monitor will never turn on, even for a moment. It's only after I wait a few minutes that the monitor will respond momentarily before losing signal again.

 

[alexoiu]

"Unfortunately, my new computer (built just 3 months ago) has a 16 pin connection power supply to the MB while my old one has 24pin"
What do you mean by 16 pin?

 

[malagus]

"Unfortunately, my new computer (built just 3 months ago) has a 16 pin connection power supply to the MB while my old one has 24pin"
What do you mean by 16 pin?

The MB connection cable is composed of one 16 pin connector and one 8-pin connector. They fit into separate slots on the new PS but the old MB has one long connector that is 24 pin. The old PS that I was going to try only has one long 24 pin connector.

 

[alexoiu]

You'd connect it to the board 24 pin connector. Does the PSU have a CPU 4+4 power cable?

 

[malagus]

You'd connect it to the board 24 pin connector. Does the PSU have a CPU 4+4 power cable?

I was not willing to try to connect a 16 pin MB cable into a 24 slot PS... I wouldn't even know where it would line up. I understand there are adapters for this but I don't have one.
Yes, I have a 4+4 CPU power cable.

Update: Removed GPU, PCIe SDD, disconnected all other peripherals. At this point, only powering up the CPU, MB and Mem (which I reseated). Also, did a full CMOS clear. No difference.

Edit: Update of my update: After removing battery from CMOS and waiting awhile, it booted up for a few seconds, auto-restarted, then got to qcode: 04. However, just before qcode: 04, it was working on qcode: 66 which is CPU DXE initialization. And that is where it sits now.

 

[alexoiu]

It might be a board, or CPU issue, assuming that the power supply does work. I'd RMA them both, if under warranty.

 

[malagus]

It might be a board, or CPU issue, assuming that the power supply does work. I'd RMA them both, if under warranty.

It stinks that I currently have no way to test which one is the culprit. I have a nice water-cooler on my CPU and its never been overly stressed (with the exception of the first overclock). On the other hand, my ASUS MB had problems right off the bat refusing to overclock the memory AND the CPU at the same time. I ultimately had to keep the memory voltages at default just to get the CPU overclock to work. So I think I will start with contacting ASUS. Any thoughts?

 

[alexoiu]

I'd contact both ASUS and Intel, just to be sure.