Overclock boot

[smolkomartin1]

Hi, I´ve got a problem recently. I had my trusty Intel i7 6700K set at 4,7 GHz at 1,325 V for over a year now and I went to update my BIOS. I have an ASUS Z170-A motherboard and everytime I update it, I´ve got an error message saying that overclocking failed. I always fixed it (still not sure how, I always did it (I guess a CMOS reset)), but this time is something different. When I start my computer it doesn´t boot, like it starts up, but I´ve got no signal. Also I can say, that on the motherboard there are 4 LEDs, all next to one component (CPU, GPU, RAM and bottom of motherboard), when everything works the RAM LED will flash, then GPU and then bottom, but at this "No Signal" state, only RAM LED flash and turn off after like 3 seconds. Then I hard restart it (holding the power button) and it will boot normally, but with an error saying ,,The system has POSTed in safe mode". I then get into windows by going into the BIOS and exitting without saving, but I don´t have my OC. What should I do?

 

P.S. I found out, that when pressing the MemOK! button, which gives me status that everything is fine with RAM, I can boot via BIOS (same as above) into windows and my overclock is applied. I´m now confused as hell.

 

Thanks!

[Princess Luna]

I have always been told not to update BIOS without need... this is a clear good example of it

[heimdali]

Well, what´s the definition of "need"?

 

[smolkomartin1]

6 minutes ago, Princess Cadence said:

I have always been told not to update BIOS without need... this is a clear good example of it

Wish I knew that before 

[Windows7ge]

8 minutes ago, heimdali said:

Well, what´s the definition of "need"?

 

In this situation "need" would be defined primarily for certain hardware incompatibilities. Some incompatibilities can be fixed with a firmware/BIOS update like with the CPU, GPU, and sometimes RAM. I'd say less common but maybe even certain kinds of network adapters like 10Gbit NICs in a PCI_e slot may not be compatible with a certain BIOS version but an update can sometimes fix it. Also your BIOS version can even conflict with the OS itself or not allow you to boot to certain media like NVMe. When NVMe first came out the software wasn't quite there like with any other new release. When the AM4 socket was first released there were all sorts of issues with the stock BIOS. BIOS updates can be a "need" in any of these circumstances.

 

My rule of thumb is don't update the BIOS unless something you're doing requires it or you've exhausted every other troubleshooting option when the system is having issues with new software or new hardware.

 

I've personally had instances where updating the BIOS had the opposite effect and took things that previous worked great and made them completely unresponsive to anything I did.

[heimdali]

Well, yes, maybe I´ve had too much to do with server hardware to be afraid of BIOS updates and to still say they shouldn´t be done.  They become available because things don´t work as could be expected, hence it´s usually a good idea to install them.