F5F Stay Refreshed Power Users Overclocking Wattman slows my card without any effort

Wattman slows my card without any effort

Wattman slows my card without any effort

B
blueyednick
Member
Find
199
12-22-2016, 09:29 PM
#1
I am using driver 17.5.2. On Wattman, my state 7 (max) is displayed as 650 instead of the actual 1250. What should I do?
EDIT: The photo shows 1250 on the stat monitor on the left, but that was because I set it to 1250mhz when I noticed it was at 650mhz, and then changed it back to 650mhz for this forum post. It happens every time I boot.
Reply
Reply
B
blueyednick
12-22-2016, 09:29 PM #1

I am using driver 17.5.2. On Wattman, my state 7 (max) is displayed as 650 instead of the actual 1250. What should I do?
EDIT: The photo shows 1250 on the stat monitor on the left, but that was because I set it to 1250mhz when I noticed it was at 650mhz, and then changed it back to 650mhz for this forum post. It happens every time I boot.

Reply
Reply
L
LFPC
Member
Find
98
12-22-2016, 11:01 PM
#2
Restore settings to the standard in Wattman, execute a benchmark or any task to engage your GPU, and check the core clock speed. If it remains insufficient, proceed with a complete driver uninstallation and reinstallation.
Reply
Reply
L
LFPC
12-22-2016, 11:01 PM #2

Restore settings to the standard in Wattman, execute a benchmark or any task to engage your GPU, and check the core clock speed. If it remains insufficient, proceed with a complete driver uninstallation and reinstallation.

Reply
Reply
S
Siked
Member
Find
114
12-28-2016, 11:00 AM
#3
Restore settings to the standard in Wattman, execute a benchmark or any task to engage your GPU, and check the core clock speed. If it remains insufficient, proceed with a complete driver uninstallation and reinstallation.
Reply
Reply
S
Siked
12-28-2016, 11:00 AM #3

Restore settings to the standard in Wattman, execute a benchmark or any task to engage your GPU, and check the core clock speed. If it remains insufficient, proceed with a complete driver uninstallation and reinstallation.

Reply
Reply
W
WhiteMurderPVP
Junior Member
Find
12
01-02-2017, 08:29 PM
#4
TJ Hooker suggests resetting settings in Wattman, running a benchmark or loading your GPU, and checking the core clock speed. If it remains low, he recommends a clean uninstall and reinstall of drivers. He mentions doing a clean install first, then updating to 17.5.2, which resolved the problem, but now the issue is fixed with 17.7.2.
Reply
Reply
W
WhiteMurderPVP
01-02-2017, 08:29 PM #4

TJ Hooker suggests resetting settings in Wattman, running a benchmark or loading your GPU, and checking the core clock speed. If it remains low, he recommends a clean uninstall and reinstall of drivers. He mentions doing a clean install first, then updating to 17.5.2, which resolved the problem, but now the issue is fixed with 17.7.2.

Reply
Reply