F5F Stay Refreshed Hardware Desktop Processor halted at 0.99GHz with a 6x boost factor

Processor halted at 0.99GHz with a 6x boost factor

Processor halted at 0.99GHz with a 6x boost factor

A
AyyLmaokai
Member
124
04-09-2016, 05:57 PM
#1
The multiplier on your Core 2 Duo T5850 appears fixed at 6x and won’t adjust despite attempts. ThrottleStop increases the speed but doesn’t update the processor, keeping it stuck at 0.99ghz. The clock mod adjustment seems to work differently, which is unusual. Recent disassembly and repasting might have affected the CPU settings. At 0.99ghz on both cores, performance is limited. Consider software that can bypass these restrictions or explore alternative solutions.
A
AyyLmaokai
04-09-2016, 05:57 PM #1

The multiplier on your Core 2 Duo T5850 appears fixed at 6x and won’t adjust despite attempts. ThrottleStop increases the speed but doesn’t update the processor, keeping it stuck at 0.99ghz. The clock mod adjustment seems to work differently, which is unusual. Recent disassembly and repasting might have affected the CPU settings. At 0.99ghz on both cores, performance is limited. Consider software that can bypass these restrictions or explore alternative solutions.

D
DantehIsGay
Posting Freak
902
04-10-2016, 10:19 PM
#2
Here are some images to show your configuration. It's simple to capture brief details while taking apart the device. BD PROCHOT or clock modulation throttling can be applied afterward. Static electricity poses a hidden threat.
D
DantehIsGay
04-10-2016, 10:19 PM #2

Here are some images to show your configuration. It's simple to capture brief details while taking apart the device. BD PROCHOT or clock modulation throttling can be applied afterward. Static electricity poses a hidden threat.

E
EggsyDiamond
Member
166
04-14-2016, 03:09 PM
#3
It appears the mistake was expected; turning on SpeedStep resolved the problem. Usually I turn it off for Core 2 Duos since they run at full speed, but this one behaves differently. Appreciate your help.
E
EggsyDiamond
04-14-2016, 03:09 PM #3

It appears the mistake was expected; turning on SpeedStep resolved the problem. Usually I turn it off for Core 2 Duos since they run at full speed, but this one behaves differently. Appreciate your help.