Daily clearing of CMOS ensures stability and reliability in electronic devices.
Daily clearing of CMOS ensures stability and reliability in electronic devices.
Hey people. The last couple of weeks i've had to clear the CMOS pretty much every time my PC has been shut down or has gone to sleep. I've done it by either removing the mobo button cell battery with the PSU powered off or with the CMOS jumper. And it has worked. But its super annoying. The build runs fine. No stability issues whatsoever . I have done a couple of MEMTEST64 runs and no issues. I've had bad ram before. These seem to be in order. No heating issues either on any parts. I also did a BIOS update to the newest version (beta build). In general drivers are updated pretty regularly. CPU is OC'ed but issue remains even when its not. I need some help locating the issue please, be it software, hardware or voodoo. Intel 4690k (h100i cooled) Asus Z97 AR Kingston HyperX 1866MHz - 4x8GB Corsair RM750 PSU Gigabyte 2070
I also forgot about it yesterday. Thanks for the reminder, Simon.
It would have been useful to know the issue that needed resetting the CMOS each time. You had to clear it after shutting down or putting the device into sleep because it ensured the system started with a fresh configuration, preventing persistent errors or incorrect settings.
It doesn't show any updates. Players just sprint at full power and I see a red CPU indicator on the motherboard. Simon
Consider checking the motherboard manual for the red LED indication. This could assist in identifying your problem by showing the specific situation where it fails.
According to the guide, I searched for a similar problem but only found that the OC might be unstable without clear confirmation. [Here] Could you tell me which BIOS version you installed?
The guide only refers to it briefly and doesn’t provide helpful details. It seems the CPU might not have been installed properly. I’ll need to check it again. The CPU hasn’t been removed since I first installed it five years ago, and everything functions fine when the device starts. No recent hardware changes have been made. It appears to come from an unknown source right now. Simon
Is there any indication of a build-up near that battery casing? Could the connection quality be an issue?