When I increase the clock speed, nothing occurs, especially after turning off EIST.
When I increase the clock speed, nothing occurs, especially after turning off EIST.
Hello, here are the details of my system
i9-10900kf
RTX 3080
colorful Z490 Vulcan x20
32GB RAM
Gamemax 1050W PSU
When I access BIOS and disable EIST (Intel SpeedStep), overclocking no longer functions.
I can adjust the core clock in BIOS, but it remains stuck at stock 3.7GHz.
I attempted to switch on/off Intel Speed Shift and Speedstep features, removed the CMOS battery and reinserted it, reset the BIOS, and tried various voltage settings from 1V to 1.5V.
Still, nothing changes.
When EIST is enabled, the system automatically selects the CPU core clock (typically between 4GHz and 4.8GHz), but even when I set it to 5GHz in BIOS, it still stays around 4GHz–4.8GHz.
I’m unsure if this is due to my motherboard or any other factor, but I urgently need assistance.
Thank you very much.
I purchased all the specifications from a local shop in the Middle East (Saudi Arabia) about 20 days ago. Yes, I’m confident the CPU is KF and not a cheap copy. Updated: After several attempts yesterday and hours of repeatedly clearing the CMOS to adjust BIOS settings, it finally worked. I changed EIST to ON and TDP Lock to On from the motherboard—it was off and disabled Intel speed shift tech. Now it’s running at a steady 5GHz, so I believe the issue is resolved. The TDP Lock seems to have fixed it.
The motherboard and CPU are likely quite old, and it's important to verify their purchase details to ensure authenticity.
I purchased all the specifications from a local store in the Middle East (Saudi Arabia) about 20 days ago. Yes, I'm confident the CPU is KF and not a cheap copy.
Update: After several attempts yesterday and hours of repeatedly clearing the CMOS to adjust BIOS settings, it finally worked.
I changed EIST to ON and TDP Lock to On from the motherboard—it was off and disabled Intel speed shift technology. Now I'm running at a steady 5GHz, so I believe the issue is resolved. The TDP Lock seems to have fixed it. I tried turning it on just to be sure, and everything is now working properly. Thanks everyone!
I hope this helps someone facing the same problem. Thank you all!