0

I have an Asus Nvidia Geforce GTX 550TI In my system. For some reason, a short time after booting up my PC it's clock rates will drop to their minimums

screenshot

regardless of the load on the card.

For example, I can run a game a few minutes after booting up and it runs at 60fps no problem for say about 10 minutes, with the clock speeds at their normal values. But then suddenly the clocks drop down to the minimum and even with 100% usage on the GPU they stay there and my framerate drops to ~2fps.

I have MSI afterburner installed which as far as I know is the only non-system program that has control of the GPU clock speeds. But I only use that for fan control and on-screen display. The clocks and voltage are left at their default values

MSI afterburner screenshot.

Once the clock speeds fall to their minimum they stay there until i restart the PC and then the whole process starts again and it works fine for a little while before dropping back down again after a seemingly random amount of time.

Any ideas or help is appreciated.

Edit: It does appear to be Afterburner causing it, but strangely only when started with windows. If I uncheck the box to start afterburner with windows and restart then the card runs fine without afterburner running (ignoring the temperature) and then if I open afterburner and apply the fan control it seems to continue to run without any of the previous problems.

  • If you don't use Afterburner, for an ASUS card, any change? – Ramhound Sep 13 '16 at 11:28
  • If you are using the fan control to limit the fan speed then it may be that the card is getting too hot. Have you tried disabling the fan control? – Mokubai Sep 13 '16 at 11:41
  • @Ramhound see my edit to the original question – Jack Sep 13 '16 at 11:49
  • @Mokubai I don't think it's the temperature, I use the fan control to make sure the temperature is under control as it seems to stay at 30% fan speed without it regardless of temperature. With fan control, the temp is around 35 celsius – Jack Sep 13 '16 at 11:51
  • Then it is probably a problem with the MSI software not re-setting itself as the controller for the fan and clocks after the system comes out of the "fastboot" hibernation process. I've seen something similar in the past but can't remember what software it was. If disabling that software fixes the problem then either leave it disabled or see if there is an update from MSI. – Mokubai Sep 13 '16 at 11:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.