Problems with a GTX 690

Phaseonedsm

Honorable
Oct 15, 2013
21
1
10,520
I just bought a new motherboard a Sabertooth R2 and it works great from what i can tell. I also bought a GTX 690. I used to have a MATX board but as you can guess the overclocking wasn't great so i bought the Sabertooth R2 for better OC. Then i also had a GTX 770 4GB but i wanted something faster that could push 3 monitors with higher settings so thus i bought the 690. Since i've bought the 690 i've had bad performance issues. I've tried different Drivers and even put my PC back to stock settings and it didn't make any difference actually it made them worse due to even lower frame rates. Here is what is happening. I noticed i was getting around the same frame rate as my 770 if not worse. but i was getting what i would describe as stutter. I started looking deeper and noticed on MSI Afterburner that under the GPU Power % it will jump up and down from say 125% down to 32% give or take. I've tried everything to make it not do this but i'm worried that the 690 is a dud. Here is my specs.

CPU: 8350 @ 4,8GHz 1.36v
RAM: 8GB DDR3 1600 @ 2133MHz (9-11-10-28)
MB: Asus Sabertooth R2.0
GPU: Asus GTX 690

Here is my MSI Afterburner Monitor during Far Cry 3 just walking around.
Capture_zpsf3940f0d.png
 
got the computer back they couldn't figure it out told me it was normal lol but i found out it was a monitoring program causing the bad fps and the stutter called HWMonitor i know its widely used but this was the cause.
 

I unselected that Best Answer. You can select another if you wish.

So is your problem fixed? My initial thought was that your power supply was inadequate. Your Afterburner screenshot actually looks pretty good, as your GPU is supposed to peak out around 83c.
 
Yeah its fixed turns out the monitoring software i was using caused a conflicted with my CPU. Causing everything to stutter really bad in every game i played. Deleted that and now everything runs as it should i still get a very small amount of stutter so i think there is another program causing it so i'll track that down.