
UNSOLVED
Closed
B
BedazzledUK
11 Posts
0
18845
October 4th, 2005 09:00
SpeedStep won't disable fully
I'm trying to run Grand Prix Legends on my Inspiron 6000 and SpeedStep is causing some strange problems. I've tried disabling it using control panel / power options / "always on" but, according to SpeedSwitchXP, the CPU speed is still varying between about 1.0GHz and 1.6GHz depending on processor load and this is confusing the game into running too slowly.
Bizarrely, if I run WinThrottle and limit the maximum CPU speed to 50%, the game runs fine. I think this is effectively fixing the CPU speed at 1GHz, but as a result I can't make full use of the computer's power and the game suffers accordingly.
(I've tried disabling SpeedStep in the BIOS and again the game then runs properly, but this forces the CPU to run at its lowest frequency so the game is unplayable).
So my questions:
1. Why is the CPU speed still varying when I have supposedly disabled SpeedStep?
2. How can I disable SpeedStep fully so that GPL works properly at 1.6GHz?
3. Is there any risk to the computer if it constantly runs at 1.6GHz (e.g. too hot)?
Thanks in advance!
Responses (6)
Solutions (0)
BedazzledUK
11 Posts
794
0
Posted October 4th, 2005 17:00
Message Edited by BedazzledUK on 10-04-2005 08:01 PM
BedazzledUK
11 Posts
794
0
Posted October 4th, 2005 18:00
I just found this : http://www.techspot.com/vb/all/windows/t-16513-FPS-Drop-in-CS-and-other-Games.htmlI've got BIOS A07 and it seems that this has some built-in (and over zealous) hardware throttling for the CPU. Apparently installing BIOS A06 solves the problem, but I'm reluctant to try this - can anyone give more advice on this? (especially someone from DELL!).Maybe I'll have to use my new computer whilst it is sitting inside a fridge...!BedazzledUK
11 Posts
794
0
Posted October 4th, 2005 22:00
Fred,
You were absolutely right - I've just tried it again after leaving the computer off for a few hours and when I switched it back on it ran at a steady 1.6GHz for 5-10 minutes then when it warmed up it switched into the variable CPU speed mode, so it's definately a thermal issue.
The question is, should I load the older BIOS to get round this problem?
BedazzledUK
11 Posts
794
0
Posted October 5th, 2005 14:00
Ok, I've cracked this without having to mess around with the BIOS! It's really simple - I've just written a tiny VB application that creates an infinite loop that just issues a "DoEvents" command so that Windows can function normally:
Do
DoEvents
LoopThe loop forces the CPU to run at maximum speed and uses hardly any processing power itself so games etc run perfectly. Just compile it to an EXE and run it in the background when you are playing games. You also need to disable speedstep first by setting the power options to "always on" in the control panel. I monitored the CPU temperature while it was running and it stays at 50 degreesC with continued use (which is slightly higher than normal but ok I think).... sorted!
I've extended it to also display the CPU speed while it is running:
Set objProc = GetObject("winmgmts:root\cimv2:Win32_Processor='cpu0'")
Reset = False
Do
If (Timer - StartTimer > 1) And Reset = False Then
CPUspeed.Caption = objProc.CurrentClockSpeed
StartTimer = Timer
End If
DoEvents
Loop Until Reset = TrueMessage Edited by BedazzledUK on 10-05-2005 12:23 PM
- THANK YOU!!! This was the ONLY fix that helped me to run the original Unreal Tournament properly on my precision m90 without rendering my 2.33ghz dualcore to 600mhz with a bios Speedstep disable, screwing around with render patches or other tweaks that didn't do squat!

fred_nd
7 Posts
794
0
Posted October 4th, 2005 17:00
For me the solution was to blow compressed air (from one of those cans) into the processor cooling vents on the back. It seems that the dust collected was enough to stop the cooling from doing what it should.
I guess that the total life time of the computer will be lowerd if running to how for a long time. I have forgotten mine on while having it in my backpack and then it have just shut down (and been complayning loudly afterwards ;).
Hope it helps.