All of the settings were manual with no offsets enabled.

 

>what were the multipliers/ratios set to?
Rather high, like the maximum that has been known to be successful. But that wouldn't have killed it, it must have been the voltage, specifically seems it could have been the Uncore voltage.

 

Max (and perfectly safe on water) VCCIn is 2.1 according to many review sites, Intel is conservative.

 

You can see in my linked post that the guy said he got to 4.7GHz uncore on water with an 8core no less! Some guys with the PentiumG Haswell(non-E) 4core/8Thread have it up to 5GHz with 5.6GHz core.

My 5820K chip was tested good for 4.5GHz @1.27v by a friend, but he didn't try beyond that conservative Vcore: so 5GHz @1.437 wasn't an unreasonable request. That 1.437Vcore is cited by many as safe, but I only found that one guy(linked post) who said uncore over 1.2V was possible, and maybe I misinterpreted that, when he really meant Vcore instead of Vuncore in that cite.

 

It is just hard to believe that setting it to that, even if wrong killed the CPU in one sec, it never rebooted again!

You can try RMA the CPU, you may get lucky and get it replaced.

I sure hope it's not my video card or something preventing the BIOS LED from turning on. (Though it worked fine before, so the CPU setting change must have killed the CPU, I guess.)

I guess I shouldn't have trusted some random post, or maybe that number wasn't uncore even though it sure seemed like it.

So based on your recommendation that there should be a "missing CPU" dr.debug code, I assumed it was the motherboard and ordered another identical one.

 

Same problem with the new motherboard. Monitor recieves signal but the signal is a black screen, the Fans are on, but the red BIOS led is off. So I will try ordering a new CPU then.

There is only a Killer version of 3.1

 

I highly doubt rebooting with the uncore would kill the CPU as there was no load, i.e. it never worked with that setting.

 

I tried taking out the RAM and there is no Dr.Debug codes, if the motherboard was fine then it should show in either case of missing cpu OR ram. I am pretty sure if there are no lights on the motherboard that means it is dead, so I reordered the same board, but I have to pay $69 restocking now. Seems the CMOS got corrupted and can't be cleared, seems separate problem from the BIOS, since that switch doesn't help.

The only way I can think of to determine if the board is dead is to remove the CPU and power on the system, the Dr. Debug LED panel should display a "00" error if the board is working correctly. If it does not then the board has probably died. If it does display a 00 code then try checking for bent pins and dirt on the contact pads then reinserting the CPU. Clear CMOS again before you attempt another boot at this point. If there is still no life at this point then the CPU is the fault.

Good luck, I hope it is just poor contact in the CPU socket.

 

If the fans that are connected to the motherboard spin, it seems it is alive but I think if there are no LEDs there then it must be dead, how would the CMOS clear fix that?

I tried leaving the battery out before, the CMOS jumper wasn't in the clear position for that time, I guess I can try that.

 

The Dr.Debug should show codes if CPU was bad.

 

UPDATE: With No RAM it still doesn't beep with the PC-speaker or headphones. LAN lights up but no dr.Debug. I hope it's not the CPU that died because (I assume dr.Debug would show up in that case) I will try RMA'ing the mobo.

I would first try a battery cmos clear:

Power off the system and unplug the power cord

Press and hold the power button to clear residual charge from the PSU

Set the clear CMOS jumper to the clear position and leave it there

Remove the CMOS battery 

leave the system like this for 4 - 8 hours

set the clear CMOS jumper back to normal

replace battery

connect power cord

try to power on the system

This is what I like to call a "failsafe" clear and will clear any and all cobwebs from the bios. 

If this fails then remove the CPU and check for charring/dirt on the contact pads as well as look for bent pins. Depending on the voltage you set the CPU could have taken damage. Bare in mind that intel CPUs have the VRMs built into them these days. You can additionally try to power on the system with no CPU installed and compare symptoms.