Intel 10th Gen Core i7 stuck at 0.79Ghz and I applied a fix that works, but I don’t understand why this needs to be done?

4 months ago I sent my ASUS ROG Strix to ASUS for repair. The main reason was the CPU running at 0.79Ghz.

Since then I have gotten my laptop back and it worked fine, it also worked fine with Windows 11 for the past 4 months.

Today I noticed extreme lag. I checked the performance tab in Task Manager and the CPU was stuck at 0.79Ghz.

I then said to myself “It must be the software.”

So I did a clean install of Windows 11 and the problem persisted.

Then I made a clean install of Windows10 and the same problem; CPU stuck at 0.79Ghz.

Then I was fed up and I reinstalled clean Windows 11 and still had the problem.

I contacted ASUS and they just told me to send it in for repair.

But then I checked on Google a bit with the only 700Mhz I had.

I found out some Intel CPUs get throttled down to that speed for a reason I can’t even imagine.

So what I found is an application called ThrottleStop. I’ve uncheck a box with the option called BD PROCHOT. I have no clue what this option is but now my CPU is back up running as it should, 2.6Ghz at normal and 4.2Ghz at turbo.

Is anyone aware of this issue?

I’m not new to PCs but I don’t even know what that checkbox changed in the software for my CPU to start running as it should be.

The fact that I needed software fix for a new CPU is mind boggling. I document all I do such as troubleshooting and all. I feel that ASUS must replace the CPU with its defects.

Solution 1:

The problem is that one of your system thermal sensors is triggering a thermal overload protection in your CPU.

From the Intel CPU Datasheet

5.2.1.3.1 Bi-Directional PROCHOT#

By default, the PROCHOT# signal is defined as an output only. However, the signal may be configured as bi-directional. When configured as a bi-directional signal, PROCHOT# can be used for thermally protecting other platform components should they overheat as well.

By default PROCHOT# is a signal that the CPU tells the system that it is thermally throttling due to overheating. Your system firmware can choose to reconfigure that signal to be bi-directional and essentially change it to BD PROCHOT#.

When in this mode thermal sensors in your chipset or other devices can be used to signal the CPU that the system is experiencing abnormal temperatures and should throttle as a result. What it doesn't do is tell the CPU where the problem lies, it is entirely an all or nothing "something, somewhere is wrong." type signal.

By disabling BD PROCHOT# using ThrottleStop you are switching back to the "old" style where the CPU controls itself and nothing else matters. The CPU will ignore thermal warnings from the wider system and only throttle when it is overheating itself.

I would recommend using a program such as hwinfo to look at all the sensors available in your system to see if there are any that are showing high temperatures.