Error encountered during startup: "Unable to run overclock"
Error encountered during startup: "Unable to run overclock"
I gathered this up possibly due to a fan error... initially it worked, but after a power outage it failed. After checking the overclock settings in BIOS, it wouldn’t boot again. The power was off for a while and the room was hot—80 degrees, which wasn’t a problem before. Overheating seemed to start right before the error appeared.
I’m worried something important might have been damaged, and if it did, I could be in trouble. I noticed the fan took a while to spin up, which might be the issue, and I’ve turned off fan speed for now because of another problem.
I’m wondering if anyone else has experienced this issue... my system info is below, and I’ll share more details if I find something useful for checking system stats.
I haven't encountered any motherboard errors yet (that's good news). It looks like the SPU fan is functioning properly, though I raised its base speed from 500 at idle to 700. I'm still puzzled about the motherboard problem beyond possible CMOS settings, which I haven't changed. Someone on another thread mentioned overcharged RAM due to a power outage that fluctuated several times—maybe it's time to replace the PSU. If the CPU were faulty, it wouldn't run Windows at all. Similarly, damaged RAM would cause the same issue, and I'd hear strange beeps afterward.
Did you experience a power outage at your place that turned off your PC? The first boot then triggered an error message. I understand ASUS boards might display OC error warnings after POST if the boot process is interrupted, or if the power button is pressed. A power surge or brownout could harm components, but that doesn't match your situation. A faulty CPU would prevent the system from starting at all. Fan speeds may change during idle due to temperature, and without an onboard system speaker or installed one in your case, you wouldn't hear any beeps. I'm not clear about the "overcharged RAM" reference.
Yes, the power was cut off when the computer started, then it would turn on and off intermittently (even though it was already off). The first boot showed an error, but the second one booted normally to Windows and then shut down. I adjusted the cooler's fan speed to around 700 before it reached about 500. I was concerned it might have been damaged, but I don’t mind replacing it now since it’s working fine. Someone mentioned a power outage or overclocking might have caused the issue, but I tried that once and it was risky. Regarding the internal speaker, the ASUS Z77 doesn’t display RAM counts; I assume it’s just a soundboard speaker. I know it works, but if there’s only one beep sound, I’m not sure. I used ASUS software to check CPU temperatures and speeds, which all looked normal. I think the problem might be related to the motherboard itself, especially since it crashed into Windows 10 on the second try—something I’ve never experienced before.
It might simply be due to power fluctuations from the utility power and Windows 10 not shutting down correctly. It could also relate to hybrid sleep during a normal shutdown compared to the traditional method used with Windows 7 and earlier versions. Concerning the speakers, a case might have a wired speaker connected somewhere, linked to the front panel IO headers on the motherboard. If not, some OEM boards still have a small speaker soldered onto the board, usually black, which produces the "beeps" during POST or for debugging. The built-in audio on your motherboard differs from the speakers or headphones you use.
With these points in mind, has your system been operating normally since the error and speed issue? If yes, don’t be too concerned unless further problems arise. It’s still wise to monitor the fan speed to detect any changes.
Yeah, I haven't played a game for a while yet, but I think it wouldn't be fun to keep running Deus Ex: Mankind Divided for too long if things were really messed up. The motherboard software shows the processor speed changes, and the temperatures look normal. I'll let you know if it starts acting weird again.
I received a warning from the software that my CPU was at 61C, which seems unusually high. For a Sandy Bridge overclocked, is that considered excessive? Could continuously running the fan at high speeds be problematic? When playing Deus Ex Mankind Divided, does it reach 60C?
You have the option to keep the fan at high speed if you prefer, which may increase noise and slightly reduce its lifespan, though it's likely you'll replace it soon. Concerning the CPU 61C, the warning from software seems high, particularly when running a game. The program appears to be referencing a package temperature rather than the actual core temperatures. Could you share your real core temperatures using CoreTemp or RealTemp?
currently it operates at 37 to 40c on desktop. with my modified fan adjustments at 900rpm idle and 40c it reaches 1200rpm, then 50 it climbs to 1700. i haven't seen it exceed 50c in the game often stays between 40c and 50c.
What CPU model do you have? 61 isn't the highest most CPUs can handle, typically they run smoothly from 62 up to around 68-70°C. This could cause the PC to shut down or fail to power on, which might happen if the overclocking attempt fails. If that occurs and it doesn't turn on again, resetting the CMOS could resolve the issue.
1. Remove the MOBO battery
2. Wait 5-10 seconds
3. Reinsert it
If this doesn't work, the MOBO, CPU, or power supply might be damaged.
If you suspect the RAM is the cause, remove one module and test with another. If it boots fine, the RAM is likely the problem.
For an idle temperature around 37-40°C, it's acceptable, though the fan speed might be too high. Consider replacing the heat sink—options include a budget Hyper 212 Evo or a premium Noctua NH-D15 SSO2, though they're large.
CPU fluctuations are normal; if it drops significantly during gaming (e.g., from 3.6 GHz to 2.1 GHz), it may indicate a problem. Replacing both the CPU and heat sink could fix the issue, but if that fails, replacing the CPU itself is advisable due to potential faults.
After completing the overclock, everything should work properly unless the MOBO is damaged. If it still doesn't function, ordering a new one or using an available alternative is necessary.
Error during startup might also stem from an inadequate MOBO, as my previous M2N68-AM SE2 only supported a 7% overclock, and higher values trigger an OC error.