• 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.

Varied clock speeds when GPU is inactive...

Associate
Joined
2 Oct 2013
Posts
4
Location
United Kindgom
Hey guys,

I have an EVGA GTX 580 (1GB) and I have recently downloaded the EVGA Precision X application in order to try and diagnose some Battlefield 4 FPS issues...

While I was watching my GPUs performance I noticed that while my GPU was idle(no games/applications were running) that the GPUs clock speeds were constantly changing between the following values:

-50 MHz:
4GwRE.png
-405 MHz:
4GwT9.png
-772 MHz:
4GwVm.png
 
Last edited:
Mine do this according to precision, tend to find it's more when I'm watching a video on youtube or a twitch stream.
 
Mine do this according to precision, tend to find it's more when I'm watching a video on youtube or a twitch stream.

Thanks for the reply but when I say that no applications were running at all, I literally mean:

I did a clean install of Windows 8, installed my drivers, installed EVGA Precision X and then sat on my desktop and watched it happen there and then.
 
Last edited:
My gpu while it is amd but I has the same behaviour it simply down clocks when it is not being used to save power. Your CPU will do the same but it only happens when no load is applied to your gpu and cpu.

What issuse are you having with bf4 and what is your cpu? I did notice that your gpu is only 1gb the problem with that is that it is recommended that you need 2gb of vram this may be your issue so you may need to whack all the settings down to low.

Don't forget it is in beta so it will not be optimised as well as it will be when the final release comes.
 
Last edited:
My you while it is amd but I has the same behaviour it simply down clocks when it is not being used to save power. Your CPU will do the same but it only happens when no load is applied to your gpu and cpu.

what issuse are ypu having with bf4 and what is your cpu. I do notice that your you is only 1gb the problem with that is that it is recommended that you need 2gb of gram this may be your issue though you may need to whack all the settings down to low.

Don't forget it is in beta so it will not be optimised as well as it will be when the final release comes.

This thread isn't really about the BF4 problem it was more to do with the fact that there was a varied clock speed result while my system was idle but seeing as you are showing interest in my BF4 situation I will elaborate.

When BF4 was released on the Tuesday I noticed that I was receiving about 5-10 FPS, so I decided to troubleshoot this problem by installing Windows 8 and the NVIDIA BETA driver(331.40) after doing this I noticed that my FPS was still at an unplayable framerate(10-25 FPS) so I decided to seek information from the Battlelog forums and soon enough I found out that if you close Battlelog from behind the game once it has loaded up and then set your game's process priority to 'Low' then you notice a much more playable frame rate of(25-59 FPS) obviously this FPS is varied because the game is still in BETA and not optimised very well.
 
Last edited:
Just tested mine for 15min on a clean boot.

It still does it, after a quick read up elsewhere it will do it whenever anything accesses the gfx card be it something in the background on windows or something your doing.

Perfectly normal from what I've found.
 
Just tested mine for 15min on a clean boot.

It still does it, after a quick read up elsewhere it will do it whenever anything accesses the gfx card be it something in the background on windows or something your doing.

Perfectly normal from what I've found.

Thanks for that dude, I feel much better knowing that it isn't just me.

P.S: Something that might interest you is that when my friend who has an ATI GPU used a GPU monitoring program such as EVGA Precision X he did not notice the same issue that I have stated above so this may well also be something to do with NIVIDIA GPUs only...
 
Back
Top Bottom