Gigabyte 980 ti Core clock remains stuck at 405MHz, unsure of the cause or solution.
Gigabyte 980 ti Core clock remains stuck at 405MHz, unsure of the cause or solution.
Gigabyte 980 ti Core clock is stuck at 405MHz instead of the expected 1450MHz, and I’m unsure why or how to resolve it. After resetting the settings in Afterburner it didn’t change, so I checked for a driver update but was using version 361.75 as of February 2, 2016. I just turned my computer on earlier today and it worked fine, but after shutting it off for about four hours, it started behaving oddly around 20 minutes ago. Any advice or explanations would be greatly appreciated.
Verify the central clock under stress in a game or benchmark. Execute 3Dmark to observe if performance drops unexpectedly. An unusually low score indicates an issue, otherwise it's likely nothing to worry about. The 405MHz frequency is typical for cards in 2D mode or within Windows settings. Also, note that 1450MHz is quite high for a card to reach without overclocking—are you certain it will go that far?
Verify the central clock under stress in a game or benchmark. Execute 3Dmark to observe if your score drops unexpectedly. An unusually low result indicates an issue, otherwise it's likely nothing to worry about. The 405MHz frequency is typical for cards in 2D mode or within Windows settings. Also, note that 1450MHz is quite high for a card to reach without overclocking—are you certain it will go that far?
Check the core clock under load in a game or benchmark. Run 3Dmark to verify if you receive an unexpectedly low score. If you see such a score, it indicates an issue, otherwise it’s probably nothing to worry about. The frequency of 405MHz is typical for cards in 2D mode or within the Windows environment. Also, 1450MHz is quite high for a card to reach without overclocking—are you certain it will go that far?
At first, I reinstalled the driver and it resolved the problem. However, after loading SWBF, it displayed a slide show and didn’t exceed 405 MHz. I fixed it temporarily, but now it’s an overclock situation.