Overclock.net › Forums › Graphics Cards › NVIDIA › Bad FPS in Counter-Strike: GO + micro-stutter, GTX 680 + i5 2500k MSI P67a-G43 motherboard 16gigs DDR3
New Posts  All Forums:Forum Nav:

Bad FPS in Counter-Strike: GO + micro-stutter, GTX 680 + i5 2500k MSI P67a-G43 motherboard 16gigs DDR3

post #1 of 8
Thread Starter 
I am at my wits end here, so I'm trying to post this everywhere.

My build worked perfectly for 2 years now, especially the since getting my GTX 680 last year. I put in my new Samsung 830 120 Gig SSD which started this chain of events as detailed below:

I put the SSD in, reformat my RAID 0 (previous Windows install), and install windows to the SSD which is now C. During the process the computer won't show the RAID 0 in Windows. Using the Windows disk I finally am able to format the RAID 0 and Windows eventually detects it again.

I install the motherboard chipset drivers from MSI's website, update Windows, install Nvidia's latest Beta 314 drivers (same ones I had been using). I install CS:Go on the SSD and fire it up. Everything works fine. This was Sunday night.

Monday I decide to mess with my logitech g400 mouse. I need to fix the DPI. I had trouble with Logitech Setpoint in the past when trying to get it to detect my wireless keyboard a month ago (I gave up on the keyboard). Anyway, SetPoint didn't recognize my g400, just like it hadn't recognized my keyboard in the past. I was checking forums and someone suggested deleting the mouse driver out of system32 and reinstalling. I didn't realize at the time that logitech uses a completely different piece of software for the g400, thus that's why setpoint wasn't working. I deleted the mouse driver, re-installed it, and rebooted.

That's when the system lost its bootsector. The Windows disk recognized a previous install of windows, but would not repair it, or the bootsector. I used command prompt and DISK PARTITION eventually make the SSD primary, and then bootsec commands to finally rebuild the bootsector and get back to my desktop. I loaded Counter-Strike and it proceeded to run like garbage. We're talking 30-150 frames with huge variation and micro-stuttering no matter what settings I used. Feeling that the computer must have fragged itself I ran 3D Mark and scored about 10 percent under for my build on Wednesday, about 27k.

I reformat the SSD again, to get rid of any sort of problems derived from the bootsector failure on Monday, and the problem persists. Confused I consult a friend who says I should roll back my drivers to 310 from December, swap the SATA cable and SATA port to the SSD. I do all this.

I score a normal range 30k.

I run Counter-Strike, and it is pushing a solid 120-230 FPS. Not my normal constant 300 I am used to, but at least the micro-stutter is gone and I can play again. Considering it a victory I retire for the night.

Thursday, I go to play CS and the problem is back. We're talking absolute garbage, micro suttering, 30-120 FPS, with huge variation. Without rebooting or anything I run 3DMark to see if it is a problem with CS, and only CS, or the machine. 3DMark reports completely normal levels, 5400 in Fire Strike.

I try updating the drivers to 314.07, the latest WHQL, and the problem persists. I check my GPU on GPU-Z to make sure it is coming out of 2d clocks, and yes it is. I tried turning off my over clock. I check my temperatures, my i5 is around 60c w/ over clock, and ice cold when non-overclocked. I've done everything I can think of. I deleted CS and reinstalled it on my mechanical drive. I double checked my chipset drivers are installed.

TL;DR So I put in a new SSD and reformatted my machine. I'm running an i5 2500k at 4.4 and a GTX 680. I installed latest Nvidia WHQL drivers 314.07 and all my motherboard MSI p67A-G43 chipset drivers. I've played CS:Go on this machine for the past year at 250-300 FPS. I am now getting awful frames and lots of lag. We're talking 30-120 frames on net_Graph 3 and micro-stutter the whole time. I have reformatted twice. I have no idea what could be causing this. I deleted CS:Go from my SSD and redownloaded and installed on the mechanical drives and still have this issue. Nothing I do seems to resolve it.

The computer runs 3DMark fine scoring around 5439 on Fire Strike, so my issue is solely with Counter-Strike. I tried turning the over clock off and running default bios settings but the problem persists. I don't know what else to do.
post #2 of 8
Wow, it seems like you've tried everything. I'm actually baffled as to what has happened. The only thing I can think of is to maybe downgrade some of your drivers... A similar problem has happened to me before and downgrading my nVidia drivers seemed to do the trick. Good luck thumb.gif
     
CPUMotherboardGraphicsRAM
3930k Rampage 4 Extreme EVGA GTX 690 Corsair Platinum 
Hard DriveOptical DriveCoolingOS
Western Digital Caviar Black x2 Nope Liquid Cooled Win 7 Ult 64b 
MonitorKeyboardPowerCase
3x Yamakasi Catleap Q270 "extreme OC" 120hz 1440p Razer Blackwidow 2013 Corsair AX1200i COSMOS 2 
MouseMouse PadAudioAudio
Razer Ouroboros ?Vespula? Crappy 2.1 Logitech Raze Tiamat 7.1 
CPUMotherboardGraphicsRAM
i3 2100 ASUS P8H77-I AMD Radeon HD 6450 Cheapo RAM - 4GB 
Hard DriveCoolingOSMonitor
500 GB Heatsink that came with the CPU  Windows 7 Ultimate 64bit HANNS-G 24 Inch 
KeyboardPowerCaseMouse
Cheapo Cheapo Qubz Mini ITX Cheapo 
Mouse PadAudioOther
Do i look like I'm rich? Teac 2.1 speakers Low ego 
  hide details  
Reply
     
CPUMotherboardGraphicsRAM
3930k Rampage 4 Extreme EVGA GTX 690 Corsair Platinum 
Hard DriveOptical DriveCoolingOS
Western Digital Caviar Black x2 Nope Liquid Cooled Win 7 Ult 64b 
MonitorKeyboardPowerCase
3x Yamakasi Catleap Q270 "extreme OC" 120hz 1440p Razer Blackwidow 2013 Corsair AX1200i COSMOS 2 
MouseMouse PadAudioAudio
Razer Ouroboros ?Vespula? Crappy 2.1 Logitech Raze Tiamat 7.1 
CPUMotherboardGraphicsRAM
i3 2100 ASUS P8H77-I AMD Radeon HD 6450 Cheapo RAM - 4GB 
Hard DriveCoolingOSMonitor
500 GB Heatsink that came with the CPU  Windows 7 Ultimate 64bit HANNS-G 24 Inch 
KeyboardPowerCaseMouse
Cheapo Cheapo Qubz Mini ITX Cheapo 
Mouse PadAudioOther
Do i look like I'm rich? Teac 2.1 speakers Low ego 
  hide details  
Reply
post #3 of 8
Thread Starter 
Quote:
Originally Posted by 512TBofRAM View Post

Wow, it seems like you've tried everything. I'm actually baffled as to what has happened. The only thing I can think of is to maybe downgrade some of your drivers... A similar problem has happened to me before and downgrading my nVidia drivers seemed to do the trick. Good luck thumb.gif

Thanks! I'm going to need some luck. So I tried 310 and it worked that one night then not the next day. Should I go back even further in the legacy archive? Additionally, I used 314 beta on this machine before installing the SSD no problem. I update drivers like a comic book collection.
post #4 of 8
I think that you should try downgrading one more time. If nothing happens, it;s clear that something else is the issue. Another thing you can try is to toggle multi-core rendering. It's been known to help poeple with micro stuttering problems, espesially in Source games. A while back CS:GO started stuttering and I fixed it by disabling the Steam Store window (by changing favorite window to 'Library' in Steam Settings). The store window would force a refresh every few seconds (even if it had been opened and closed) which caused the stuttering in-game. I don't know if this has since been fixed but I just don't load the Steam Store at all anymore and everything has been fine.

I don't know if this helped at all but this is the only experience I've had with stuttering.

I agree that it is a very annoying problem, and i'll do my best to help with getting the situation fixed for you. Let me know if anything has worked thumb.gif
     
CPUMotherboardGraphicsRAM
3930k Rampage 4 Extreme EVGA GTX 690 Corsair Platinum 
Hard DriveOptical DriveCoolingOS
Western Digital Caviar Black x2 Nope Liquid Cooled Win 7 Ult 64b 
MonitorKeyboardPowerCase
3x Yamakasi Catleap Q270 "extreme OC" 120hz 1440p Razer Blackwidow 2013 Corsair AX1200i COSMOS 2 
MouseMouse PadAudioAudio
Razer Ouroboros ?Vespula? Crappy 2.1 Logitech Raze Tiamat 7.1 
CPUMotherboardGraphicsRAM
i3 2100 ASUS P8H77-I AMD Radeon HD 6450 Cheapo RAM - 4GB 
Hard DriveCoolingOSMonitor
500 GB Heatsink that came with the CPU  Windows 7 Ultimate 64bit HANNS-G 24 Inch 
KeyboardPowerCaseMouse
Cheapo Cheapo Qubz Mini ITX Cheapo 
Mouse PadAudioOther
Do i look like I'm rich? Teac 2.1 speakers Low ego 
  hide details  
Reply
     
CPUMotherboardGraphicsRAM
3930k Rampage 4 Extreme EVGA GTX 690 Corsair Platinum 
Hard DriveOptical DriveCoolingOS
Western Digital Caviar Black x2 Nope Liquid Cooled Win 7 Ult 64b 
MonitorKeyboardPowerCase
3x Yamakasi Catleap Q270 "extreme OC" 120hz 1440p Razer Blackwidow 2013 Corsair AX1200i COSMOS 2 
MouseMouse PadAudioAudio
Razer Ouroboros ?Vespula? Crappy 2.1 Logitech Raze Tiamat 7.1 
CPUMotherboardGraphicsRAM
i3 2100 ASUS P8H77-I AMD Radeon HD 6450 Cheapo RAM - 4GB 
Hard DriveCoolingOSMonitor
500 GB Heatsink that came with the CPU  Windows 7 Ultimate 64bit HANNS-G 24 Inch 
KeyboardPowerCaseMouse
Cheapo Cheapo Qubz Mini ITX Cheapo 
Mouse PadAudioOther
Do i look like I'm rich? Teac 2.1 speakers Low ego 
  hide details  
Reply
post #5 of 8
Thread Starter 
I think you may be on something with the Steam GUI. I remember disabling some part of it a long time ago. Maybe this setting got changed. I'll look in to it tonight. Thanks for all your help thus far.

Also I tried switching between multi-core rendering enabled and disabled. This shouldn't matter of course. At 4.4ghz a single core can blast out 170 frames easily in CS:Go.
post #6 of 8
Thread Starter 
So I tried the library trick and switched between multi-threaded mode and still no luck. My next step is to take out the SSD and use just the mechanical drive with a fresh format of windows.
post #7 of 8
Thread Starter 
So I tried running from a fresh format on my SSD with all my other hard drives out and the motherboard on AHCI, latest drivers and I tried 310. Nothing worked. I took out the SSD and loaded up 1 of my old mechanicals, reformatted and installed windows fresh. I then tried 310 and the problem persists. I have no idea what's left to do. I turned off my overclock and everything. Tomorrow I'll try a hard reset on the bios and swapping out my GTX 680 with my old GTX 460se.
post #8 of 8
Thread Starter 
So I finally fixed it. I put mRs.Waffles's GTX 460se in my machine. I swapped the PCI-Express power cables and position on the power supply. The 460se worked so I figured maybe my GTX 680 is broken. I put the GTX 680 back in, on the same cables going to the 460SE and viola we're in business. I want to think everyone for their help. I have no idea how a bad cable could run 3DMark perfectly and not CS:Go. It makes no sense. Somehow we're working now. Thanks again.

I'm going to put the SSD back in and hope for the best.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: NVIDIA
Overclock.net › Forums › Graphics Cards › NVIDIA › Bad FPS in Counter-Strike: GO + micro-stutter, GTX 680 + i5 2500k MSI P67a-G43 motherboard 16gigs DDR3