MSI Z170A Gaming Pro Clear CMOS?

I am having the same issue. Mine was working fine at first, until I downloaded a BIOS update through the MSi update utility. Afterwhich my system restarted, and failed to boot. On the motherboard the CPU led fault light turned on, and my monitor isn't getting a signal. The lights on the tower turn one and so do the fans. Everything sounds like its running, but the system does not appear to be even trying to boot and if it is, nothing is responsive. All parts are new and they were working, so in my case it would seem that the BIOS update is what caused the problem. I am also trying to fix this myself. It is just frustrating since I was so excited to get started using the system after so much time and money.

So far I've attempted some fixes that have been suggested on various forums, they are listed below with loose detail.

- Removing the graphics card from the motherboard and reseating it firmly. It didn't help but its didn't seem to hurt.

- Removing all RAM, then attempting to boot with one RAM chip on DIMM2, then again with two chips on DIMM 2 and 4 (my default setup). Again no progress. There were a few different DIMM combinations suggested.

- Unplugged all cables, held power button 60+ sec. then rewired. A lot of people advocated this solution with a few variations, but it didn't work for me. I tried it at least 3 times now.

- I removed the CMOS battery and left it unattached for about 30 min. before reinserting. This was suggested as a form of CLR_CMOS, but yet again- nothing. I tried twice, but I feel as if I may need to leave the battery out longer to fully drain. The fans, lights, and everything still seem to power on and run as they should, so I do not think that the CLR_CMOS worked.

- There's also the CLR_CMOS using the Jumper Cap on JBAT1, but I haven't tried it because my Motherboard did not have a Jumper Cap and I do not have one (yet). I've read a few suggestions stating that shorting the jumper can be done with a paperclip or flathead screwdriver, but there seems to be mixed responses about this.

I feel like clearing the CMOS should fix this, especially in light of the event preceding the issue. So far its just frustrating. If I could at least get a signal on the monitor I could see whats going on. As a note, the User Guide specifically prescribes a CLR_CMOS in response to no boot after a BIOS update. I've already put in a lot of time on the rig, so any help putting this to rest would be great.