14700 (non-K) "stuck" on 3GHz

[Shini1]

Hello there!

I got a i7-14700 and whenever I start a stress test for example with CPU-Z, I can see that my CPU boosts to 5Ghz, then after 2 seconds it always locks itself to 3Ghz (45Celsius) and does not go back up.

I tried it in 2 different setups and does the same. Can this be considered faulty, maybe an internal power regulator is faulty? I'm guessing here. Can this be just a wrongly setup BIOS in my motherboard? Or is this normal?

Sometimes it crashes from games and also the PC can restart as well.

Setup:

Mobo: Asus Rog Z690 D4 with newest bios.
64gb RAM
RTX 3080
1000W +80 PSU

3 fan Asus rog AIO watercooler

Thanks in advance!

[pressed_for_time]

Have you updated all your drivers as well? Particularly the Intel Management Engine Interface driver. The easiest way to do this is ASUS DriverHub - which can be downloaded from here  - if you are not already using it.

I would recommend using the Intel Default Settings in the BIOS, not altering other settings and not over-riding the BIOS with any form of software.

Trying the CPU-Z Bench I do not get the 3 GHz locking issue with CPU-Z 2.16. This is probably something that needs to be reported to CPUID, the authors of CPU-Z.

[Shini1]

Hey!

Yes, I tried that, all my drivers are up to date thankfully.

Maybe my cpu is infected with this?

https://community.intel.com/t5/Blogs/Tech-Innovation/Client/Intel-Core-13th-and-14th-Gen-Desktop-Instability-Root-Cause/post/1633239

It says that it can cause blue screens, instability, I also read that cpu's with 65w base power have a higher chance to get this issue.

Cheers

[AlHill]

run the IPDT:

https://www.intel.com/content/www/us/en/support/articles/000005567/processors.html

Doc (not an Intel employee or contractor)
[IDSA needs to be abandoned, uninstalled and forgotten]

[pressed_for_time]

That issue only affected the unlocked multiplier K, KF and KS 13th and 14th gen i5, i7 and i9 CPUs. It was fixed by a series of BIOS and driver updates by around November 2024. There has been a recent BIOS and Intel ME firmware update to clear a small remaining potential issue. As your processor is non-K it is not affected.