The first happened and I was able to bring the system back by switching the B BIOS chip and continue using my system that way after struggling to get the CMOS and everything reset. It's quite interesting because it seems these ASRock mobos need to be cmos reset and then take a long time to rebuild after the reset.

Now this happened again two weeks later with the same symptoms but now I don't have another BIOS to switch to. Since I can just switch BIOS chips it doesn't seem like its a CPU issue. It seems like somehow the NVRAM is getting corrupted and preventing it from booting... or just the firmware keeps killing itself somehow. Is there some way to clear out the NVRAM or investigate it being firmware aside from shipping the whole thing in?

Yes I tried reseating the CPU, checking the cooler and socket, only one stick of ram, etc.

Specs:

I7-7600K Skylake

Z170 Extreme 6+ 1.60 FW

G.SKILL RIPSAW 4 16 GB DDR4-2800

Asus GTX 970 4GB GPU

OCZ ZX Series 850W PSU

Samsung EVO 850 1 TB

Windows 10 64-bit (TH2) UEFI install

< id="kpm_plugin" ="application/x-KPMPlugin">

< id="kpm_plugin" ="application/x-KPMPlugin">

< id="kpm_plugin" ="application/x-KPMPlugin">

< id="kpm_plugin" ="application/x-KPMPlugin">

< id="kpm_plugin" ="application/x-KPMPlugin">

For example its CMOS clear, first initialize, and first power on all seems quite strange. Like you power it on after CLR CMOS and it rebuilds the CMOS and values.

< id="kpm_plugin" ="application/x-KPMPlugin">

It's interesting because the 00 code the board doesn't even get far enough to initialize the onboard fan controller. I loosened and checked the cpu cooler again and it still seems fine. This is an interesting error, normally I am used to things being simple on my builds.

I am starting to wonder if its a combination of things. Like a bad mobo or firmware with a dying PSU and bad CPU? I know that there was some strange behavior setting DDR 4 memory settings outside of stock before the 1.60 firmware. That is an unintentional overclock of the base clock for the bus. That might have done something. Anyways, for me it stays as 00, no switching of codes or even initialization of the mainboard's onboard fan controller (the case fans stay off, but since I use a water block (corsair H100i) cooler it doesn't require any power or control of the mobo to run the CPU cooler. Never have to worry about the fan(s) not being powered so long as the system is getting powered.

I carried out the suggested changes bellow, it was interesting that at one point I was able to get the case fans to run, but nothing but code 00. As a side note I think the first time I booted up this computer it lingered at 00 for a while until the BIOS initilized and I was able to get into the delete to set up BIOS. Perhaps it was a defective Mobo all the time?

Clr CMOS jumper and the reset / power switch is clear.

I have a new PSU coming on Thursday (high end corsair I got for 60% off on newegg). Will try again then, but I am pretty sure the firmware chips are just gone by now. Wish there was a flashback system so I could confirm that.

Wardog did a good job, just I find it interesting and the behavior I have seen from my Extrme 6+ is quite different from what I have seen in my almost 20 years of using and building computers. Like most of the other brands that have backup bios dont let you run off of the secondary BIOS, they just reflash and hand back off to the primary. Also I have never had the long time at first boot out of the box where I had to wait a long time for what appeared to be a re-initilization or cmos reset right out of the box. Thats why I kept asking questions, trying to throw as much information up that could be helpful and see if I can ask the right questions.

I am waiting to hear back from ASrock tech support, but I might just call them up (for some reason I couldnt find the phone # to contact them until wardog posted it). Will just order two more chips and ask them to rush them to me. Honestly this has just left me confused, intrigued but confused.