• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

clocking issue GTX 260

Toconator

[H]ard DCOTM January 2026
Joined
Jul 8, 2005
Messages
879
I've got an eVGA GTX260-216 which has been working fine since I got it. I run the eVGA Precision 2.0.0 tool and have mildly overclocked the card to 602/1512 with mem at stock and it happily folds away for the [H]orde. I also have a Logitech G15 so I can monitor the clocks on the LCD display. Everything goes fine until I play a game. Once I exit the game, the clocks go to 400/799/297 core/shader/mem and will not return to speed again unless I reboot. Running Win7 Pro x64 with 260.89 drivers. I have updated the drivers twice (was running the 195's, then the 258's) so it's not a driver issue. Moving the sliders or reset to default in Precision has no effect. wierd?
 
its because your drivers are crashing and locking the card in 2D mode.. im actually surprised you can even play games with the shader's at 1512.. most games cant handle more then 1458 on the shader clocks with the gtx 260..

my gtx 260 folded at 602/1512/1161 but i could only game at 630/1350/1161..


btw you can fix the 2D lock by reinstalling your drivers instead of rebooting.. which ever is the fastest..
 
its because your drivers are crashing and locking the card in 2D mode.. im actually surprised you can even play games with the shader's at 1512.. most games cant handle more then 1458 on the shader clocks with the gtx 260..

my gtx 260 folded at 602/1512/1161 but i could only game at 630/1350/1161..


btw you can fix the 2D lock by reinstalling your drivers instead of rebooting.. which ever is the fastest..

Thx monkey. I suspected it was 2D mode but couldn't figure out why it sets it there AFTER the game is exited. Guess you're right and I'm lucky to get away with it at all. It's in a well ventilated CM Centurion5 case with a spot fan blowing over the top of the card which helps cool the NB on my mobo so it's probably teetering on the edge when I play but crashes on exit. I'll try to find some middle ground between 1350 and 1512 and see if I can fold AND still play the odd game.

/ grabs cake and eats it too
 
When the driver crashes, it recovers right away but stuck in 2d mode. Just reboot and problem should be solved.
 
Are you saying that when you re-enter a game the clocks stay at the 2d frequencies?
 
Just had this happen last night, while fooling around with Batman:AA. Installed the lasted NVidia drivers and all is good.
 
Thx monkey. I suspected it was 2D mode but couldn't figure out why it sets it there AFTER the game is exited. Guess you're right and I'm lucky to get away with it at all. It's in a well ventilated CM Centurion5 case with a spot fan blowing over the top of the card which helps cool the NB on my mobo so it's probably teetering on the edge when I play but crashes on exit. I'll try to find some middle ground between 1350 and 1512 and see if I can fold AND still play the odd game.

/ grabs cake and eats it too
yeah 1512 is probably too high. I would just leave them linked instead of overclocking them separately.
 
602/1460/999 and all is well. played 4.5 hour multiplayer Sins of a Solar Empire and no clocking issues. might be losing a tiny bit of ppd but at least I can game a bit :D. Thanks for the help folks.
 
Back
Top