OC settings went bat crazy
OC settings went bat crazy
Last night I chose to run HW Monitor just because I wanted to check how my well-tuned system performed, and was surprised to find my v-core hovering in a very high range of 1.36 to 1.39 under load, indicating it wasn’t optimized properly. Temperatures were climbing rapidly into the high 40s. After finishing a game of Witcher 3, I became even more concerned about the situation during play. Usually I keep my overclock conservative, with an offset voltage not exceeding 1.32 and a stable 4.2Ghz, but 1.39v is completely out of my comfort zone.
I quickly restarted my machine and entered BIOS settings, which were mostly in French at first. I had to re-learn how to interpret the BIOS parameters. After a moment of confusion, recalling simpler language lessons, I managed to switch everything back to English, reset the defaults, cleared the CMOS, applied my own overclock values, and then fell asleep. This morning I replaced the CMOS battery again, thinking that after months of inactivity the battery might have lost its charge. I also noticed the motherboard clock was a few hours behind.
My OC settings remain unchanged, and I now enable HW Monitor at startup to keep a close eye on everything. I’m grateful for your help with this issue.
Could a faulty CMOS battery be responsible for such widespread corruption across my system, affecting everything from the v-core to the language settings? And what kind of long-term harm could I have inflicted on my CPU? If the BIOS was disrupted during the last time I unplugged and powered down, that would have happened a couple of weeks ago during my fan filter maintenance. I fear it might have been cranked to extreme voltages all along.