• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

core and memory clock issues while playing WoW

Associate
Joined
22 Nov 2004
Posts
1,428
I've noticed stutters in game since i started playing it again a month or so ago but i havn't played it that much to be bothered by it and assumed it was just a poor install or something.

But anyway i loaded up afterburner and gpuz today as well as windows task manager so i could monitor the performance of my components so while playing to see if i could spot what was causing it.

My CPU was running around 22-30%
GPU Core clock was around 400mhz
GPU Mem clock was around 625mhz

This was during a raid, dungeon and general wondering around.

I figured it might be because the game isn't very taxing on hardware but i think the low clocks are causing the issue. Is there any way to force GPU clocks?

Edit: specs in sig
 
Last edited:
I just tried a few random games, i'm going to try a couple more but i thought i'd post to give you some info for now.

Tried 2 more older games so i have a broad selection of results

CS 1.6 core 300ish/mem 625ish
CS GO core 300ish/mem 625ish

At this point i wondered if it was something to do with having 2 screens on so i disabled the second display.

I loaded up Rust and the core stayed around 300 but the memory went down to 150.


Edit: It was afterburner causing the issue, although i'm not sure why it had done it. The sliders were all the way to the left on the core and mem, possibly been like it since i installed the 14.9 drivers the other week. Although it doesn't explain the stuttering in WoW over the last couple of months. I might try rolling back a few drivers to see if this resolves that particular issue, i know it hasn't been down clocked for long because i did some bench marking just after i installed the new drivers.
 
Last edited:
Back
Top Bottom