F5F Stay Refreshed Hardware Desktop Processor became stuck at 3193 MHz

Processor became stuck at 3193 MHz

Processor became stuck at 3193 MHz

M
MagicTroll_PVP
Junior Member
19
10-21-2016, 01:25 PM
#1
It seems your i5 4570s was running smoothly at 3.6GHz but suddenly stuck at 3193MHz under demanding games. There might be a stability or thermal issue affecting performance. Checking for overheating, firmware updates, or adjusting BIOS settings could help. If the problem persists, consider testing with a different cooler or checking for driver conflicts.
M
MagicTroll_PVP
10-21-2016, 01:25 PM #1

It seems your i5 4570s was running smoothly at 3.6GHz but suddenly stuck at 3193MHz under demanding games. There might be a stability or thermal issue affecting performance. Checking for overheating, firmware updates, or adjusting BIOS settings could help. If the problem persists, consider testing with a different cooler or checking for driver conflicts.

P
PatrickJosh
Member
109
10-21-2016, 06:13 PM
#2
The 4570S reaches up to 3.6 GHz with one core running. Ensure C states are turned on in the BIOS for optimal performance. At full power with all four cores engaged, it hits 3.2 GHz. http://www.cpu-world.com/CPUs/Core_i5/Intel-Core i5-4570S.html
P
PatrickJosh
10-21-2016, 06:13 PM #2

The 4570S reaches up to 3.6 GHz with one core running. Ensure C states are turned on in the BIOS for optimal performance. At full power with all four cores engaged, it hits 3.2 GHz. http://www.cpu-world.com/CPUs/Core_i5/Intel-Core i5-4570S.html

K
kiddswagg_760
Member
211
10-22-2016, 01:50 AM
#3
C states are also activated.
K
kiddswagg_760
10-22-2016, 01:50 AM #3

C states are also activated.

D
DarckoXD
Junior Member
10
10-22-2016, 06:32 AM
#4
Consider testing ThrottleStop with the provided link. Ensure your BIOS has the correct turbo ratio settings—36, 35, 33, 32 for each core count. A recent Windows update might be interfering. Check the C states window in ThrottleStop to confirm idle CPU states are active. Minimize background processes so cores stay in low-power mode. In intense games, only use the 32 multiplier. Enable the Log File option in ThrottleStop and run a game to monitor changes. Record the FIVR and TPL windows during the test. Upload screenshots of both the logs and the monitoring interfaces.
D
DarckoXD
10-22-2016, 06:32 AM #4

Consider testing ThrottleStop with the provided link. Ensure your BIOS has the correct turbo ratio settings—36, 35, 33, 32 for each core count. A recent Windows update might be interfering. Check the C states window in ThrottleStop to confirm idle CPU states are active. Minimize background processes so cores stay in low-power mode. In intense games, only use the 32 multiplier. Enable the Log File option in ThrottleStop and run a game to monitor changes. Record the FIVR and TPL windows during the test. Upload screenshots of both the logs and the monitoring interfaces.

S
SpacinetiX
Junior Member
46
10-22-2016, 08:08 AM
#5
Game.txt contains images and documents. Most tests ran smoothly at 3200 MHz.
S
SpacinetiX
10-22-2016, 08:08 AM #5

Game.txt contains images and documents. Most tests ran smoothly at 3200 MHz.

T
Taybaybay
Posting Freak
850
10-23-2016, 02:46 PM
#6
Your system logs indicate Intel turbo boost functions properly during gaming. The CPU remains in C0 state for about 80% to 90% of the time, meaning all four cores are engaged and the multiplier stays at a maximum of 32.00. This is typical behavior. Your single-threaded log also reflects similar activity levels, matching the gaming performance. To verify, disable ThrottleStop and clear any old logs. Once stopped, a new log will appear. After completion, run a one-thread benchmark test. When finished, safely end ThrottleStop to finalize your data. This process helps ensure you’re not missing background processes that could affect performance. If your setup is correct, an idle CPU should show minimal activity in the C0 state, with System Idle at 98% or higher. Excess background tasks can force more cores to stay on, lowering the multiplier. The Core i5-4570S supports only four cores and four threads, which may limit performance in newer games.
T
Taybaybay
10-23-2016, 02:46 PM #6

Your system logs indicate Intel turbo boost functions properly during gaming. The CPU remains in C0 state for about 80% to 90% of the time, meaning all four cores are engaged and the multiplier stays at a maximum of 32.00. This is typical behavior. Your single-threaded log also reflects similar activity levels, matching the gaming performance. To verify, disable ThrottleStop and clear any old logs. Once stopped, a new log will appear. After completion, run a one-thread benchmark test. When finished, safely end ThrottleStop to finalize your data. This process helps ensure you’re not missing background processes that could affect performance. If your setup is correct, an idle CPU should show minimal activity in the C0 state, with System Idle at 98% or higher. Excess background tasks can force more cores to stay on, lowering the multiplier. The Core i5-4570S supports only four cores and four threads, which may limit performance in newer games.

K
KrozenFire
Member
124
10-26-2016, 02:34 PM
#7
Looks like there are no background jobs left. I cleared all log files, paused for roughly 20 seconds, and launched a test titled 2020-05-07.txt.
K
KrozenFire
10-26-2016, 02:34 PM #7

Looks like there are no background jobs left. I cleared all log files, paused for roughly 20 seconds, and launched a test titled 2020-05-07.txt.

C
cyberkrieger
Member
171
10-26-2016, 03:53 PM
#8
I'm facing a similar problem with no resolution. This started after a BIOS update, and despite trying a clean reinstall of Windows 10, adjusting the CPU voltage, and turning off Superfetch, nothing has changed. I suspect the update might have caused the issue for my system.
C
cyberkrieger
10-26-2016, 03:53 PM #8

I'm facing a similar problem with no resolution. This started after a BIOS update, and despite trying a clean reinstall of Windows 10, adjusting the CPU voltage, and turning off Superfetch, nothing has changed. I suspect the update might have caused the issue for my system.