UT Engine and AMD Cool n' Quiet

[Slaimus]

I have been getting horrible stuttering in UT engine games when CnQ is enabled.
In UT2004 multiplayer, it is not very noticable, probably because the tickrate is fairly low, but in single player it is very hard to aim with the stuttering.
In UT99, it is downright trippy. In multiplayer, people are teleporting all over the place, and in single player, the game goes hyper fast and then Matrix-like slow randomly.
I know it is definitely CnQ since it goes away if I set the power setting to anything higher than Minimal. I have also tried using CrystalCPUID to control the clock throttling, but the same thing happens.
This may be related to the way the engine determines the tickrate, as it may set the tickrate while the CPU is throttled, and then executed while it is in full speed.

Anyone else experience this?

 

[Pr0d1gy]

I have been experiencing crashes during gameplay & some stuttering on my new AMD rig. I'm pretty sure I have CnQ enabled as well, guess I should turn it off. The only game I have played so far is UT2004 as well.

 

[jim1976]

what did you expect with such low fsb?

Disable it in order to play 3dapplications.

 

[Lonyo]

Does it happen when the CPU is at stock speeds?

 

[Pr0d1gy]

I have no idea what you're talking about? My fsb should be 200 if I remember correctly?

Originally posted by: Lonyo
Does it happen when the CPU is at stock speeds?

Yeah, mine is running at stock speeds. The only thing I have done is run my RAM at 2-2-2-5 timings & upped the PSU about .5-1v in order to allow for that.

 

[sandorski]

Turn it off. Unreal based games are very cpu intensive, CnQ seems to be interering with it. If it still runs crappy, something else is to blame.

 

[m3rcury]

There was a known bug with CnQ where if the processor was running slow, and then you immediately started an app that took 100% cpu, then the cpu wouldn't go back to its full speed. It happens because the cpu can only switch clock speeds during a NOOP (idle clock cycle). So if you start a 100% intensive app, it remains stuck in the slower speed. Thus if you go from desktop usage (the cpu runs slow), into some 3d app like UT (uses lot of cpu), then UT will still be running on the 'slower cpu'.

MS was supposed to come out with a patch to fix this. Or maybe it was AMD. No idea if they did.