I5 6500 overclocking problem
I5 6500 overclocking problem
I increased my 6500 to 4.19 MHz on gigabyte z170 k3, it functioned perfectly for two days. After that, I tried to increase it further, but when I booted in Windows, an error appeared and I had to restart to 4.2, which also showed the same issue. The system didn't start at any other frequency except base without overclocking. What steps should I take again?
Arsenalk shared his experience with a voltage of 1.325 and a RAM frequency near 2800 (actual speed around 3000). He is puzzled about why it fails on previous configurations, which worked before. Intel seems to be making unusual adjustments to prevent non-K overclocking even on older BIOS versions that supported it. He mentions hearing rumors that Intel might be working with Microsoft to limit this functionality at the operating system level. If this isn’t an unusual action by Intel, he suggests resetting the BIOS to defaults and clearing the CMOS. There might be residual settings causing the issue. He recommends looking for a helpful guide or resource.
Sure to say, it's not advisable or safe to push a non-K CPU beyond its limits. If it fails or gets damaged, warranty coverage won't apply. This CPU wasn't built for overclocking; it performed briefly and you're lucky it didn't break. The idea of safely boosting a non-K CPU using BLCK isn't reliable unless voltages are controlled and cooling is maintained. I believe the main difference between K and non-K CPUs lies in the multiplier settings, not just the core itself. If you experience issues, it's likely due to overvoltage rather than a special characteristic of the K variant. Where are you finding this information about non-K CPUs? Also, regarding memory speeds, increasing the base clock can boost both RAM and CPU performance.
I'm surprised you're still managing this, do you have an older BIOS? I thought Intel tightened restrictions soon after release.
Arsenalk shared his experience with the current voltage and ram frequency settings. He noticed the system doesn't function properly on previous configurations, even though it worked before. He mentioned Intel's unusual actions to prevent non-K overclocking in older BIOS versions and suggested resetting the BIOS or CMOS as a potential solution. He also looked for helpful guides online.