Stuttering

[Madmullen]

This is my current spec:
Case:Corsair Osbidian 750D
Motherboard:Asrock 990FX Extreme4
CPU: Amd FX(tm)6300 six core Black Edition 3.76Mhz
Ram:Corsair Vengence 16GB Dual Channel @ 1600MHZ
Graphics: MSI GeForce GTX 760 OC Gaming Edition 2048MB GDDR5 PCI-Express (not clocked yet)
Sound: Onbrd
HDD: Baracuda 1TB
HDD: Toshiba 250GB
DVD: LG Lightscribe
PSU: Corsiar RM Series 650W
Aerocool X-Vision 5 Channel LCD Fan Controller

Cooling: Corsair Hydro H105 running in Push
Corsair 2XSP120mm
1 x SP120mm Exhaust
2 x SP140mm Intake

Today I received my new MSI GeForce GTX 760 OC Gaming Edition 2048MB GDDR5 PCI-Express
All drivers are up to date and I also use Geforce Experience ver 2.0 to optimise my games.
I have ran Unigine Valley works fine until I reach the part with the rain, lightning aall the effects where my system grinds to 7fps.
I ran it once more and the same thing happened but just by chance I moved the mouse and this seems to get the benchmark going again.
I ran it a 3rd time moving the mouse occassionally and on average got 70fps, can anyone tell what I can do to solve this problem as this has been horrendous when racing as lose of control is not a good thing.

 

[MacLeod]

Is it only Unigine that it does this on or is it your games as well?

 

[Madmullen]

It was doing it on all games but I have managed to OC the cpu a bit more and this seems to have solved the problem for now.

 

[MacLeod]

Yeah might want to get that FX as far up into the 4 GHz range as you can. 3.7 is a little slow for those things and could be a bottleneck but dropping down into the teens does seem a little odd.

 

[Madmullen]

Im not that good at overclocking, I tried 3.8mhz ran prime for 1hr and core5 failed.
I had to eventually clear the cmos and load default setting before reclocking to 3.7mhz. I also had to repair my MBR as I keep getting an error message when booting.

 

[Captain Shiny]

Im not that good at overclocking, I tried 3.8mhz ran prime for 1hr and core5 failed.
I had to eventually clear the cmos and load default setting before reclocking to 3.7mhz. I also had to repair my MBR as I keep getting an error message when booting.

I once had framerate problems with only one certain game and it turned out that a broken file system on my games partition was the cause - no faulty sectors, tough. Attempts to repair the partition via chkdsk failed so I had to format the partition to get rid of the problem but after that everything worked just fine again.
So you might want to keep your HDD in mind as well when you search for the culprit. A broken MBR might be an indicator that something similar happened to you.

 

[tinytomlogan]

Not heard this so much recently but before it was always due to 'auto' ram settings