Running Windows Experience Index causes down-clock of HD 5850

May 5, 2006
96
0
0
Trying to figure this out and I haven't had much success. This happens at both stock speeds and slightly overclocked at 765/1115. I'm watching the clock speeds in the sensor tab of GPU-z.

I start the Windows Experience Index test showing 725/1000, as is normal for a stock HD 5850. Once I get about halfway through the test, I see the clocks change to 400/900. On subsequent runnings of the WEI, it starts and ends at the 400/900 speed. The only way to return to the correct 725/1000 is to restart the system. Changing values in CCC does nothing. So if I play a game or benchmark after running the WEI, I obviously have much poorer performance overall (i.e. 7250 furmark score vs. 4000 @ 400/900).

I tried both the previous ATI driver for the 5850 dated in Sept, as well as the one that was just released today (Oct 13th). Same issue with both. Running Windows 7 RC x64. Is WEI known to fool with & lock clock speeds like this? Driver issue? Problem with my Windows installation? Diagnostic/repair attempts show nothing wrong.
 

OCGuy

Lifer
Jul 12, 2000
27,224
37
91
Doesnt your card always downclock when it isnt in 3D apps? Or does the 5XXX series work differently?

One fix is using Rivatuner and "force 3d mode" under the options, but you shouldnt have to do that.

On the other hand, if WEI is the only problem, is it really a problem?
 
May 5, 2006
96
0
0
Correct, it downclocks the core to 400 for 2D stuff or when I'm just at the desktop, which is as it should be. But the WEI problem is that it forces the 400/900 clock speed for all subsequent use until you restart the system. Not that I love running WEI or anything, it's pretty useless, I was just trying to figure out why my GPU was gimped as a result of it. I first figured there was something wrong when my WEI graphics scores showed up as 6.0/6.0, which is way lower than it should be (E8400 @ 3.5, 4GB DDR2)

Just wondering if anyone else experienced the same. I definitely want to keep the downclock functionality - at least how it's supposed to work.