F5F Stay Refreshed Power Users Overclocking Need assistance with the i7-7700k OC. Any suggestions would be helpful.

Need assistance with the i7-7700k OC. Any suggestions would be helpful.

Need assistance with the i7-7700k OC. Any suggestions would be helpful.

A
Acullis
Junior Member
14
05-04-2017, 02:35 AM
#1
Hey there, I've been dealing with a kernel-41 problem for quite some time with my build from last year. At first, I thought it was hardware-related, but after months of troubleshooting the wrong way, I realized instability might be the real culprit during dynamic overclocking. The kernel 41 is quite unpredictable—sometimes it works three times a day, other times it lasts days, and occasionally it restarts completely, whether idle or not. It mostly happens when idle, though. I shared my experience a while back, and someone with a similar issue suggested a fix. You can check the linked post for details: They mentioned turning off EIST resolved it for them, though their English wasn’t perfect and they weren’t entirely sure what they did. I tried other fixes before, but only now did I consider overclocking instability. Right now, I’m using the auto-overclock feature OC GENIE 4, which disables C states, turbo, EIST, and keeps a steady 4.8 GHz (temperatures stay below 70°C). This is for testing purposes, and I did it yesterday. I’ve spent hours researching Cstates and similar topics. I know what they do, but my board only lets me select a general package from C0 to C9 or leave it automatic—this is where I’m stuck. Other advice suggests enabling c3 and c6, though I’m not sure if that’s still valid since I can go up to C9. I never overclocked before because I didn’t need to, but dynamic overclocking is what I enjoy now. It’s causing instability. Also, c1e was off by default when EIST was enabled, which might have contributed. My build specs are: - 32GB Corsair Vengeance DDR4 2666MHz RAM - MOSO BOBO MSI Z270 SLI Plus - CPU: i7-7700K - GPU: Gigabyte GTX 1080 Gaming Edition (which also self-tunes via GPU dynamic) In short, I’m trying to find a way to maintain my dynamic clocking without it becoming unstable. Any suggestions would be greatly appreciated!
A
Acullis
05-04-2017, 02:35 AM #1

Hey there, I've been dealing with a kernel-41 problem for quite some time with my build from last year. At first, I thought it was hardware-related, but after months of troubleshooting the wrong way, I realized instability might be the real culprit during dynamic overclocking. The kernel 41 is quite unpredictable—sometimes it works three times a day, other times it lasts days, and occasionally it restarts completely, whether idle or not. It mostly happens when idle, though. I shared my experience a while back, and someone with a similar issue suggested a fix. You can check the linked post for details: They mentioned turning off EIST resolved it for them, though their English wasn’t perfect and they weren’t entirely sure what they did. I tried other fixes before, but only now did I consider overclocking instability. Right now, I’m using the auto-overclock feature OC GENIE 4, which disables C states, turbo, EIST, and keeps a steady 4.8 GHz (temperatures stay below 70°C). This is for testing purposes, and I did it yesterday. I’ve spent hours researching Cstates and similar topics. I know what they do, but my board only lets me select a general package from C0 to C9 or leave it automatic—this is where I’m stuck. Other advice suggests enabling c3 and c6, though I’m not sure if that’s still valid since I can go up to C9. I never overclocked before because I didn’t need to, but dynamic overclocking is what I enjoy now. It’s causing instability. Also, c1e was off by default when EIST was enabled, which might have contributed. My build specs are: - 32GB Corsair Vengeance DDR4 2666MHz RAM - MOSO BOBO MSI Z270 SLI Plus - CPU: i7-7700K - GPU: Gigabyte GTX 1080 Gaming Edition (which also self-tunes via GPU dynamic) In short, I’m trying to find a way to maintain my dynamic clocking without it becoming unstable. Any suggestions would be greatly appreciated!

M
matze07
Junior Member
4
05-04-2017, 03:38 AM
#2
I own a 7700k and an MSI mobo (x270 Titanium) and I'm really sorry to hear about your issues. The only changes I've made are on the fans; everything else remains standard. You should be able to run this too—without any power interruptions.

Consider getting a computer monitor, such as HWinfo64, and test it through a session to check for thermal warnings before the 41. If no thermal alerts appear, the problem likely lies with a faulty power part or a short circuit.

Do you have an on-board GPU? If yes, use it in the next steps.

Recommendations:
1. Reset the CMOS.
2. Take the CPU out, blow it with compressed air carefully, and reposition it. Make sure no metal parts are trapped inside.
3. Disconnect all power cables and reattach them properly (both ends).

I understand you've already tried these steps. Please let me know your outcome or how you're feeling about my advice. I suspect a defective component and I'm here to help locate it instead of masking it.
M
matze07
05-04-2017, 03:38 AM #2

I own a 7700k and an MSI mobo (x270 Titanium) and I'm really sorry to hear about your issues. The only changes I've made are on the fans; everything else remains standard. You should be able to run this too—without any power interruptions.

Consider getting a computer monitor, such as HWinfo64, and test it through a session to check for thermal warnings before the 41. If no thermal alerts appear, the problem likely lies with a faulty power part or a short circuit.

Do you have an on-board GPU? If yes, use it in the next steps.

Recommendations:
1. Reset the CMOS.
2. Take the CPU out, blow it with compressed air carefully, and reposition it. Make sure no metal parts are trapped inside.
3. Disconnect all power cables and reattach them properly (both ends).

I understand you've already tried these steps. Please let me know your outcome or how you're feeling about my advice. I suspect a defective component and I'm here to help locate it instead of masking it.

E
Exfamous
Junior Member
21
05-04-2017, 03:57 AM
#3
I haven't reconfigured the CMOS or replaced the CPU (some users reported fixing a similar problem). I ran the built-in CPU graphics for a short time without issues, and so far it hasn’t triggered any problems. It might be a hardware issue—I already have an RMA for the GPU that’s valid for 30 days. I’ve also reattached the power cables. Honestly, my heatsink is quite problematic, so I didn’t reseat the CPU because removing it from the backboard is difficult and would require extra effort. Regarding the software, did you run a stress test to check for crashes? I’m currently at work and can’t perform that now. Also, was C1E enabled or disabled by default on your board? Our boards are similar, but I’m wondering if it should be turned on initially.
E
Exfamous
05-04-2017, 03:57 AM #3

I haven't reconfigured the CMOS or replaced the CPU (some users reported fixing a similar problem). I ran the built-in CPU graphics for a short time without issues, and so far it hasn’t triggered any problems. It might be a hardware issue—I already have an RMA for the GPU that’s valid for 30 days. I’ve also reattached the power cables. Honestly, my heatsink is quite problematic, so I didn’t reseat the CPU because removing it from the backboard is difficult and would require extra effort. Regarding the software, did you run a stress test to check for crashes? I’m currently at work and can’t perform that now. Also, was C1E enabled or disabled by default on your board? Our boards are similar, but I’m wondering if it should be turned on initially.

D
Danil_0705
Junior Member
5
05-07-2017, 02:26 PM
#4
My 'C1E' is turned off by default. (But now you're making me think)
Anyway, good luck and I'll keep an eye on your progress.
D
Danil_0705
05-07-2017, 02:26 PM #4

My 'C1E' is turned off by default. (But now you're making me think)
Anyway, good luck and I'll keep an eye on your progress.

Z
Zmondy
Senior Member
405
05-13-2017, 08:17 AM
#5
I tested the software and it appeared normal, though OC genie has been active without problems. This strengthens the possibility that a BIOS setting, particularly c1e, is involved. If this isn't resolved, I'd consider disabling EIST since it's not a high-impact change at version 4.4 from 4.2. If it fails, I'll disable it completely. Generally, the most recent software-related changes haven't caused the issue, but without a reboot and dynamic OC, it's likely the root cause.
Z
Zmondy
05-13-2017, 08:17 AM #5

I tested the software and it appeared normal, though OC genie has been active without problems. This strengthens the possibility that a BIOS setting, particularly c1e, is involved. If this isn't resolved, I'd consider disabling EIST since it's not a high-impact change at version 4.4 from 4.2. If it fails, I'll disable it completely. Generally, the most recent software-related changes haven't caused the issue, but without a reboot and dynamic OC, it's likely the root cause.

9
905xA
Senior Member
667
05-19-2017, 02:51 PM
#6
I've never adjusted an OC manually except for RAM, and I don't want my PC to keep a ridiculous clock IDLe, so if that's the case and I can't do dynamic I'm at a loss since I don't want to damage my $2000 machine. :| I also heard from a colleague that he faced a similar problem where his motherboard refused to accept his RAM, causing random buffer hits and restarts, which forced him to underclock it—if that's the case, I have no idea what timings would cause such an issue, like forcing it down to 2400.
9
905xA
05-19-2017, 02:51 PM #6

I've never adjusted an OC manually except for RAM, and I don't want my PC to keep a ridiculous clock IDLe, so if that's the case and I can't do dynamic I'm at a loss since I don't want to damage my $2000 machine. :| I also heard from a colleague that he faced a similar problem where his motherboard refused to accept his RAM, causing random buffer hits and restarts, which forced him to underclock it—if that's the case, I have no idea what timings would cause such an issue, like forcing it down to 2400.