OC does not work during system startup but remains stable after a reboot.
OC does not work during system startup but remains stable after a reboot.
Hello, I have the following setup:
i5 6400
gigabyte z170 hd3 ddr3 bios f5c
2x4gb ddr3 1333 kingston
500w bequiet sp8
rx 480 nitro+
noctua u12s
I tried OC through BCLK, everything works fine at 4.1 ghz 1.275vcore, system agent voltage at 1.150, I adjusted a few other voltages slightly higher. The system runs stably, lasted two days of gaming, stressing, and idling. The issue is that when I turn it on in the morning, the OC fails. It asks me to reset the BIOS, I enter BIOS, just press f10 and reboot – it works again (since I already saved my OC profile). Another thing is, when trying to boot Linux on dual boot, it won’t boot unless the base clock is lower than 102.5 MHz; if it’s higher, it won’t boot at all. What should I do? Did I miss something?
Attempt to configure to stock settings and perform memtest. If freezing persists, reduce RAM to one stick and retry. If it still freezes, switch to another stick. Observe which sticks freeze and which remain unaffected. If none freeze at stock settings, the issue likely lies with the CPU.
If all function without freezing at stock settings, proceed with a gradual increase in overclocking and testing. Overclocking requires repeated adjustments and testing until a suitable setting is identified.
I don't suggest relying on BCLK Overclocking. The BCLK might influence more than just the processor. Using the multiplier seems to be the optimal choice. As far as I recall, the BCLK impacts the base clock of all components, including memory and CPU.
The_Staplergun :
I don't recommend using BCLK Overclocking. The BCLK can effect more than just the processor. Using the multiplier is probably the best. If I remember correctly the BCLK effects the base clock of everything which includes memory and cpu.
ye i know, i also adjusted ram clocks down to what they can held, i have no other way to oc this cpu, multiplier is locked
Certain CPUs struggle with overclocking, particularly those that are already locked. For better results, consider a more recent unlocked model. Adjusting settings can help, though sometimes higher values aren't effective.
The_Staplergun :
Some CPUs just aren't good for overclocking, especially locked ones. If you want to oc I'd recommend a newer generstion unlocked chip. You can try tweaking settings up or down. Sometimes higher numbers work but between type numbers don't.
did you read what i wrote? oc works fine, i can run the system for days under stress, i just have to enter bios every time i turn it on, and that's annoying.
This indicates instability. I can maintain 5.0ghz continuously and even under heavy load, but prime95 often generates errors and occasionally causes crashes.
Stability isn't always as quiet as a storm; sometimes it shows up as sudden failures without clear cause.
Please don’t interrupt by asking questions or criticizing others.
It might be another issue, but overclocking usually points to this.
If you believe the OC is working and the BIOS is outdated, ensure your BIOS is current and you have a solid power supply.
With those conditions in place, a new motherboard could be a good solution.
I suggest downloading memtest86 and running it overnight to check for errors, as memory issues could also be the cause.
The_Staplergun :
That indicates instability. I can maintain 5.0ghz continuously and even under heavy load, but prime95 consistently generates errors and occasionally causes Windows to crash after some time.
Stability isn't always as smooth as a tornado—it's more like occasional crashes without clear cause.
If you're not sure about the stability, please ensure your BIOS is current and you're using a solid power supply.
If those factors seem correct, it might be worth considering a new motherboard.
I suggest downloading memtest86 and running it overnight to check for errors, as memory issues could also be the culprit.
I've tested memtest86 before; it failed the test, stuck at certain percentages—first around 22%, then progressing to 40% and beyond... so at this stage, the RAM appears to be the issue.
sorry, i realized you meant the pc freezes and i need to turn it off.